How the static files are served depends on a few things. What is the DJANGO_MODE variable set to in the docker-compose.yml that you are using? (NB if you also have an .env file in that directory, that may be overwriting this issue)
If it is PROD, then the command to collect static files should copy them all to the directory "/static_root" by default. It will look for them in the directories specified in the STATICFILES_DIRS list in settings.py. This should be marked as a persisted volume in your docker compose configuration: " - arches-static:/static_root". The nginx container also has access to this volume, which it mounts as '/www/static' and serves as " http://host/static/...";. The Arches instance will be available from http://host:80/ (eg http://localhost ). The Arches instance will be served from the arches container on port 8000, but you should not be accessing this directly. If DJANGO_MODE is DEV, then the django runserver process is used to serve the contents, and it will be available on port 8000. This will also serve the static files as well, and you should be able to access the Arches instance from http://host:8000 (eg http://localhost:8000). Ben On Tue, 16 Apr 2019 at 09:24, Matthias Bussonnier < [email protected]> wrote: > Hello, > > I am trying to deploy Arches for our local institution, I'm trying to go > through the instruction [1], on how to run in docker. > Most instruction appear to work so far (a couple of couchdb and > elasticsearch warning which I'm going to assume are for first run, > But when accessing the local install, I get greeted with 404 on any static > resource situated under /media/. > > Arches does seem to properly copy assets : > > > arches | Copying > '/web_root/arches/arches/app/media/packages/font-awesome/README.md' > (and alike), > > And does this the requests ( so it's likely not a nginx thing): > > > arches | 172.21.0.1 - - [16/Apr/2019:11:18:40 -0500] "GET > /media/css/unify.css HTTP/1.1" 404 93 "http://localhost:8000/"; > > > I'm i'm starting to run out of ideas of what could cause this, and would > love some guidance – which I would be happy to contribute in the form of > pull-requests again the main repository. > > I'm tried the master (a20525c1828 as of April 11th) and 4.4.1, making > sure to update docker-compose to point at my locally built docker image, > and pruning docker volumes. > > Thanks, > -- > 1: > https://github.com/archesproject/arches/tree/master/docker#setting-up-your-own-arches-project > > -- > -- To post, send email to [email protected]. To unsubscribe, > send email to [email protected]. For more > information, visit https://groups.google.com/d/forum/archesproject?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Arches Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
