Simply log a ticket from Galaxy and the support team will help you out. In terms of account cancellations-- most people are looking for billing to stop so they just stop their apps instead of shutting down their account. We can send you a link to update your credit card information at any time.
I totally respect if you don’t want to answer this, but I’m too curious not to ask .
I’m assuming that MDG evaluated Heroku’s business model and concluded that it wouldn’t work out / be ideal for you?
I’ve used Modulus, Heroku and meteor.com. But not Galaxy yet. I’m curious as to why you’re recommending users to try out Heroku, aren’t you losing business that way? A big part of onboarding a PaaS is to just learn how to use it. Once you know one, you’re not that inclined to switch, unless you’re missing out on something. Herokus feature set is awesome, I must say. What are the unique offerings of Galaxy, why would I learn to use it instead of Heroku?
So we have the 26th of March 2016. People who deploy today on *.meteor.com don’t even get a message that the service is getting shut down. They come to chats and ask for some details on why some particular feature isn’t working on a freshly deployed app, unaware of the fact that the service got officially shut down a day before.
It would be nice if there was such a thing.
Yes, and “meteor deploy” is still documented.
http://docs.meteor.com/#/full/meteordeploy
MDG definitely has a problem with communication.
I understand why they have to remove this feature, the way they manage it is just terrible.
We ran into some speed bumps editing Transmission 10! Hopefully it can come out on Monday.
Basically everyone is really hard at work trying to release Meteor 1.3.
Sorry about the issues in communication. We had expected a lot of the documentation to be updated through the release of Meteor 1.3, but our timing didn’t quite work out. We should have done better; I apologize and thank you for your patience and understanding.
Updated http://status.meteor.com/ as we start shutting down the free tier infrastructure today. As announced initially, Mongo databases can still be accessed until April 15, 2016 12pm PDT.
Fare thee well meteor.com free hosting - thank you so much for your wonderful years of hosting greatness. You will be remembered fondly, and missed dearly …
Server not found. Firefox can't find the server
This is an unfortunate way to deal with shutting down the hosting. I’d expect the “sorry, we’re shutting it down” message instead.
You guys stated that the silent majority of Meteor devs isn’t on the forums. You were right about it - when I tell people to read the details of the shut down on forum, they ask “what forum?”.
But outside of the forums, there wasn’t even a blog post on official website, though such a crucial information should be at the main page. So now the silent majority is coming to chats and asking why are some websites not working, because they weren’t notified about your announcement. Or they are asking what will happen to sites like Fastosphere, because the decision to move these websites to Galaxy wasn’t officially announced.
I know there were emails about the shut down (and it’s good that there were), but for many people they landed in spam folders, some aren’t checking the email, some registered from the email which they use only for registering etc.
see [forum post address] for details.```
That's an improvement, thanks!
But mLab free sandbox is only available with mongo 3.0x which is not working with meteor
Can you elaborate? I’m using a free mlab sandbox for my meteor project right now, and it seems to work just fine. Am I missing something?
Meteor works with Mongo 3.x just fine.
ok. Sorry for confusion then. I thought it has to be 2.6 when working with meteor.
examples are gone for http://handlebar-helpers.meteor.com/
project page: https://github.com/raix/Meteor-handlebar-helpers
@marktrang
Here’s another option for those of you looking for almost free hosting services.
With all the free/cheap and other options pop up after Meteor hosting shut down, it seems that in retrospective, it would be better choice for MDG to make new command instead of all this long story
meteor deploy --location=galaxy
and a way to associate paid Galaxy account with Meteor account.