Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Admin site not rendering css properly #41

Closed
1 task
mrharpo opened this issue Sep 2, 2022 · 1 comment · Fixed by #42
Closed
1 task

Admin site not rendering css properly #41

mrharpo opened this issue Sep 2, 2022 · 1 comment · Fixed by #42
Assignees
Labels
bug 🐛 Something isn't working production 🎭 Relating to the production deployment

Comments

@mrharpo
Copy link
Contributor

mrharpo commented Sep 2, 2022

Because

The wagtail admin site displays properly in development, but not in production.

Screenshot from 2022-09-02 12-06-30

Everything is functional, including login, and all the files appear to be served correctly, including css.

Screenshot from 2022-09-02 12-08-29

Done when

  • Admin site displays properly
@mrharpo mrharpo added bug 🐛 Something isn't working production 🎭 Relating to the production deployment labels Sep 2, 2022
@mrharpo mrharpo self-assigned this Sep 2, 2022
@mrharpo mrharpo added this to the v0.2.1 Upgrade 🔨 milestone Sep 2, 2022
@mrharpo
Copy link
Contributor Author

mrharpo commented Sep 6, 2022

Fixed with #42

Solution

nginx needed to include /etc/nginx/mime.types;

Admin site now renders properly!
ov-admin k8s wgbhdigital org_admin_login_ (1)

After login:
localhost_8000_admin_

@afred afred closed this as completed in #42 Sep 9, 2022
afred pushed a commit that referenced this issue Sep 9, 2022
# MIME types
Includes `mime.types` with nginx config.

Closes #41, production admin site display bug.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working production 🎭 Relating to the production deployment
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant