Jeez, I shouldn’t ask for help when I’m that tired. Thank you … l changed it right away.
Now it does something but it gives me this error:
Error deploying application: Your account is not authorized to deploy to Galaxy.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ddc@ production: `cross-env DEPLOY_HOSTNAME=eu-west-1.galaxy.meteor.com meteor deploy ddcalpha.com --owner Kuroki --settings settings.json`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ddc@ production script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\NERV\AppData\Roaming\npm-cache\_logs\2019-08-28T04_38_51_368Z-debug.log
I logged in with my meteor account, so I’m not sure what the authorization problem could be?
Those are additional settings for MongoDB that are set properly inside the Meteor mongo packages when the connection is initialized. If you left it there you would run into errors.
Not sure why the deploy script is failing. The only strange thing I can see is that there is Node 10 being used, while current Meteor uses Node 8, but in this instance I don’t think that should matter. But since its Windows I have no clue.
Atlas has given you a modern connection string (‘mongodb+srv…’). I’ve had issues with this. In the Atlas UI, there’s an option to get a connection string in an older format. I’d give that a shot. Has helped me in the past.
I either do deployments completely manually on an EC2 instance or use MUP, depending on the project lifetime and scale.
We often do once-off projects that only last a few days or weeks and it’s easier to just whack it up on an existing EC2 with a wildcard DNS record pointing to it.
Things that last a bit longer or will be regularly updated get their own instance and deployed with MUP
For the larger project we’re working on, we’re looking at hosting it on Galaxy when it’s ready
M10 is a size of an instance. You see it when setting size of the container on Atlas.
You can set Galaxy Professional in your deployment settings on Galaxy. The most important thing it gives you is IP whitelisting, which you need for Galaxy and performance monitoring. It is a bit more expensive than Galaxy Essential, but worth it given the increased security and monitoring.
Ah, thanks, thought it was some kind of npm package.
I whitelisted my own IP address in atlas already. I mean, I just want to test my app, it’s not even done yet. I would like to stay on Essential. It almost sounds like I need this pro Level to deploy my app? Since I want to have the costs as low as possible for now, I also want to stay at the Sandbox cluster for now. If this wouldn’t work, I don’t see why that would be an offer.
No, essential works just fine. You won’t have IP addresses to whitelist in Atlas, so you will have to open that to every IP if you want to connect to Atlas from your Galaxy deployment.
I doubt that. Given that they have huge customers, they wouldn’t be able to get away with it.
Would be nice to get to the bottom of this though. Right now I speculate it might be related to oplog and some unrelated traffic that gets send to the app, even though the app has no need for it.
Or it could be something stupid in my app. That is always a possibility.
I noticed that Atlas talked about increases in bandwidth with 4.2 vs 4.0. I’ve just moved to the M10 cluster to begin testing & prepare my app release. I chose not to include the oplog configuration at the time. I’ll keep an eye on the bandwidth billing.
I think the example shared by @ChristopherBate is great. Two things that are worth highlighting from his post:
The "galaxy.meteor.com : { " environment variable has to be at the top of your settings json file - before your public and private configurations.
The connection link that Atlas provides works - just replace username and password with your information and you should be good to go.
With that said, if you need a step-by-step instruction on how to setup Meteor with MongoDB Atlas check out this Fall 2019 course page from the University of Hawaii - start at step 3. From my research, it is the best (i.e. fairly recent and accurate) step-by-step guide on the setup process for Meteor and MongoDB Atlas.