Skip to content

Parse Server + MongoDb Backend on AWS #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
NglSR opened this issue Jan 30, 2016 · 19 comments
Closed

Parse Server + MongoDb Backend on AWS #60

NglSR opened this issue Jan 30, 2016 · 19 comments

Comments

@NglSR
Copy link

NglSR commented Jan 30, 2016

Hello guys, thanks for all the inputs on the other Issues posted. Can someone please indicate how to deploy the backend on AWS. I'm new into dev, my app still in development and hosted on Parse. I have been looking a guide or tutorial online since I got the bad news. Thanks in advance.

@NglSR
Copy link
Author

NglSR commented Jan 30, 2016

here an open source backend: http://www.baasbox.com I hope is useful... I don't have use it yet.

@bagusflyer
Copy link

Thanks for your info. But Parse server is also open source now. Why should we use something else we're not familiar. And talking about the cloud service, I'm afraid it will become another parse.com. So my opinion is to trust myself. Maybe host by ourself is better choice.

@NglSR
Copy link
Author

NglSR commented Jan 30, 2016

@bagusflyer thanks.... And sorry for the link above. Do you know the way around deploying Parse Server+Mongodb on AWS?

@mfkenson
Copy link

@NglSR
Copy link
Author

NglSR commented Jan 30, 2016

@mfkenson Thanks Brother, but thats the Heroku parse-server guide. Im looking for the deploy guide on AWS.

@mfkenson
Copy link

@NglSR Under AWS EC2, you can follow the same steps mentioned in "For Local Development".
After you clone the repo, you may edit index.js and set the DATABASE_URI if your mongodb is not installed in the same EC2 instance.

@NglSR
Copy link
Author

NglSR commented Jan 31, 2016

@mfkenson Thanks men... deployed Node, Phyton and Parse Server on AWS... working on MongoDb.

@ihomecall
Copy link

NgISR, I am waiting for you or someone else to publish the whole success steps of migrating parse server to AWS EC2.

@niraj-shah
Copy link

I've created a AWS AMI if anyone wants to use it. It includes MondoDB, NodeJS and the Express example already setup. You just need to edit the /var/www/parse/app.js file with your API keys and run it using node app.js.

The AMI Name is: Parse-Server (located in Europe Ireland) (you can add it using this guide)

@JcMinarro
Copy link

Here is a HowTo Step by Step to create a Parse Server on your own Server.
https://medium.com/@jcminarro/run-parse-server-on-your-own-server-using-digitalocean-b2a7d66e1205#.e33bkf4m3

@gfosco
Copy link
Contributor

gfosco commented Feb 1, 2016

We'll continue working with other providers to create easy ways to launch your own Parse servers and migrate to popular clouds, and we'll blog/tweet/wiki about everything.

@gfosco gfosco closed this as completed Feb 1, 2016
@NglSR
Copy link
Author

NglSR commented Feb 1, 2016

@niraj-shah @JcMinarro @gfosco Thanks for the support.... @niraj-shah can't find the AMI.

@niraj-shah
Copy link

Sorry @NglSR. I forgot to mention the AMI is located in the Europe Ireland region.

@NglSR
Copy link
Author

NglSR commented Feb 1, 2016

@niraj-shah, thanks... Found it. Thanks a lot.

@niraj-shah
Copy link

No worries @NglSR. Also, if you right click on the AMI name and select "Copy AMI", you can copy it any region you want.

@NglSR
Copy link
Author

NglSR commented Feb 1, 2016

@niraj-shah
screen shot 2016-02-01 at 9 17 38 am

@christianmarth
Copy link

You may need to launch a new server from the AMI and create a new image from that instance to copy

@niraj-shah
Copy link

@NglSR Strange! Looks like the AMI can only be created in Europe Ireland. I just tried the Copy AMI option and got the same error. I've updated the EBS permissions and made it public. Copying should work now!

@NglSR
Copy link
Author

NglSR commented Feb 1, 2016

@niraj-shah @christianmarth Guys, thanks a lot.

screen shot 2016-02-01 at 9 35 26 am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants