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..
Theoretically you should be able to build production like images with containers containing your sou
Comments
-
Hello. Actually there is a good reason to stick to the "Spryker-way" doing the infrastructure topics. But if the ci/cd stuff is not achievable with it the optimal way, what stack do use exactly? ps. I see, gitlab ci. So, to sum up, You use spryker docker sdk for local dev and gitlab ci for deployment tasks, right?
0 -
We use our own Docker containers for the Spryker shops (and running tests) but a docker/sdk oriented Kubernetes deployment triggered via GitLab CI, yes.
So we are using all the parts that are in docker/sdk, just not via docker/sdk and in some details specialized to our use cas.e0 -
Hi guys,
Yes, at the moment, our docker/sdk supports local development and preparing production images/assets.
CI/CD support is planned, but itβs too early to share more details.0 -
I would love to hear more about your setups and how you work at the moment.
0 -
Same setup as Thomas here.
Custom docker containers based on Ubuntu 18.04 (20.04 in testing). Custom dev environment with docker compose. CI/Staging/Production/Review APPs also with custom scripts on Gitlab CI with Google Kubernetes Engine.
Custom, cause we startet with Spryker on Docker 3 years ago and since it all works no urgent reason to migrate to SDK.0 -
@UPZH5HHEV As to me, Im just at preparing setting up dev and ci infrastructure, so, basically "standing on the crossroads". The constraints I have are, I should stick to bitbucket ci instead of gitlab ci. So the thought is to use Spy Docker SDK for local setups and Bitbucket ci + Kubernetes for deployments.
0 -
@UPZH5HHEV "CI/CD support is planned, but itβs too early to share more details." -- Could you provide some informations about the approx. terms so far? Or it is too early for such statements yet?
0 -
Alexey, it is really to early. I will share any information as soon as possible π
0 -
I think one major thing here is that Docker/SDK can only cover a quarter of the story to a successful CI/CD chain and therefore to a successful deployment. Building the containers for Spryker isn't very hard and your containers already serve as a good base.
What is really challenging is the project / customer specific scenarios that one faces and the requirement to "make it scale" and easy to fan out. This is highly custom so I don't think there can be such thing as a general solution. Marc and I are using Kubernetes but the way we do will probably be very different and very specific to our needs - which is a good thing.
0 -
On the other hand, Spryker could improve the post-deployment story. Jumping into a container and running console commands is not really ideal. We have our workarounds and solutions for those scenarios but a well defined "post-rollout" tool would be greatly appreciated.
0 -
@UQ958DA4U I see. Still, don't you think it would make sence to provide some kind of "sample solution" for deployment scenarios, basing on, say b2c demoshop?
0 -
Yeah sure, but that's an entirely different story IMO. Both a general Ansible/Chef/... and maybe Kubernetes deployment example for B2C (DE/AT/US) would probably be a good idea (incl. documentation about stop-gaps and high availability / scaling scenarios)
0 -
Are there news on the CI/CD capabilities for docker/sdk @UPZH5HHEV?
0 -
Hi Sebastian,
At the moment, we are finalizing a large amount of docker-sdk improvements and are going to release them soon. Some of these features aimed to improve CI/CD processes. I will announce here when it is released.
Meanwhile, if you have a specific case or feature you would like to improve or being implemented, please, let us knowThank you.
Dmytro0 -
Thank you @UPZH5HHEV. I will wait for the release and see what we get there π
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 75 Spryker News
- 924 Developer Corner
- 783 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
- 25 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