Keep migrations in repository?
We are about to move to prod. Currently we just use the Spryker default .gitignore setup where migrations are not commited to the repository.
I've seen 2 articles that relate to this topic in the docs:
I understand it is recommended then to keep migration files for productive systems.
Do I just remove migration files from gitignore and commit them?
Are the default pipelines in aws and install recipes ready for this? I see propel:migration:delete and propel:diff in production.yml.
Best Answer
-
Hello Victor, yes, you need to remove migration files from .gitignore and adjust installation recipe (remove propel:migration:delete command) in the project files, AWS pipelines will use installation recipe from the project repository.
1
Answers
-
Hello Victor, yes, you need to remove migration files from .gitignore and adjust installation recipe (remove propel:migration:delete command) in the project files, AWS pipelines will use installation recipe from the project repository.
1 -
fsmeier Senior Software Engineer & Developer Enablement Advocate Sprykee Posts: 1,084 ⚖️ - Guardians (admin)
Heyhey, please also have a look here:
All the best,
Florian
1
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 927 Developer Corner
- 785 Spryker Development
- 88 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random