You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2020. It is now read-only.
For production and testing for production locally, we will want to serve the frontend app index page located at interface/frontend/templates/index.html for requests to '/' on the Django server.
Expected Behavior
Visiting '/' at localhost:8000 renders the compiled frontend app.
Current Behavior
At the moment, visiting '/' at localhost:8000 yields a 404.
Possible Solution
Add a route which serves the compiled frontend app.
Steps to Reproduce
docker-compose -f local.yml up
Visit localhost:8000 in browser
Context (Environment)
I was trying to see how the compiled app looks and noticed that the Django server is no longer serving the frontend app. To get the app ready for production, we need to know that the compiled app is working as expected.
Possible Implementation
PR 97 had the compiled app being served from localhost:8000 so it may be able to be used as a reference.
Checklist before submitting
I have confirmed this using the officially supported Docker Compose setup using the local.yml configuration and ensured that I built the containers again and they reflect the most recent version of the project at the HEAD commit on the master branch
I have searched through the other currently open issues and am confident this is not a duplicate of an existing bug
I provided a minimal code snippet or list of steps that reproduces the bug.
I provided screenshots where appropriate
I filled out all the relevant sections of this template
The text was updated successfully, but these errors were encountered:
One note - the vue devserver is now the one true way to look at the frontend when developing locally. I want to make sure we don't get confused about "production" for this app — almost every meaning of that word is out of scope and we should not waste time on that.
That being said, there is still value in getting a pipeline set up so that Django can serve the built frontend script.
For posterity: my take on a good way to do this is to reuse the same Node/NPM container from the vue service but with a different entrypoint so that the production build creates the minified, static assets and puts them into the Django folder. Still some footwork to figure out how to point Django to these files so they will be served statically and loaded in the base template (?) or something like that.
For production and testing for production locally, we will want to serve the frontend app index page located at
interface/frontend/templates/index.html
for requests to'/'
on the Django server.Expected Behavior
Visiting
'/'
atlocalhost:8000
renders the compiled frontend app.Current Behavior
At the moment, visiting
'/'
atlocalhost:8000
yields a404
.Possible Solution
Add a route which serves the compiled frontend app.
Steps to Reproduce
docker-compose -f local.yml up
localhost:8000
in browserContext (Environment)
I was trying to see how the compiled app looks and noticed that the Django server is no longer serving the frontend app. To get the app ready for production, we need to know that the compiled app is working as expected.
Possible Implementation
PR 97 had the compiled app being served from
localhost:8000
so it may be able to be used as a reference.Checklist before submitting
local.yml
configuration and ensured that I built the containers again and they reflect the most recent version of the project at theHEAD
commit on themaster
branchThe text was updated successfully, but these errors were encountered: