#Does extension auto reload work in docker container?
25 messages · Page 1 of 1 (latest)
the .env file contains this
I can see the log "Watching extensions for changes..." but nothing happens when updating the extension files
That is possible not all host operating systems allow for watching the files (windows is the main culprit there)
I usually use the npm version to work on my dev environment
But it seems to not work after the docker version came
it just quits the script without any errors
how do you mean? i thought you said extensions we'rent reloading so what script are you referring to?
have you tried not overwriting the entire /extensions folder but just mounting the specific extensions you want? that sometimes helps
no i mean the directus instance doesn't auto reload when the extension changes
the extension files inside /extensions/hooks/myextension gets updated but the server doesn't reload
It works if i run the npm version
question one, did you run windows?
have you tried this?
You're free to keep using that method if you prefer, it will keep working but won't be supported/documented
Yeah i am using windows
Then following this suggestion should help 🙂 Docker runs under Linux so the file watching compatibility is not great when updating on the Windows end and expecting linux to pick up on that
what do you mean?
mounting your extensions individually ```
volumes:
- /path/to/extension/dist:/directus/extensions/<type>/<name>
I tried that but doesn't seems to work unfortunately
Thats a shame
Docker runs under Linux so the file watching compatibility is not great when updating on the Windows end and expecting linux to pick up on that