Running s:up s:d:c s:s:d

[francesco-di-marcantonio]

Hi there, one information, i'm testing your helm chart but i dont understand how can i run deploy command like setup:upgrade setup:di:compile setup:static-content:deploy.

Once the infrastructure is on, if we create a module or want to redeploy, how can we do?

Thanks

[phoenix-bjoern]

@francesco-di-marcantonio The Helm chart is to deploy/setup the services (infrastructure) in Kubernetes. What you are looking for is the (Magento2 container image) (https://github.com/PHOENIX-MEDIA/magento2-build). The container image contains the Magento2 code, all the modules and themes as well as a setup/deploy script to execute setup/upgrade etc. once the pod starts up in K8S.

So basically every time you change your code, you have to build a new container image and deploy it to K8S. Building the container is part of the CI while the Helm chart is used for the CD process.

Check out this video here to see the process: https://youtu.be/7Ke0aqXeyNs?si=exgbmgL5bCF1Uozr

[phoenix-bjoern]

@francesco-di-marcantonio check out the Medium article on how to build the Docker image.

[francesco-di-marcantonio]

Okey thanks! i'm trying to understand how the infrastructure is connected (all the images/dockerfile/github repo). The helm chart is deploying a clean magento2 skeleton but how i'ts related with the magento2-build? if i wanted to connect my own repo and run the ci, should i rebuild from your "magento2-cloud-build" and link my own repo?

[phoenix-bjoern]

Actually the Helm chart is only loosely coupled with the „application“ (Magento2 image) it deploys. So, you are interested in this file: https://github.com/PHOENIX-MEDIA/magento2-build/blob/main/install.sh. To understand how to build the Docker image check out the Medium article mentioned above.

Will close the ticket as this is not an issue to fix. But feel free to ask more questions.