Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

Configuring Production Environments (Linux) 

  • For the system to know the linux install (e.g. aws ec2) is configured as a production environment, and any other system wide configurations you have to edit the ~/.bashrc file. While this will vary by production, but an example line for a Ruby on Rails install will be “export RAILS_ENV=production” 

  • In addition within the application code folder there will usually be a .env file that should be used to store machine specific configuration variables that should not be stored in public locations (e.g. Github). For example devise secret keys 

  • No labels