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
  • #17
Closed
Open
Created Aug 27, 2020 by David Werner@rootOwner

Pathes/routing of the application in deployment needs to be fixed

Suppose the application runs on https://dumux.org/dumux-web-app/. Like my current version in branch feature/routing-of-production with modified routing in App.js.

Then a path like (on hypertext protocol)

GET /dumux-web-app/config/simulation-1

should work. It does not. This you trigger when you push your reload button of browser on application 1.

I also see in Webserver-Log an access like

GET /images/fracture-case1.png 

generated when loading the application 2. Of course this does not work as it is an access to something not is not the app directory. It should be

GET /dumux-web-app/images/fracture-case1.png

which is already accessibly. You can just directly access https://dumux.org/dumux-web-app/images/fracture-case1.png

Edited Aug 27, 2020 by David Werner
Assignee
Assign to
Time tracking