I am trying to debug issues with Palm release and Discovery plugin. It doesn’t work correctly and many people have already asked questions about this and no one provided answer. So I decided to debug the code and see what’s happening. However with Tutor dev discovery plugin doesn’t work at all (see bug in tutor discovery plugin github which I submitted). So I am forced to debug in local mode. However even with mounted edx-platform code, every tiime I change code I need to restart lms container in order for changes to be applied. In dev mode as soon as I change the code and refresh the page the changes are applied. Anyone knows why is this happening and how can I solve it?
Could you share links to the specific issues you’ve encountered with the Discovery plugin in tutor dev? That would help narrow down whether it’s a known bug or something specific to your setup.
On the core question, the difference between tutor dev and tutor local is intentional:
tutor dev runs services in development mode with auto-reload (via Django’s runserver and the watchthemes container for theme changes). Code changes take effect on page refresh without restarting containers.
tutor local runs a production-like setup using gunicorn, which does not watch for file changes. That’s why you need to restart the container after each change — it’s mimicking how the platform runs in production.
If you can share links to the Discovery-related issues, we can see if there’s a fix or a patch that would let you stay in tutor dev.