Local Atmosphere for testing?

[trusktr]

Can I run Atmosphere locally, then tell Meteor to use the local Atmosphere (falling back to the official one when packages aren't found) so I can test how packages work without posting non-working junk on Atmospherejs.com?

[Tarang]

This is no longer possible due to to meteorite's deprecation. This repository's atmosphere is no longer compatible with meteor as well.

Only the official atmospherjs.com system can be used now, which is closed source. Meteor is open source so if you can reverse out the way it works you may be able to change the server somehow, it would be a starting point.

[paralin]

Having any component of the system closed source is a huuugeee turn-off for
a lot of people. In a company, especially, relying on some external closed
source system with no uptime guarantees or security information is a bit of
a flaw.

On Fri, May 29, 2015, 5:33 AM Tarang Patel [email protected] wrote:

This is no longer possible due to to meteorite's deprecation. This
repository's atmosphere is no longer compatible with meteor as well.

Only the official atmospherjs.com system can be used now, which is closed
source. Meteor is open source so if you can reverse out the way it works
you may be able to change the server somehow, it would be a starting point.

Reply to this email directly or view it on GitHub
#108 (comment)
.

[trusktr]

@Tarang That makes things complicated. It's impossible to test package publication without potentially pushing completely broken versions of a package to Atmosphere. I'm making a package where I need to do something in a build plugin before publishing to Atmosphere, then I need further code to do something with that result after the package is downloaded into an app during project build, and the only way (it seems) to test that is by publishing the package in order to test the project-side results.

[Tarang]

@trusktr You may get more help at https://github.com/percolatestudio/atmosphere/issues

You could test the package by building it in /packages right? If it works there the result will be the same as when its published.

[trusktr]

@Tarang Building in packages is not 100% the same as when building outside of a project folder. There's small differences that can only be encountered when building for publishing on Atmosphere from outside a project folder. Thanks for the link! I made the same issue there.