{"action":"opened","issue":{"url":"https://api.github.com/repos/ParsePlatform/parse-dashboard/issues/113","repository_url":"https://api.github.com/repos/ParsePlatform/parse-dashboard","labels_url":"https://api.github.com/repos/ParsePlatform/parse-dashboard/issues/113/labels{/name}","comments_url":"https://api.github.com/repos/ParsePlatform/parse-dashboard/issues/113/comments","events_url":"https://api.github.com/repos/ParsePlatform/parse-dashboard/issues/113/events","html_url":"https://github.com/ParsePlatform/parse-dashboard/issues/113","id":139702480,"number":113,"title":"What are best practices for deployment to production?","user":{"login":"yuzeh","id":351023,"avatar_url":"https://avatars.githubusercontent.com/u/351023?v=3","gravatar_id":"","url":"https://api.github.com/users/yuzeh","html_url":"https://github.com/yuzeh","followers_url":"https://api.github.com/users/yuzeh/followers","following_url":"https://api.github.com/users/yuzeh/following{/other_user}","gists_url":"https://api.github.com/users/yuzeh/gists{/gist_id}","starred_url":"https://api.github.com/users/yuzeh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yuzeh/subscriptions","organizations_url":"https://api.github.com/users/yuzeh/orgs","repos_url":"https://api.github.com/users/yuzeh/repos","events_url":"https://api.github.com/users/yuzeh/events{/privacy}","received_events_url":"https://api.github.com/users/yuzeh/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-09T21:14:39Z","updated_at":"2016-03-09T21:14:39Z","closed_at":null,"body":"Apologies if this question doesn't belong in the right place. Somewhat related to the discussion going on in #102.\r\n\r\nI'm trying to deploy parse-dashboard in production, and would love to know what best practices are, and also how other people are doing this.\r\n\r\nMore specific questions:\r\n* Should it be deployed as a standalone application, or is there a vision to make it mountable on another node application?\r\n* Should we always deploy the latest possible version? Will there be hazards for not being kept up to date? (#102 kind of discusses this)\r\n* Should the client-side assets (JavaScript, CSS) be built on every deploy from source, or will they be provided (pre-built either in the Git repo or on a CDN somewhere)?\r\n* Should the most common deployments for parse-dashboard not require modification of the source code?\r\n\r\nMy current (nonfunctional) deploy process is as follows:\r\n* I maintain a private fork of this repo, which I've modified to\r\n  1. add a health check endpoint, and\r\n  1. edit `npm start` to build the client side assets and put them in the right place before starting the server.\r\n* I am using Elastic Beanstalk for deployment, which essentially zips up the project directory (of my private fork), uploads to a EC2 instance, unzips, and runs `npm start`.\r\n* Requests are HTTPS terminated at the load balancer level, and are sent to the EC2 instance unencrypted."}}