What if for app demos we had a really easy way to set up a terminal.com free instance? Then you just click a button and you have a demo app running in the browser, and as a bonus you can even mess with the code.
I would say this is a Win Win!
Hereâs my question: back in the day, before Galaxy started and MDG put the ban-hammer on feature requests in GitHub, it was real common to get a simple response from the core team when an issue was submitted: âcan you provide a replication of the bug?â.
That one simple request, and the free hosting tier, spurred a community of developers to work out countless bugs and features. Because we could put together the integration tests, the not-quite-complete-apps, that would let us build more complex apps.
So, with the Galaxy tier⌠do customers need to use their own spot instances for doing bug replications? That seems to me to be a critical question (to me, at least). A lot of the other discussions will follow from how MDG wants to handle community bug replications.
That sounds pretty cool. Like a alrounder meteorpad
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.
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.
That wouldnât change things. Instead of doing meteor deploy mysite
people would do meteor publish mysite-empty-package && meteor deploy mysite
.
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:
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
I have tunguska-gauge-demo.meteor.com and ukgrid.meteor.com for the tunguska:gauge and tunguska:gauge-themes packages.
Meteoric
http://meteor-ionic.meteor.com/
http://meteoric-contacts.meteor.com/
http://meteorhunt.meteor.com/
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
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.
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.
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.
Hm, old HTTPS addressed do not work anymore. For example, opening https://wikimedia.meteor.com/ gives me a HTTPS error.