But for the Meteor related projects, nothing beats meteor.com or meteorapp.com domain.
I don’t think a deployed app actually helps with replication. Having the source code of the app so that we can run it locally is the only thing we need for a bug reproduction.
4 Likes
Heroku is really cool for paid apps as well!
To be able to explore some functionality using their free dyno and then later scale up your dyno into a paid one is a very powerful feature. They also have pipelines, with disposable (and free) review apps, to support continuous deployment. Impressive and useful stuff!
I’m not reading the 67 posts of the thread, so I don’t know if someone has suggested this already.
What about a free *.meteor.com instance for every atmosphere package? Demos & documentation for the packages should be hosted by meteor IMHO.
1 Like
That wouldn’t change things. Instead of doing meteor deploy mysite people would do meteor publish mysite-empty-package && meteor deploy mysite.
2 Likes
Hey great news - we’re going to talk about this on the next TRANSMISSION show, with the Meteor and Galaxy project managers, @zoltan and @rohit2b. Show is recording on Friday and will come out next week! Get notified when the show comes out, and help ask questions here:
1 Like
A few package demos that I currently run on meteor.com:
constellation-demo.meteor.com for packages at https://atmospherejs.com/constellation
transactions.meteor.com for https://atmospherejs.com/babrahams/transactions
editable-text-demo.meteor.com for the editable text packages at https://atmospherejs.com/babrahams
1 Like
I have tunguska-gauge-demo.meteor.com and ukgrid.meteor.com for the tunguska:gauge and tunguska:gauge-themes packages.
1 Like
Meteoric
http://meteor-ionic.meteor.com/
http://meteoric-contacts.meteor.com/
http://meteorhunt.meteor.com/
2 Likes
We’ll be working directly with a set of popular package authors behind the demo/doc sites below to migrate their *.meteor.com app to a special instance of Galaxy free of charge. If you see a popular or very useful package demo site missing from this list, you’re welcome to request access and nominate yourself or another contributor’s package demo site.
http://useraccounts.meteor.com
http://viewmodel.meteor.com
http://components.meteor.com
http://autoform.meteor.com
http://user-status.meteor.com
http://autocomplete.meteor.com
http://documents.meteor.com
http://testtut.meteor.com
http://turkserver.meteor.com
http://zf5.meteor.com
http://s-alert-demo.meteor.com
http://s-alert.meteor.com
http://s-grid.meteor.com
http://s-id-demo.meteor.com
http://s-id.meteor.com
http://s-image-box-demo.meteor.com
http://s-image-box.meteor.com
http://fastosphere.meteor.com
http://meteor-react-start-app.meteor.com
http://touch2s.meteor.com
http://components-explorer.meteor.com
http://wikimedia.meteor.com
http://transitions-demo.meteor.com
http://jcplayground.meteor.com
http://messageformat.meteor.com
13 Likes
Please don’t forget about Meteor Icon - http://icon.meteor.com/.
It is being used by many Meteor packages including useraccounts, ryw:blog, and mquandalle:jade. It was also a 2015 Global Distributed Hackathon winner for the best app under 100 lines of JS.
2 Likes
When deploying to Galaxy, should we use the *.meteor.com package hostname as a target hostname?
Almost, it’s actually *.meteorapp.com. e.g.
DEPLOY_HOSTNAME=galaxy.meteor.com meteor deploy <custom.subdomain>.
meteorapp.com --settings path-to-settings.json
And recommended way is to use mlab for MongoDB? The free tier (single-node) does support oplog tailing?
Maybe some instructions how to migrate would be useful. 
1 Like
Please see all the various migration docs & links from the original post on the other thread. The free tier of MLab doesn’t support oplog; you’ll need to use a Shared instance in order to use oplog for your app.
1 Like
Hm, old HTTPS addressed do not work anymore. For example, opening https://wikimedia.meteor.com/ gives me a HTTPS error.
@sashko: just letting you guys know that i find it SOOOOOOOO frustrating that you guys shut down *.meteor.com for all existing BLAZE-packages out there!!! WHAT where you thinking??? You killed years of efforts put into your platform by open-source developers!!!
Just think about all the abandoned but still working & usable packages out there that did NOT make the manual switch. The demo-sites are a BIG PART of the docs - you guys should really really try to find a way to automatically redirect & mirror them to the new meteorapp.com.
Today I searched for some Blaze-packages and 70% still direct to *.meteor.com. 
Do you see a way to automatically redirect & mirror those?
1 Like
@marktrang: I really DO NOT get this. Any developer putting a package out on atmosphere is enhancing your product - for FREE!!! She or he should have access to a free tier for the packages demo-site. At the end of the day, server-load will only add if the package gets popular. Otherwise you will host it, BUT it will NOT take any CPU as there is NO traffik.
So what’s the problem here?
1 Like
I wouldn’t be as aggressive as thebarty but I generally agree, yes it would be nice to have easier access to a package account. We’ve been waiting for one for a while, we’ll probably end up just hosting it ourself now, even with the risk of not being able to pay for it in the future.
I understand though that you would have to pay for AWS instances, so no super bad feelings there.
I really have to agree… a few days I was at a client. We were walking through a project and I said: “Did you look into Meteor-Useraccounts if they have templates for Materialize”? And I checked on the project page… Yeah, they have one! And of course we’d have to take a look how it’d look in materialize. And of course… the link was dead.
That project. It supports seven different frontend frameworks. Seven. Works with both iron-router and flow-router. Has been translated and is readily available to kickstart and secure your next Meteor project in 35 languages out of the box at my current manual count.
There is rarely a package as well-rounded and thought-out and extendable and embeddable and awesome as this one.
Imagine my heartache as I hovered over the link and saw the “*.meteor.com” example links.
This is a real tragedy for all the package authors.
Why not put out a bounty for somebody or an intern to surf through the most popular packages and contact the authors and offer them space on preconfigured galaxy instances?
I think it’d be a good opportunity to show some support for the community.
Just my 9-5 cents, it’s just my opinion and I just wanted to let you know how I feel about that too.