...
After I update
tutor/templates/apps/openedx/settings/partials/pre_common_all.pyhow do I update my local tutor settings files?Why does the run command set permissions every time?
Should we be running exec instead?
Why do we have to re-build the image between dev and test? https://docs.tutor.overhang.io/dev.html#running-edx-platform-unit-tests
Could there be a simpler workflow?
Is setting up to test e2e something you're planning to do?
If we want to change Django settings, is this where we should be using some existing hooks that we're not aware of?
Why have your own Django settings files? Is this due to historic reasons?
5 Next Steps
Talk to Régis about our open questions.
Reevaluate in the future after some of the gaps have narrowed, or prioritize helping narrow the gaps. See the following notes on the current stance on various questions:
Should we replace devstack with tutor today? No.
Should we replace devstack with tutor someday? Maybe.
What's preventing us from doing it now?
Missing MFEs
Currently Tutor has no MFE plugins. We would need to build this.
Missing Backend Plugins
Credentials
Registrar
Out of date with Master for data layer services (mongo, es)
Example: Course discovery elasticsearch
This may be tricky to fix and would involve updating tutor's settings files and default images.
Replacing default images is already supported.
We may be able to use hooks to update settings which is the other thing that would be needed.
Not all Unit Test work for the LMS
Other various use cases that devstack currently supports and Tutor doesn't (not making a value judgement, just calling out for completeness.)
e2e testing
Generating Programs Data
No quick script to provision all plugins at once, each service/plugin is manage individually.
Missing a "do all the things" script is fine if we want the users to know and do each thing they want manually.
But missing the "do all the things" scirpt does increase the number of things a developer needs to know and do manually.
The option to run with NFS mounts
...