What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hi docker Guys π I've seen that spryker now is compatible with newer version of Postgres (offi
Hi docker Guys π
I've seen that spryker now is compatible with newer version of Postgres (officially π )
-> https://github.com/spryker/docker-sdk/tree/master/generator/src/templates/service/postgres
What are the steps to migrate correctly to new version (12 i.e.) locally? Of course task 1 is set version in deploy.yml and deploy.dev.yml (or default set). After that? We have to remove the container or just run bootstrap!? I want just write the migration for all devs in project.
Thank u very much in advance.
Comments
-
Hi, I suggest:
* stopping the containers (if they are running)docker/sdk stop
- , running clean
docker/sdk clean
- and then boostrap
docker/sdk boostrap deploy.dev.yml
- and then run up
docker/sdk up
0 - , running clean
-
you can omit clean but this will leave containers that will not be used
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
Ok @UKHD8KTMF but what is about data?
When i upgraded the ES version 6 months ago then i must remove container otherwise it was not more working -> https://sprykercommunity.slack.com/archives/CMYFJCG2E/p1576585779010200
0 -
then run clean π
0 -
I would personally run docker system prune - but this is not without side effects, because it will clean images/volumes etc everywhere and this is not acceptable to some
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
Ok.. but clean
- Stop all Spryker containers and remove images and volumes.
and it means that i have to re-intall the whole application locally.. right?0 -
yes
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
ok. clear now... thank u very much..
p.s.: i thought that maybe there was another way to save db data, swithc version and then restore data... without re-install the application
0 -
maybe there is, I am just no aware of it
0 -
you can try, doing bootstrap and then reset
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
ok.. me too.. because reinstall was also my first idea.. just as u described...
0 -
reset will -
Remove and build all Spryker images and volumes
0 -
would need to check if it is leaving storages intact
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
ok. i will try.. thanks
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
reset remove all data and intialise all new.. and not take care on deploy.dev.yml changes..
After reset now bootstrap and i get the same error that database is not running, please check name etc...
it means:
stop
clean
bootstrap
up
demo-data0 -
deploy.yml changes are only taken into account when you run bootstrap
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
yes i know.. i thouth that the reset command before build process take care on bootstrap self
0 -
your order is what I would do - only thing that make wonder why up after clean did not run data import
0 -
it should
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
yes.. i see too... it just run demo-data to initialise db but not import data...
0 -
ok, I just learned something new
0 -
maybe behavior changed
0 -
giovanni.piemontese Technical Lead @ LΓΆffelhardt Spryker Solution Partner Posts: 871 π§π»βπ - Cadet
yes.. it make sense... just one command and everything fresh there..
0 -
Hi Giovanni,
In case you really need to save the data, you might want to consider the following flow (we tested it only to increase version:
For pg:
1. docker exec spryker_demo_database_1 pg_dumpall -U root > dump.sql
2. docker/sdk down
3. docker volume rm spryker_demo_database-postgres-data
4. Change version into docker/deployment/default/docker-compose.yml for database
5. docker/sdk run
6. docker cp dump.sql spryker_demo_database_1:/var/lib/postgresql/data
7. docker exec -it spryker_demo_database_1 bash
8. psql -U root < /var/lib/postgresql/data/dump.sql
I hope it will help and provides a guideline of how to upgrade PostgreSQL to a higher version and preserve the data.0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 69 Spryker News
- 894 Developer Corner
- 757 Spryker Development
- 83 Spryker Dev Environment
- 361 Spryker Releases
- 3 Oryx frontend framework
- 34 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 22 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
- 68 Spryker Safari Questions
- 50 Random