jordansissel / heroku-buildpack-meteor

a heroku buildpack for meteor (meteor.com)
588 stars 264 forks source link

Unable to push projects that are 0.6.0+ #14

Closed dabeeeenster closed 9 years ago

dabeeeenster commented 11 years ago

As per issue #13 unable to use meteor version 0.6.0 or 0.6.1.

adnissen commented 11 years ago

There's a fork which works here: https://github.com/v8squirrel/heroku-buildpack-meteor

It looks like Jordan is waiting for someone to submit a patch to the main repo, and until then is keeping it working with 0.5.9

jordansissel commented 11 years ago

Indeed; I made an attempt this morning to support selectable versions, but the heroku buildpack system isn't capable of that (based on tests). :(

madsmao commented 11 years ago

Meteor 0.6.0 introduces the ability to "lock" the meteor version for any given Meteor project. I have not yet had the chance to poke around to find out where Meteor stores version information for a given project, but it would seem that it should be possible to detect the Meteor version that a given project is locked to and install that particular version of Meteor. However, this will obviously only work for projects based on Meteor 0.6.0+

For 0.5.9 and below this might be useful: https://devcenter.heroku.com/articles/labs-user-env-compile

@jordansissel I'll continue work on my fork, but I won't send any pull requests as long as my code breaks backward compatibility.

adnissen commented 11 years ago

@jordansissel since this is the second time this issue's been opened in the last couple days, it might be useful to link to @madsmao 's fork for 0.6.0 (and 0.6.1 or .2 which came out in the last hour or so) in the readme.

schweigerd commented 11 years ago

hello

i just tried the forked version, but i still cant push it. this is what i get:

ds@linuxmint ~/Workspace/wordplay $ git push heroku master
Counting objects: 18, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (16/16), done.
Writing objects: 100% (18/18), 468.46 KiB | 322 KiB/s, done.
Total 18 (delta 0), reused 0 (delta 0)

-----> Fetching custom git buildpack... done
-----> meteor app detected
Fetching meteor deb package
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 13.6M  100 13.6M    0     0  49.5M      0 --:--:-- --:--:-- --:--:-- 51.8M
Unpacking meteor
Building meteor bundle
Checking for post_compile script
-----> Discovering process types
       Procfile declares types  -> (none)
       Default types for meteor -> web

-----> Compiled slug size: 13.7MB
-----> Launching...
 !     Push rejected, Please verify your account to install this add-on
For more information, see http://devcenter.heroku.com/categories/billing
Verify now at https://heroku.com/verify

To git@heroku.com:damp-castle-9418.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@heroku.com:damp-castle-9418.git'

any idea?

regards

madsmao commented 11 years ago

You need to add a credit card to your account. When running Meteor apps on Heroku, you depend on a Heroku add-on called MongoHQ for your Mongo database. Using that add-on requires you to have a credit card attached to your Heroku account.

schweigerd commented 11 years ago

ok thanks a lot, ill try that :)

jordansissel commented 11 years ago

Think maybe it's time to formerly upgrade this buildpack to use the latest meteor?

wfleming commented 9 years ago

Outdated: buildpack has now been updated for newer Meteors.