A tip for using Beanstalk Enhanced Health monitoring instead of Basic Health:
For Drifting Ruby's Production environment, my nginx.config looks like this. Take note that the file is not /etc/nginx/conf.d/proxy.conf, but rather /etc/nginx/conf.d/webapp_healthd.conf. This is because we are overwriting the existing default webapp_healthd.conf that beanstalk creates a symlink for. If you do have existing instances with the older proxy.conf, it could create a conflict since we're listening on port 80.
Hello Alispat, is there anything in particular you'd like to see about Beanstalk? So far, this series should be enough to get an app running. Honestly, Drifting Ruby is on Beanstalk, and I haven't done much more beyond these configs. I am using Redis and Elasticsearch which are external resources to Beanstalk which may be good to cover since they can be a bit quirky.
Well done! Invaluable knowledgment! Please, more PRO episodes about beanstalk! It's fantastic!!!! Regards and thank you!
A tip for using Beanstalk Enhanced Health monitoring instead of Basic Health:
For Drifting Ruby's Production environment, my nginx.config looks like this. Take note that the file is not /etc/nginx/conf.d/proxy.conf, but rather /etc/nginx/conf.d/webapp_healthd.conf. This is because we are overwriting the existing default webapp_healthd.conf that beanstalk creates a symlink for. If you do have existing instances with the older proxy.conf, it could create a conflict since we're listening on port 80.
Hello Alispat, is there anything in particular you'd like to see about Beanstalk? So far, this series should be enough to get an app running. Honestly, Drifting Ruby is on Beanstalk, and I haven't done much more beyond these configs. I am using Redis and Elasticsearch which are external resources to Beanstalk which may be good to cover since they can be a bit quirky.