We would prefer GCP over AWS for it is supposed to be cheaper. Any reason we should reconsider?
No reason comes to mind. I do not if anyone in the community has any thoughts about it.
We currently think the the bitnami LAMP stack is perfect for us. What if we use RDS or GC SQL, can we then just disable MySQL from the stack?
Yes, you can disable and use whichever system you prefer. I do not know if you may need to install any extra php extension in the case of GC SQL, but it is doable. Execute these commands to stop and disable the MySQL stack.
sudo /opt/bitnami/ctlscript.sh stop mysql
sudo mv /opt/bitnami/mysql/scripts/ctl.sh /opt/bitnami/mysql/scripts/ctl.sh.disabled
How are updates handled? Does bitnami automagically update the stack on our instance in the cloud leaving our php app untouched?
I am afraid it is not the case. If you want to update the stack the recommended process is to launch a new instance and redeploy. The best way to work with Bitnami images is to use Immutable infrastructure:
In today’s landscape of web service deployment, it’s pretty clear that everyone has moved to the cloud. You’re either using a public cloud, a private cloud or are currently frustrated with your infrastructure.
Containers have started to...
You may not realize it, but you're only a few steps away from building an immutable infrastructure for your applications. In this post, I will explain why immutability matters and how Bitnami ready-to-use cloud images can help you achieve it. We do...
As the stack contains a mysql db we suppose that this db is running inside the ec2 or compute engine. That means we do not make use of RDS or GC SQL. What is the advantage? Is it cheaper? How is it scalable if our website gets many visits?
Our images are all-in-one. Depending on the size of your instance, it could be cheaper than using RDS or GC SQL. However, depending on your needs, you may want to look into multi-tier deployments or using RDS or GC SQL. If you want to scale, then multi-tier deployments should suit your needs better. This link should help you:
In our php app the users can also upload images. We suppose it is no good idea to store those uploads in the instance where the stack is running. Should we use S3 or GC Storage for that?
Following the immutability principles, then S3 or GC Storage is a better solution.
The CI of our app from github the the could still be done with TravisCI that just ftp uploads the current commits? Is there a better way?
I don't have much experience with that. In advanced deploymens, the CI/CD would build a cloud image and re-deploy it. I do not know if anyone in the community could share their experience.
Hope it helps.
Javier J. Salmerón
Was my answer helpful? Click on