Open
Conversation
- Bring over database migrations from the your_platform engine and wingolfsplattform - pply filename namespacing - Fix migration issues due to the update to rails 6 - Comment out migration code that requires models and is no longer necessary for fresh app installs. This way, the migration can be tested without using the model layer. #67 (comment)
Owner
Author
Database migrations
|
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.
This pull request collects the following major maintenance steps:
Migrate the application from rails 5.0 to rails 6.1
Many things have changed in rails since our last major update. In particular, webpacker is now a first-class citizen. Because this pull request also converts the rails engine to a standalone application, rather than using the rails-update rake tasks, I'm creating a fresh rails-6 application and replace the appropriate files.
Convert the your_platform rails engine to a standalone application
Move organization-specific code into namespaces
Managing engines requires additional steps when separating javascript code. I've done it for another project and I think that, for now, it's easier for the development process to unify the engine with the major main applications.
Dockerize the development workflow
Drop obsolete feature specs
Dockerize continuous tests