How to set up tmux so that it starts up with specified windows opened?

I am considering using Firebase as MBaaS, however I couldn&#39;t find any reliable solution to the following problem:

I would like to set up two separate Firebase environments, one for development and one for production, but I don&#39;t want to do a manual copy of features (eg. remote configuration setup, notification rules, etc.) between the development and production environment.

Is there any tool or method I can rely on? Setting up remote configuration or notification rules from scratch can be a daunting task and too risky.

Any suggestions? Is there a better approach than having two separate environments?

***Before you post another answer to the question which explains how to set up separate Firebase accounts: it is not the question, read it again. The question is: how to TRANSFER changes between separate dev and prod accounts or any better solution than manually copy between them.***

Separate dev and prod Firebase environment

The default Rails app installed by `rails new` has `config.assets.compile = false` in production. 

And the ordinary way to do things is to run `rake assets:precompile` before deploying your app, to make sure all asset pipeline assets are compiled. 

So what happens if I set `config.assets.compile = true` in production?

I wont&#39; need to run `precompile` anymore. What I _believe_ will happen is the first time an asset is requested, it will be compiled. This will be a performance hit that first time (and it means you generally need a js runtime in production to do it).  But other than these downsides, after the asset was lazily compiled, I _think_ all subsequent access to that asset will have _no_ performance hit, the app&#39;s performance will be _exactly the same_ as with precompiled assets after this initial first-hit lazy compilation. **is this true?**

Is there anything I&#39;m missing? Any other reasons not to set `config.assets.compile = true` in production?  If I&#39;ve got a JS runtime in production, and am willing to take the tradeoff of degraded performance for the _first_ access of an asset, in return for not having to run `precompile`, does this make sense?

config.assets.compile=true in Rails production, why not?

How can I change my Rails application to run in production mode? Is there a config file, environment.rb for example, to do that?


Change a Rails application to production

What is the best way to enable log rotation on a Ruby on Rails production app?

Is it by using logrotate on the hosting server or is there a set of options to use when initialising logger from the app?

Ruby on Rails production log rotation

From my experience, a php server would throw an exception to the log or to the server end, but node.js just simply crashes. Surrounding my code with a try-catch doesn&#39;t work either since everything is done asynchronously. I would like to know what does everyone else do in their production servers.

How do I prevent node.js from crashing? try-catch doesn&#39;t work

My understanding of a canary release is that it&#39;s a partial release to a subset of production nodes with sticky sessions turned on. That way you can control and minimize the number of users/customers that get impacted if you end up releasing a bad bug.

My understanding of a blue/green release is that you have 2 mirrored production environments (&quot;blue&quot; and &quot;green&quot;), and you push changes out to all the nodes of either blue or green at once, and then use networking magic to control which environment users are routed to via DNS.

So, before I begin, if anything I have said so far is incorrect, please begin by correcting me!

Assuming I&#39;m more or less on track, then a couple of questions about the two strategies:

 * Are there scenarios where canary is preferred over blue/green, and vice versa?
 * Are there scenarios where a deployment model can implement both strategies at the same time?

Canary release strategy vs. Blue/Green

It seems like it&#39;s taken for granted that you must not use Webrick as production server, but I can&#39;t really find anywhere mentioning why. The consensus seems to be:
&quot;Webrick is ok for development, but Thin or Unicorn is the choice for production, period.&quot;

I did look up Thin server&#39;s homepage and it talks about requests/second but I don&#39;t really understand the graph since there&#39;s no annotation.

Can anyone let me know why I should use Thin or Unicorn compared to Webrick? Also is there any benefit to using Webrick for development? I&#39;ve been using Webrick since it comes with rails, and I think there should be a reason why it&#39;s default.

I&#39;m using Heroku by the way.

Webrick as production server vs. Thin or Unicorn?

