:sigh: This could have maybe been framed better. A few points:
-
Communicating that no new *.meteor.com deploys are going to be accepted as of March 25th is a much less stressful message to receive than “we’re turning everything off”.
-
This should be framed as the migration go-live for Galaxy; not the ending of the free tier.
-
People aren’t going to make the distinction between *.meteor.com and *.meteorapp.com without leading them through it.
-
If the application database data were kept around for a few months (I’d recommend 3 mo), that would reduce a lot of stress. Not everybody is going to have the time over the next 2 weeks to export their data. Because life.
-
Some people may not even hear about this deprecation until after March 25th.
-
This shouldn’t be too big of a surprise for anybody who’s been paying attention; what with the containers being shutdown automatically and it’s instability of late.
-
If people need to know what applications they’re running, they should use
meteor list-sites. -
Here’s the Database Management page from the Meteor Cookbook with a lot of utilities and recipes for managing mongodumps, mongoexports, re-importing, etc.