Except, I get “404 Not Found: No applications registered for host” when I visit the URL (and I have checked that my DNS is updated to correctly point at the ingress for meteor), and see no applications on my dashboard when logged in to Galaxy.
I have only the one meteor / galaxy account, so I’m certain I’m logged into the account I’m checking.
Very similar to mine. I verified it was able to locate the settings file by giving it a fake filename instead. It failed to deploy with an error message. Tried removing oplog setting, same result. I’m at a bit of a loss. Considering Modulus.
I haven’t, I didn’t want a trail of instances I needed to drop/destroy afterwards. Hoping someone in support can help figure it out faster than I can deploy elsewhere. I’m quite fond of the idea of deploying/hosting with the group behind the tech I’m using.
I just mean that the command console window, the window that appears when you type “cmd” into the command bar, shows a “Now serving at www.domain.com” after the meteor deploy is complete. No apps show in the Galaxy console/dashboard despite this.
If you are not even seeing the app in your Galaxy console, then the app has not been associated with that account. Is it possible that you have more than one Meteor account? When you signed up for the Galaxy account, did you sign in first with your Meteor developer account?
If I have two accounts, it’s due to some error on Galaxy’s/Meteor’s end. It would be especially troublesome as the second account shares my primary account password and username. (I don’t mean that to sound snarky at all, sorry, I just mean, I’d be shocked as it authenticated using the credentials I use for main account and am not aware of a second)
This often happens when DEPLOY_HOSTNAME=galaxy.meteor.com is not specified in the deployment command. Without that env variable, the deploy will target the Meteor.com free tier, hence you won’t see the app show up in the Galaxy dashboard.
If you are on Windows, the way to set this env variable and deploy is:
$ SET DEPLOY_HOSTNAME=galaxy.meteor.com
$ meteor deploy www.mydomain.com --settings ./settings.json