This is the hack approach to adding environment variables to the nginx configuration files. As with most Google results for this search, the reason is Docker.
I intended to deploy two Docker containers.
| # Project: https://github.com/getsentry/sentry | |
| # Doc: https://docs.getsentry.com/on-premise/server/installation/python/ | |
| sudo apt-get update | |
| sudo apt-get install python-virtualenv | |
| sudo apt-get install python-setuptools | |
| sudo apt-get install python-pip | |
| sudo apt-get install libxslt1-dev | |
| sudo apt-get install gcc | 
| # Project: https://github.com/getsentry/sentry | |
| # Doc: https://docs.getsentry.com/on-premise/server/installation/python/ | |
| sudo apt-get update | |
| sudo apt-get install python-virtualenv | |
| sudo apt-get install python-setuptools | |
| sudo apt-get install python-pip | |
| sudo apt-get install libxslt1-dev | |
| sudo apt-get install gcc | 
| require 'rspec/expectations' | |
| RSpec::Matchers.define :be_boolean do | |
| match do |actual| | |
| [true, false].include? actual | |
| end | |
| failure_message_for_should do |actual| | |
| "expected that #{actual.inspect} would be a boolean(true or false)" | |
| end | 
| { | |
| "config": { | |
| "chainId": 33, | |
| "homesteadBlock": 0, | |
| "eip155Block": 0, | |
| "eip158Block": 0 | |
| }, | |
| "nonce": "0x0000000000000033", | |
| "timestamp": "0x0", | |
| "parentHash": "0x0000000000000000000000000000000000000000000000000000000000000000", | 
| Latency Comparison Numbers | |
| -------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD | 
| set :private_pub_pid, -> { "#{current_path}/tmp/pids/private_pub.pid" } | |
| namespace :private_pub do | |
| desc "Start private_pub server" | |
| task :start do | |
| on roles(:app) do | |
| within release_path do | |
| with rails_env: fetch(:stage) do | |
| execute :bundle, "exec thin -C config/private_pub/thin_#{fetch(:stage)}.yml -d -P #{fetch(:private_pub_pid)} start" | |
| end | 
This is the hack approach to adding environment variables to the nginx configuration files. As with most Google results for this search, the reason is Docker.
I intended to deploy two Docker containers.