Check Validity of Instructions / Buttons

[dblythy]

As discussed in this PR, there are a few issues with the current instructions.

As far as I can tell:

-Deploy to AWS button doesn’t work (just creates a new server with “sample code”
-mLab references are obsolete

Assigned to me

[mtrezza]

@mrharsh2804 I looked into this and Heroku does not offer an add-on for MongoDB Atlas as replacement for the obsolete mLab add-on. MongoDB Atlas has to be manually set up to work with Heroku. In short, the Heroku button is obsolete and will be removed.

[dblythy]

Related:

https://community.parseplatform.org/t/cannot-find-the-correct-server-path-after-success-deployment-to-beanstalk/1482/11

[mtrezza]

@dblythy It not just the button / instructions that need to be adapted, I think. It seems the current repo doesn't work out-of-the-box for EB deployment, because in EB the port is assigned automatically, so it's not possible to set the server URL as environment var, because the port is still unknown. A PR for this issue will likely have to address this.

Also, when writing the instructions, we should consider that EB can run with or without a load balancer. I think we should focus on the load balancer scenario, because adding TLS to EB without load balancer is not that simple.

I think the example repo could actually include a EB definition file that includes all the necessary settings. So all one has to do is execute eb deploy and the Parse Server is ready. That could actually substitute the button.

[dblythy]

I'll see how I go. I'll crack in this week and comment here for your advice!