I&#39;ve been searching the web looking for best practices for configuring MongoOptions for the MongoDB Java driver and I haven&#39;t come up with much other than the API. This search started after I ran into the &quot;com.mongodb.DBPortPool$SemaphoresOut: Out of semaphores to get db 
connection&quot; error and by increasing the connections/multiplier I was able to solve that problem. I&#39;m looking for links to or your best practices in configuring these options for production.

The options for the 2.4 driver include:
http://api.mongodb.org/java/2.4/com/mongodb/MongoOptions.html

 - autoConnectRetry
 - connectionsPerHost
 - connectTimeout
 - maxWaitTime
 - socketTimeout
 - threadsAllowedToBlockForConnectionMultiplier

The newer drivers have more options and I would be interested in hearing about those as well.
     
  

How to configure MongoDB Java driver MongoOptions for production use?

For some reason, I have to run my app in production mode. What is the difference between those modes?

What is the difference between production and development mode in Angular2?

I used `script/server -e production` to start rails in production mode. It did and I got no errors. However how do I tell if it is in production mode? I tried a non-existent route, and I got a similar error page I did in development. 

I thought if under production model, I get the 404 error page that is in my /public folder.

Does it mean it didn&#39;t start in production mode?

Thanks for your help.


How to tell if rails is in production?

I&#39;ve written a Node.js app, I&#39;m looking to get it running on one of our production machines. This seems like a pretty common request yet I can&#39;t find an adequate solution. Is there not established solutions for deploying production Node.js apps?

The app is simple (&lt;100 LOC), but needs to be very efficient, reliable and could run continuously for years without restarting. It&#39;s going to be run on a large site, with dozens of connections/second. (the app is not used as a webserver, it only has a JSON API)

Here are the approaches I&#39;ve considered but I&#39;m still not sure about:

**Using a framework (eg. Express)**

Because the app needs to be high performance and is so simple, adding bloat in the form of a framework is something I want to avoid.

**Starting the server with `nohup`**

The main problem here is with exception handling, we (obviously) don&#39;t want the entire server to crash because of an exception. From what I understand, wrapping the entire app in a `try {} catch {}` loop won&#39;t help because the Javascript interpreter is left in an unpredictable state after an exception. Is that correct?

**Using something like Forever**

I&#39;ve installed Forever in a FreeBSD machine of ours and it was very buggy. It ended up spawning endless processes that couldn&#39;t be killed from Forever. I had to run `kill -9` to get my machine back and I don&#39;t feel too confident about running a production app on Forever. It also seems that Upstart (similar tool, but more generic) won&#39;t run on FreeBSD.

**Hosted solutions (eg. Heroku, Rackspace, Amazon EC2, etc.)**

This is probably the simplest solution, but we already have a the serious hardware for the rest of our webservers. For financial considerations, it doesn&#39;t make sense.

Surely there must be some established solution to this? Am I missing something?



Deploying a production Node.js server

- Should source-maps be used in production environment? Do they provide any benefits other than debugging?
- Do they impact app load time due to the additional server round-trips? Are browsers smart enough to load `.map` assets after app is loaded and rendered?
- If a browser cannot find the `.map` asset (`404` error), would there be performance impact? Should I care about fixing it?

Note that fixing the last one may not be as easy as serving the `.map` assets if there are complicated concat / minify build steps.

Performance impact of using css / javascript source-maps in production?

I&#39;m considering using SQLite as a production database for a site that would receive perhaps 20 simultaneous users, but with the potential for a peak that could be many multiples of that (since the site would be accessible on the open internet and there&#39;s always a possibility that someone will post a link somewhere that could drive many people to the site all at once). 

Is SQLite a possibility? 

I know it&#39;s not an ideal production scenario. I&#39;m only asking if this is within the realm of being a realistic possibility.


SQLite as a production database for a low-traffic site?

