Search the Community
Showing results for tags 'stateless instance'.
Found 1 result
It is unfortunate that I must learn so many things the hard way. After changing my Amazon Elastic Beanstalk with deployed Processwire code the Amazon Elastic cloud removed the website content because it is a stateless environment. Here is the article that explains this: https://www.otreva.com/blog/deploying-wordpress-amazon-web-services-aws-ec2-rds-via-elasticbeanstalk/ I think my mistake is that inside the instance I stored content inside the instance that was running mysql and not the other instance that I thought was the database but I am not sure. Understanding elastic beanstalk as a stateless environment is very important and means that the server instance will terminate and rebuild automatically and any local content will not be replicated unless deployed through the beanstalk environment. This means you you should not ftp php code changes but should instead write scripts or use the EB CLI with GIT hooks to deploy new code or deploy a new zip file version through elastic beanstalk. So my question for the forum is will Processwire work in a stateless environment like Amazon Elastic Beanstalk? If all content including images, etc. is stored in an outside database (RDS) and connect to the Amazon EC2 instance then it should all work. If any content or settings are stored inside the EC2 instance like what I think happened to me with mysql running inside my EC2 instance then when Elastic Beanstalk terminates and rebuilds environments the content will be lost. It is scary to think that all the admin controls will be lost if they are not stored outside the EC2 instance inside the RDS database otherwise Elastic Beanstalk will wipe them out terminating and rebuilding, bummer. If anyone can add advise on this subject of PW running inside stateless environments it is much appreciated. Sincerely, March