(Continuing from [SOLVED] Unable to connect GitHub repo to Meteor Cloud)
I circled back to give this another go, and found it is happening again. I made a new video:
I tried deleting the app from GitHub and starting over, but no luck:
I tried to deploy with CLI instead but that results in an error:
❯ DEPLOY_HOSTNAME=galaxy.meteor.com meteor deploy lume.meteorapp.com
Talking to Galaxy servers at https://galaxy.meteor.com
Preparing to build your app...
Preparing to upload your app...
Uploaded app bundle for new app at lume.meteorapp.com.
Galaxy is building the app into a native image.
Waiting for deployment updates from Galaxy...
Building app image...
Deploying app...
******************************************************************************
ERROR: Failed to deploy new app version: 1.
Galaxy failed to deploy your app. The final deploy status was: Deploy Failed.
Your app is currently stopped.
See https://galaxy.meteor.com/app/lume.meteorapp.com/logs for details.
******************************************************************************
The linked log shows:
Error: MONGO_URL must be set in environment
I am looking at the following, and thinking I don’t want to configure that stuff, I just want good defaults to get going:
It would be nice if deploying the app automatically included a database with a single command (like NodeChef does for Meteor apps).
The pricing on Galaxy says that the free plan offers “Free MongoDB Shared Hosting”. When I look in the “Create Database” UI, I don’t see any free option. The cheapest is $8/mo.
This seems to imply that the free deployment plan should have a free database included (without configuring one manually)?
1 Like
Hey @trusktr, thanks for flagging this!
The UI should show a simple checkbox to add MongoDB to your deployment in the next steps. Since that’s not working for you, I’ll have the team investigate.
The pricing on Galaxy says that the free plan offers “Free MongoDB Shared Hosting”. When I look in the “Create Database” UI, I don’t see any free option. The cheapest is $8/mo.
The free MongoDB is only available for deployments made with Meteor apps right now, and that’s why you’re not seeing it when requesting a new database.
It would be nice if deploying the app automatically included a database with a single command
For Meteor apps, you can deploy with MongoDB in one go:
meteor deploy your-meteor-app.meteorapp.com --free --mongo
Please try using the CLI and let us know if it works. We’ll fix the UI issue and let you know.
2 Likes
Ah, that worked. Thank you! I’ll use that command for now.
I need to figure how to migrate from NodeChef’s DB to this new DB.
I ran the following:
output of DEPLOY_HOSTNAME=galaxy.meteor.com meteor deploy lume.meteorapp.com --free --mongo
Talking to Galaxy servers at https://galaxy.meteor.com
Preparing to build your app...
Preparing to upload your app...
Uploaded app bundle to upgrade lume.meteorapp.com to version 2.
Galaxy is building the app into a native image.
Waiting for deployment updates from Galaxy...
Building app image...
Deploying app...
You have successfully upgraded your app to version 2.
******************************************************************************
Your new mongo URL is
mongodb://xxxxxx:XXXXXXXXXXXXXXXXXX@galaxyadmin_galaxyfreedb-01.mongodb.galaxy-cloud.io:30025,galaxyadmin_galaxyfreedb-02.mongodb.galaxy-cloud.io:30025,galaxyadmin_galaxyfreedb-03.mongodb.galaxy-cloud.io:30025/lume-meteorapp-com?replicaSet=galaxyadmin_galaxyfreedb&ssl=true.
It is a good idea to add this new URL to your app settings ({ "galaxy.meteor.com": { env: { MONGO_URL: "YOUR
MONGO URL" } } }).
******************************************************************************
For details, visit https://galaxy.meteor.com/app/lume.meteorapp.com
A few questions:
- What happens if I don’t save the mongo URL into app settings and run the same command again? I’m guessing it keeps the same DB.
- Is
DEPLOY_HOSTNAME=galaxy.meteor.comrequired? (this doc makes it seem required) - If I change to a non-free plan later, will this command automatically keep including the DB? I’m hoping it keeps the same DB (maybe upgrades it to non-free plan as well?)
- When I visit galaxy UI, I see I have “0” databases. Where can I see and manage this DB?
- I also see a database that I “requested” (not sure what that means yet) a couple days ago, and not sure how to cancel it.
- I’m guessing the trailing period is not part of the URL, as seen in the output, right?
The way it is currently formatted, when selecting text in terminal, most terminals will also select the period as part of the last “word”. An easy fix is to print the URL on its own line.mongodb://xxxxxx:XXXXXXXXXXXXXXXXXX@galaxyadmin_galaxyfreedb-01.mongodb.galaxy-cloud.io:30025,galaxyadmin_galaxyfreedb-02.mongodb.galaxy-cloud.io:30025,galaxyadmin_galaxyfreedb-03.mongodb.galaxy-cloud.io:30025/lume-meteorapp-com?replicaSet=galaxyadmin_galaxyfreedb&ssl=true.
Hey there,
Hope all is well, so here are the answers:
1 - If you repeat the command without including the Mongo uri in your settings, it will use the string saved in your last app version settings.
2 - If you don’t use DEPLOY_HOSTNAME it defaults to galaxy.meteor.com;
3 - It will keep the Mongo connection string of your settings file. If you get a paid database, you will need to update the settings with this new connection string.
4 - These databases shown are only paid databases; we are making continuous improvements to this UI. For instance, you can check inside your app version by expanding the settings.
5 - You can ask for cancel your request on our support chat;
6 - You are right, it’s not part of the URL.
Hope this helps you! Let us know if you have nay further question and feel free to reach us out using the support chat, as well!
Best regards!
1 Like
Ah thanks. It seems this implies a DB migration is required. My wish is that this would not be something I need to worry about. With NodeChef, for example, I don’t have to think about this, I can just deploy an app, and I can later change the auto-scaling parameters without having to think about changing any settings or migrating.
Ah gotcha. That part is a little confusing. Also with NodeChef, when a Meteor app is deployed the DB is automatically added and visible in the list of DBs. It would be intuitive to have the same UI for all DBs regardless if paid or not.
Oh ok. I think I should just be able to cancel in the UI, but I’m sure you’ve thought about this already. I don’t get the purpose of having a “requested” mode. It seems that if I make a DB, it should just be spun up and paid for right away. That’s what all other hosting solutions I’ve tried do.
ok cool. Its easy to miss that period, so may be worth tracking this in an issue, because at some point someone will surely double click the URL, copy/paste it, and it won’t work.
Another Q: do you have a database import feature? That would be very nifty. I didn’t see it, but maybe that’s because the unpaid DB is not listed in UI (item 4 above) and the paid DB I “requested” is not showing me anything more.
I imagine it would be a simple paste of the URL into the UI (f.e. including username:password) and then the rest is automatic.