I am launching a beta site with a select group of users. I want to disable registration in the production environment only, and only for a short period of time (i.e. I don&#39;t want to nuke my registration altogether). I know I can simply hide the &quot;sign up&quot; link, but I suspect that hackers smarter than I can still use the RESTful routes to accomplish registrations. What&#39;s the best way to disable registration so my test/development environments still work, but production is affected? Thanks for any pointers.

I&#39;ve tried pointing named scopes in such a way that &quot;sign_up&quot; goes to &quot;sign_in&quot;, but it didn&#39;t work. Here&#39;s what I&#39;ve tried:

    devise_scope :user do
        get &quot;users/sign_in&quot;, :to =&gt; &quot;devise/sessions#new&quot;, :as =&gt; :sign_in
        get &quot;users/sign_up&quot;, :to =&gt; &quot;devise/sessions#new&quot;, :as =&gt; :sign_up
    end

Ideally, we&#39;d send the user to a &quot;pages#registration_disabled&quot; page or something like that. I just wanted to get something working I can play around with.

EDIT:
I&#39;ve changed the model as requested, then added the following to /spec/user_spec.rb

    describe &quot;validations&quot; do
        it &quot;should fail registration if in production mode&quot; do
          ENV[&#39;RAILS_ENV&#39;] = &quot;production&quot;
          @user = Factory(:user).should_not be_valid
        end
    end

it is passing as &quot;true&quot; rather than false. Is there a way to mock up the production environment? I&#39;m just spit-balling this one. 

Thanks!

disabling Devise registration for production environment only

Is there a way to automatically use a separate app.config when building in release mode?

In other words, I want to test with one app.config, and release with another.

Currently, I keep a separate copy called app.config.production, and manually overwrite bin\Release\Application.exe.config after building for release.

Visual Studio: differentiate app.config for debug and release mode

I&#39;m using VueCLI 2 and build as production. THe build.js is built and compiled into 200KB. When I re-run the server as development, it loaded 3MB. I&#39;m sure the build.js inside dist folder is 200KB. I tried to open index.html but it doesn&#39;t work and redirect to root directory on website.



**Package.json**

    &quot;scripts&quot;: {
      &quot;dev&quot;: &quot;cross-env NODE_ENV=development webpack-dev-server --open --hot&quot;,
      &quot;build&quot;: &quot;cross-env NODE_ENV=production webpack --progress --hide-modules&quot;
    },
**Webpack**

    module.exports = { ...
    module:{
     ...
     plugins: [
      new webpack.ProvidePlugin({
        $: &#39;jquery&#39;,
        jquery: &#39;jquery&#39;,
        &#39;window.jQuery&#39;: &#39;jquery&#39;,
        jQuery: &#39;jquery&#39;
      })
     ],
     devtool: &#39;#eval-source-map&#39;
    },
    ...
    }

    if (process.env.NODE_ENV === &#39;production&#39;) {
      module.exports.devtool = &#39;#source-map&#39;
      // http://vue-loader.vuejs.org/en/workflow/production.html
      module.exports.plugins = (module.exports.plugins || []).concat([
       new webpack.DefinePlugin({
        &#39;process.env&#39;: {
         NODE_ENV: &#39;&quot;production&quot;&#39;
       }
      }),
      new webpack.optimize.UglifyJsPlugin({
        sourceMap: true,
        compress: {
         warnings: true
        }
      }),
      new webpack.LoaderOptionsPlugin({
        minimize: true
      }),
      new webpack.optimize.CommonsChunkPlugin({
        name: &#39;vendor&#39;,
        minChunks: function (module) {
          return module.context &amp;&amp; module.context.indexOf(&#39;node_modules&#39;) !== -1;
        }
      })
     ])
    }


**HTML**

    &lt;body&gt;
      &lt;script src=&quot;/dist/vendor.js&quot;&gt;&lt;/script&gt;
      &lt;script src=&quot;/dist/main.js&quot;&gt;&lt;/script&gt;
    &lt;/body&gt;

**Command**

&gt; npm run build
&gt;
&gt; npm run dev


All Production Environment Solutions on Gang of Coders

Total of 17 Production Environment Solutions