Repository navigation
fix(): Streamline setup process of local dev environment - #88
Merged
Merged
Conversation
…p, as this is no longer needed
…-learning into fix/setupscript
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Remove usage of mariadb and building of the OpenEDX image during setup of the local dev enviromnent, as this is no longer needed and just takes longer to set things up.
Context: the usage of mariadb instead of MySQL for the dev environment was made originally because on older versions of OpenEDX, MySQL 5.7 was required, and there was no docker image for that version of MySQL for ARM (which is the platform we use to develop on Apple Silicon Macs). Newer versions of OpenEDX use MySQL 8.0, which does offer docker images for ARM.
We also used to build the image to make it ARM native, but nowadays we can just pull the official image and run it via rosetta which is performant enough for this use case.
Checklist
i.e.
feat(CUR-###): Feature title