title: Running Standard Notes on self-hosted Standard File Server with Ruby Implementation
body: <p>I'm trying to have <a href="https://app.standardnotes.org/" rel="nofollow noreferrer">Standard Notes</a> to run on my self-hosted Ubuntu 16.04 server. I've followed the basic instructions given here on <a href="https://github.com/standardfile/ruby-server" rel="nofollow noreferrer">Github</a>, which is to say, install Ruby 2.2+, Rails 5, MySQL 5.6+ database. All done, and running. </p>
  
  <p>After that, in a subdirectory, I pulled the the <a href="https://github.com/standardfile/ruby-server" rel="nofollow noreferrer">Standard File Server git clone</a>, set up the <code>.env</code> file with this content:</p>
  
  <pre><code>RAILS_ENV=production
  SECRET_KEY_BASE=use "bundle exec rake secret"
  RAILS_SERVE_STATIC_FILES=true
  
  DB_HOST=localhost
  DB_PORT=3306
  DB_DATABASE=db_name
  DB_USERNAME=db_user
  DB_PASSWORD="db_password"
  
  SALT_PSEUDO_NONCE=use "bundle exec rake secret"
  </code></pre>
  
  <p>Initialized the project with: </p>
  
  <pre><code>bundle install
  bower install
  rails db:create db:migrate
  </code></pre>
  
  <p>Again, all fine. When I start the server with <code>rails s</code>, this is the output:</p>
  
  <pre><code>/usr/local/rvm/gems/ruby-2.4.1/gems/activesupport-5.0.1/lib/active_support/xml_mini.rb:51: warning: constant ::Fixnum is deprecated
  /usr/local/rvm/gems/ruby-2.4.1/gems/activesupport-5.0.1/lib/active_support/xml_mini.rb:52: warning: constant ::Bignum is deprecated
  =&gt; Booting Puma
  =&gt; Rails 5.0.1 application starting in development on http://localhost:3000
  =&gt; Run `rails server -h` for more startup options
  /usr/local/rvm/gems/ruby-2.4.1/gems/activesupport-5.0.1/lib/active_support/core_ext/numeric/conversions.rb:138: warning: constant ::Fixnum is deprecated
  Puma starting in single mode...
  * Version 3.10.0 (ruby 2.4.1-p111), codename: Russell's Teapot
  * Min threads: 5, max threads: 5
  * Environment: development
  * Listening on tcp://localhost:3000
  Use Ctrl-C to stop
  </code></pre>
  
  <p>I think the two warnings can safely be ignored. The thing that doesn't make sense is that the <code>.env</code> file is not read as it's running in dev instead of prod, and on port 3000 instead of 3306. Any idea why?</p>