Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D Dumux Web App
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 18
    • Issues 18
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • dumux-repositories
  • Dumux Web App
  • Issues
  • #3
Closed
Open
Created Jul 21, 2020 by Timo Koch@timokOwner

Backend configuration

The configuration for each case needs a configuration section specifying the docker setup send from the frontend on simulation start. To make this a bit more secure we could have a list of trusted images and entrypoints stored in the backend, so that not everything the frontend sends is accepted.

JSON scheme

"configuration" : {
  "resources.image"  : "git.iws.uni-stuttgart.de:4567/dumux-repositories/dumux-docker/viplab/test", 
  "resources.volume" : "/data/shared",
  "resources.memory" : "1g",
  "resources.numCPUs" : 1,
  "running.entrypoint" : "/data/bin/run.sh",
  "running.commandLineArguments" : "params.input"
}
Edited Jul 21, 2020 by Timo Koch
Assignee
Assign to
Time tracking