@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?
@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.
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.
I wouldnāt be as aggressive either, because MDG do allow developers to host their open-source projects on Galaxy, just check a few posts back:
So, authors themselves are responsible for deployment to Galaxy and if some app has not been deployed yet, you should check with the author first.
If youāre a developer of an open-source project, you should first contact MDG support and ask if they can host it for you. From my experience, they usually do if a particular project is meaningful to the broader community.
Finally, I canāt say for sure, but Iād say that most (all?) old *.meteor.com links are forwarded to *.meteorapp.com (mine are) which makes more sense anyway.
Not to mention that useraccounts is also pretty dead because they relay on Blaze and now everything has to be migrated to React and nobody has time to do it.
Hi all, new Meteor developer here and eager to help! I was thinking, we all have access to free tiers of AWS, OpenShift and the like. What if we forked some repos and hosted them? If there are packages that are very important, but appear to be dying, perhaps we should work on those first? How can I help?
