Skip to content

Dev experience: client service fails to come up when trying to use storage directory that will load media files #2620

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

Open
angela-tran opened this issue Jan 9, 2025 · 1 comment
Labels
bug Something isn't working chore Chores and tasks for code cleanup, dev experience, etc.

Comments

@angela-tran
Copy link
Member

angela-tran commented Jan 9, 2025

To Reproduce

Steps to reproduce the behavior:

  1. Set DJANGO_STORAGE_DIR in your .env file to /home/calitp/app/data (it has to be this path so that nginx can serve media files correctly -- see our nginx.conf)
  2. Outside the devcontainer, run docker compose up -d client
  3. The container fails to start because the database cannot be opened

Expected behavior

The container starts, and the app is running in similar way to how it runs in production using NGINX.

@angela-tran angela-tran added the bug Something isn't working label Jan 9, 2025
@angela-tran angela-tran self-assigned this Jan 9, 2025
@angela-tran angela-tran added the chore Chores and tasks for code cleanup, dev experience, etc. label Jan 9, 2025
@angela-tran angela-tran moved this from Todo to In progress in Digital Services Jan 9, 2025
@angela-tran angela-tran moved this from In progress to In review in Digital Services Jan 9, 2025
@angela-tran angela-tran changed the title Dev experience: client service fails to come up Dev experience: client service fails to come up when trying to use storage directory that will load media files Jan 9, 2025
@angela-tran
Copy link
Member Author

In our most recent discussion about this bug, we said it'd be good to introduce a Docker Compose service that sets up the database correctly for the client service. That way, we don't need to have a volume mapping on client.

@thekaveman thekaveman moved this from In review to Todo in Digital Services Feb 25, 2025
@angela-tran angela-tran removed their assignment Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working chore Chores and tasks for code cleanup, dev experience, etc.
Projects
Status: Todo
Development

Successfully merging a pull request may close this issue.

1 participant