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.

Sign up for GitHub

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

Jump to bottom

serve static content under dedicated assets route #4736

Open
Schwehn42 opened this issue Dec 30, 2024 · 0 comments · May be fixed by #4775
Open

serve static content under dedicated assets route #4736

Schwehn42 opened this issue Dec 30, 2024 · 0 comments · May be fixed by #4775

Comments

@Schwehn42
Copy link
Collaborator

In order to allow for some Nginx configs, we should serve static content (timer_finished.mp3, hotkeys.pdf) under a dedicated subdirectory. Could be called assets.

Originally posted by @kersten in #4724
@Schwehn42 Schwehn42 linked a pull request Jan 14, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
scrumlr.io
Status: Todo
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

refactor: static content assets directory inovex/scrumlr.io
1 participant
@Schwehn42