admithub / meteor-buildpack-horse Goto Github PK

View Code? Open in Web Editor NEW

644.0 35.0 591.0 122 KB

Heroku buildpack for Meteor v1.0+. The horse one.

License: MIT License

Shell 100.00%

meteor-buildpack-horse's Introduction

Meteor Buildpack Horse

A heroku buildpack for Meteor v1+, designed to be as simple and readable as possible.

To use this with your meteor app and heroku:

Set up your app to deploy to heroku with git.
Set your buildpack to the latest version from the registry:
```
 heroku buildpacks:set admithub/meteor-horse
```
Add the MongoLab addon:
```
 heroku addons:create mongolab
```
Set the ROOT_URL environment variable. This is required for bundling and running the app. Either define it explicitly, or enable the Dyno Metadata labs addon to default to https://<appname>.herokuapp.com.
```
 heroku config:set ROOT_URL="https://<appname>.herokuapp.com" # or other URL
```

Once that's done, you can deploy your app using this build pack any time by pushing to heroku:

git push heroku master

Environment

The following are some important environment variables for bundling and running your meteor app on heroku. Depending on your settings, you may need to override these on heroku. See heroku's documentation for how to set these.

ROOT_URL: The root URL for your app, needed for bundling as well as running. If you enable the Dyno Metadata labs addon and ROOT_URL is undefined, it will default to https://<appname>.herokuapp.com).
MONGO_URL: The URL to mongodb. If not defined, it will default the value of MONGODB_URI, MONGOLAB_URI, or MONGOHQ_URL (in order). If you don't use mongolab as a regular addon (and none of the fallbacks are defined), you'll need to set this.
METEOR_APP_DIR: The relative path to the root of your meteor app within your git repository (i.e. the path to the directory that contains .meteor/). The buildpack will look in the root of your repository and app/ subdirectory; if you put your app anywhere else (like src/), define this variable to tell the buildpack where to look.
BUILDPACK_PRELAUNCH_METEOR: If your app uses packages that need to compile their assets on first run, you may need meteor to launch prior to bundling. If this applies for you, define BUILDPACK_PRELAUNCH_METEOR=1. Reference issue.
BUILDPACK_VERBOSE: Set BUILDPACK_VERBOSE=1 to enable verbose bash debugging during slug compilation. Only takes effect after the environment variables have been loaded.
BUILDPACK_CLEAR_CACHE: This buildpack stores the meteor installation in the CACHE_DIR to speed up subsequent builds. Set BUILDPACK_CLEAR_CACHE=1 to clear this cache on startup and after build is done.
BUILD_OPTIONS: Set to any additional options you'd like to add to the invocation of meteor build, for example --debug or --allow-incompatible-update.
NODEJS_PARAMS: additional parameters for running node binary. This can be used eg. for adjusting garbage collector settings by putting --optimize_for_size --max_old_space_size=460 --gc_interval=100 here

Extras

The basic buildpack should function correctly for any normal-ish meteor app, with or without npm-container. For extra steps needed for your particular build, just add shell scripts to the extra folder and they will get sourced into the build.

Extras included in this branch:

mongo_url.sh: If MONGO_URL is empty, set it to the value of MONGODB_URI, MONGOLAB_URI, or MONGOHQ_URL (in order).
root_url.sh: If ROOT_URL is empty and HEROKU_APP_NAME is available, set ROOT_URL to https://$HEROKU_APP_NAME.herokuapp.com

Where things go

This buildpack creates a directory .meteor/heroku_build ($COMPILE_DIR) inside the app checkout, and puts all the binaries and the built app in there. So it ends up having the usual unixy bin/, lib/, share etc subdirectories. Those directories are added to $PATH and $LD_LIBRARY_PATH appropriately.

So $COMPILE_DIR/bin etc are great places to put any extra binaries or stuff if you need to in custom extras.

Using the latest buildpack code

The admithub/meteor-horse buildpack from the Heroku Registry contains the latest stable version of the buildpack. If you'd like to use the latest buildpack code from this Github repository, you can set your buildpack to the Github URL:

    heroku buildpacks:set https://github.com/AdmitHub/meteor-buildpack-horse

Tips & Tricks

Please help us add tips and tricks to the wiki for further help, like usage with Dokku or other environments.

Why horse?

There are a gazillian forks and branches of various buildpacks remixing the words "heroku", "buildpack", and "meteor", many of which are abandoned or outdated or broken, and it's really hard to keep them straight.

So this one is the horse one.

README image credit: wikicommons contributor Arsdelicata

meteor-buildpack-horse's People

Contributors

Stargazers

Watchers

Forkers

djhi whimdatingapp devcare occasl typeofgraphic llama anthonymayer carlesso nxpeacock colllin jurikern mercuryrising acechris queso riso nigelng okgrow henrikgs hvtor bensonnjonjo artsandideas derrickjames dalloro ewindso markdowney risul yourcelf f3rnandomoreno kozy agradipyahoo paralin robertlowe polyomino chatr peryaudo benmgreene hanouman vincilbishop manuelmateus16 jasonburt maxko87 alexzaporozhets adeelraza samjoch cwattrus bouncingto kannans roddle biguhq harshjv gaboesquivel daz2345 paludetto nicolaslopezj ukabu rocketchat alveoli shepelt abstractaab ssathy2 everhusk creativej bogdanrn hristaki dmplutenko forwarder tdenovan derekclair dheerajbhaskar dominikmayer simonv3 dashersw stepri allanriffert lvelours wonderkiln dnswus lpender elenoar oneupcompany alykoshin johnhbenetech emadurandal nathando347 marvelicy vandretti codefabric hashlabs ondrej-kvasnovsky jsbranco wdk122 buo excalliburbd maka-io kengoldfarb sampaiodiego thedracle awear thiagoc7 flevour

meteor-buildpack-horse's Issues

Push rejected, failed to compile Node.js app

I got this when pushing to Heroku. It doesn't look related to the MongoHQ issue.

Any idea?
Thanks

Push rejected, failed to compile Node.js app

I keep getting this error. I already have committed to my local repo and the log is as follows. Seems the temporary file created states "mv can not stat", resulting in the error.

https://gist.github.com/jmwenda/2a9f6d9686a2a1080d40

What could be the problem?

unknown package: isobuild:compiler-plugin

getting the error unknown package: isobuild:compiler-plugin on heroku

Using to connect to PostgreSQL database

Can this buildpack be used to connect to PostgreSQL (with use of numtel/pg package)

meteor restart on heorku

Does somebody knows how can I do meteor restart on heroku?

someting like

heroku run meteor restart

Detemine meteor version from .meteor/release

The buildpack currently installs the latest production version of Meteor.

This causes a problem because if a developer is using a beta version (such as a 1.3 beta), the buildpack ignores the version of Meteor that the developer developed for and uses 1.2.1, which is the latest production version.

It'd be better if the meteor version were determined based on the version specified in ./meteor/release Example: https://github.com/jordansissel/heroku-buildpack-meteor/blob/master/bin/compile_meteor#L23

Integrating wkhtmltopdf in Heroku?

How would you combine a second Heroku buildpack into this buildpack : https://github.com/dscout/wkhtmltopdf-buildpack ?

I'm hoping to use wkthmltopdf in Heroku to render PDFs.

Push Rejected

remote: sh: 0: Can't open /tmp/build_ea59c436880c95874118ec9130918be3/packages/rocketchat-livechat/plugin/build.sh
remote:
remote: /tmp/buildpack20160113-159-1l8sp7j/meteor-xkbL/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/fibers/future.js:245
remote: throw(ex);
remote: ^
remote: Error: Builder can not write without either data or a file path or a symlink path: os/packages/rocketchat_livechat/public/head.html
remote: at Builder.write (/tools/isobuild/builder.js:225:13)
remote: at Builder.writeToGeneratedFilename (/tools/isobuild/builder.js:353:10)
remote: at /tools/isobuild/isopack.js:1346:27
remote: at Array.forEach (native)
remote: at Function..each..forEach (/tmp/buildpack20160113-159-1l8sp7j/meteor-xkbL/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/underscore/underscore.js:79:11)
remote: at .each..each.builder.generateFilename.directory (/tools/isobuild/isopack.js:1320:11)
remote: at Array.forEach (native)
remote: at Function..each..forEach (/tmp/buildpack20160113-159-1l8sp7j/meteor-xkbL/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/underscore/underscore.js:79:11)
remote: at /tools/isobuild/isopack.js:1233:9
remote: at [object Object]..extend.saveToPath (/tools/isobuild/isopack.js:1585:26)
remote: at /tools/isobuild/isopack-cache.js:289:23
remote: at /tools/utils/buildmessage.js:356:18
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at /tools/utils/buildmessage.js:349:34
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at /tools/utils/buildmessage.js:347:23
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at Object.enterJob (/tools/utils/buildmessage.js:321:26)
remote: at [object Object]..extend.loadLocalPackage (/tools/isobuild/isopack-cache.js:227:18)
remote: at /tools/isobuild/isopack-cache.js:166:14
remote: at /tools/utils/buildmessage.js:356:18
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at /tools/utils/buildmessage.js:349:34
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at /tools/utils/buildmessage.js:347:23
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at Object.enterJob (/tools/utils/buildmessage.js:321:26)
remote: at [object Object]..extend.ensurePackageLoaded (/tools/isobuild/isopack-cache.js:158:20)
remote: at /tools/isobuild/isopack-cache.js:73:14
remote: at /tools/packaging/package-map.js:57:7
remote: at Function..each..forEach (/tmp/buildpack20160113-159-1l8sp7j/meteor-xkbL/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/underscore/underscore.js:87:22)
remote: at [object Object]..extend.eachPackage (/tools/packaging/package-map.js:49:7)
remote: at [object Object]..extend.buildLocalPackages (/tools/isobuild/isopack-cache.js:72:24)
remote: at /tools/project-context.js:735:25
remote: at /tools/utils/buildmessage.js:356:18
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at /tools/utils/buildmessage.js:349:34
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at /tools/utils/buildmessage.js:347:23
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at Object.enterJob (/tools/utils/buildmessage.js:321:26)
remote: at ProjectContext..extend.buildLocalPackages (/tools/project-context.js:734:18)
remote: at /tools/project-context.js:257:35
remote: at /tools/utils/buildmessage.js:356:18
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at /tools/utils/buildmessage.js:349:34
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at /tools/utils/buildmessage.js:347:23
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at Object.enterJob (/tools/utils/buildmessage.js:321:26)
remote: at ProjectContext..extend.completeStagesThrough (/tools/project-context.js:247:18)
remote: at ProjectContext..extend.saveChangedMetadata (/tools/project-context.js:235:10)
remote: at ProjectContext..extend.prepareProjectForBuild (/tools/project-context.js:240:10)
remote: at /tools/cli/commands.js:838:20
remote: at /tools/utils/buildmessage.js:268:13
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at /tools/utils/buildmessage.js:261:29
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at /tools/utils/buildmessage.js:259:18
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at /tools/utils/buildmessage.js:250:23
remote: at [object Object]..extend.withValue (/tools/utils/fiber-helpers.js:114:14)
remote: at Object.capture (/tools/utils/buildmessage.js:249:19)
remote: at Object.main.captureAndExit (/tools/cli/main.js:270:29)
remote: at buildCommand (/tools/cli/commands.js:837:8)
remote: at Command.main.registerCommand..extend.name as func
remote: at /tools/cli/main.js:1378:23
remote:
remote: ! Push rejected, failed to compile Node.js app
remote:
remote: Verifying deploy....
remote:
remote: ! Push rejected to penguin-khandelwal.
remote:
To https://git.heroku.com/penguin-khandelwal.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/penguin-khandelwal.git'

bash: .meteor/heroku_build/bin/node: No such file or directory (for Iron apps)

This buildpack works great for regular meteor apps, such as the todos examples. I got that working and can make changes, commit, push, and the app still works.

But for apps generating using Iron CLI, the website is only accessible on the first push, if I'm lucky. I've tested this with a bunch of little apps. Any push after the first causes this error:

HTML page error:

Application Error
An error occurred in the application and your page could not be served. Please try again in a few moments.
If you are the application owner, check your logs for details.

The heroku logs shows:

2015-06-12T22:38:05.433576+00:00 heroku[web.1]: State changed from crashed to starting
2015-06-12T22:38:08.025035+00:00 heroku[web.1]: Starting process with command `.meteor/heroku_build/bin/node .meteor/heroku_build/app/main.js`
2015-06-12T22:38:09.388371+00:00 app[web.1]: bash: .meteor/heroku_build/bin/node: No such file or directory
2015-06-12T22:38:10.070487+00:00 heroku[web.1]: State changed from starting to crashed
2015-06-12T22
:38:10.071527+00:00 heroku[web.1]: State changed from crashed to starting
2015-06-12T22:38:10.050633+00:00 heroku[web.1]: Process exited with status 127
2015-06-12T22:38:13.248325+00:00 heroku[web.1]: Starting process with command `.meteor/heroku_build/bin/node .meteor/heroku_build/app/main.js`
2015-06-12T22:38:15.256277+00:00 app[web.1]: bash: .meteor/heroku_build/bin/node: No such file or directory
2015-06-12T22:38:16.155231+00:00 heroku[web.1]: State changed from starting to crashed
2015-06-12T22:38:16.144090+00:00 heroku[web.1]: Process exited with status 127

The important part is: bash: .meteor/heroku_build/bin/node: No such file or directory

This is the workflow I was using:

iron create myapp
cd myapp
heroku login
heroku create myapp
heroku config:set BUILDPACK_URL=https://github.com/AdmitHub/meteor-buildpack-horse.git
heroku config:set ROOT_URL=http://myapp.herokuapp.com
git push heroku master

I'm not sure what is going wrong here.

Compress js and css files after build

Right now the buildpack is working really nice for me, but my site loads up a lot of js files and css files and even in uncompressed form which takes it a lot of time to load. So I was thinking if this build pack could compress the files I could put them in the cdn and manage my website much faster.

Is there any easy way to do this?

Routing problems after deploying on Heroku

I have been investigating Heroku as a host for Meteor apps and decided to use the horse buildpack to get everything set up. I followed the instructions and my logs show that the app was successfully deployed to Heroku (https://swapp-materialize.herokuapp.com). However, when you visit the home page it just shows the Iron Router intro page.. I am not sure what I did wrong here but I'd appreciate it if you could shed some light on the issue for me.

Also, Heroku logs look fine... Here is a sample.

2015-04-21T22:11:25.823841+00:00 heroku[router]: at=info method=GET path="/packages/materialize_materialize/font/roboto/Roboto-Regular.woff2" host=swapp-materialize.herokuapp.com request_id=0faf3729-961f-4d75-a493-63c94da9b076 fwd="45.56.15.15" dyno=web.1 connect=2ms service=8ms status=200 bytes=49532
2015-04-21T22:11:25.917391+00:00 heroku[router]: at=info method=GET path="/sockjs/info?cb=6vizpc342l" host=swapp-materialize.herokuapp.com request_id=94da4675-9dfe-4bef-9024-d1bfb2ad0ad2 fwd="45.56.15.15" dyno=web.1 connect=3ms service=3ms status=200 bytes=348
2015-04-21T22:11:26.939942+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=swapp-materialize.herokuapp.com request_id=b8c993c3-4173-47e8-9b08-59727c5c3d30 fwd="45.56.15.15" dyno=web.1 connect=1ms service=3ms status=404 bytes=138
2015-04-21T22:11:38.182115+00:00 heroku[router]: at=info method=GET path="/sockjs/852/ijpqobo1/websocket" host=swapp-materialize.herokuapp.com request_id=4653d567-b53a-4ba6-b3c0-87a5ddc0f497 fwd="45.56.15.15" dyno=web.1 connect=2ms service=12055ms status=101 bytes=1046
2015-04-21T22:14:17.757603+00:00 heroku[router]: at=info method=GET path="/" host=swapp-materialize.herokuapp.com request_id=ff8efede-0bf0-4210-9703-ab12063f70e8 fwd="45.56.15.15" dyno=web.1 connect=0ms service=11ms status=200 bytes=1168
2015-04-21T22:14:18.135921+00:00 heroku[router]: at=info method=GET path="/1793cc6c2fc668c9ae9070e7f50730aa4e529bd1.css?meteor_css_resource=true" host=swapp-materialize.herokuapp.com request_id=f2896840-fb90-4198-b8c0-6bea2420c4a4 fwd="45.56.15.15" dyno=web.1 connect=2ms service=28ms status=200 bytes=24636
2015-04-21T22:14:18.187577+00:00 heroku[router]: at=info method=GET path="/f0d9a08d85f3c9fa6759423e9cce53b629c038b3.js" host=swapp-materialize.herokuapp.com request_id=093ead39-97d8-4207-b744-a7fa132d11b6 fwd="45.56.15.15" dyno=web.1 connect=0ms service=80ms status=200 bytes=207475
2015-04-21T22:14:18.799336+00:00 heroku[router]: at=info method=GET path="/packages/materialize_materialize/font/roboto/Roboto-Regular.woff2" host=swapp-materialize.herokuapp.com request_id=fedd5c72-2988-4ce8-8323-7fe90f1c7c4d fwd="45.56.15.15" dyno=web.1 connect=1ms service=13ms status=200 bytes=49532
2015-04-21T22:14:18.915338+00:00 heroku[router]: at=info method=GET path="/sockjs/info?cb=r1wu_p_e4c" host=swapp-materialize.herokuapp.com request_id=f9925c79-b52d-4d2a-9447-84566957ec3b fwd="45.56.15.15" dyno=web.1 connect=4ms service=4ms status=200 bytes=349
2015-04-21T22:14:19.023061+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=swapp-materialize.herokuapp.com request_id=eaf385fd-ec57-45b7-a6d1-2a74737f3eba fwd="45.56.15.15" dyno=web.1 connect=1ms service=3ms status=404 bytes=138
2015-04-21T22:14:57.361292+00:00 heroku[router]: at=info method=GET path="/" host=swapp-materialize.herokuapp.com request_id=2c4a4b1c-b377-4d2b-80c1-6c2d4ec83f50 fwd="45.56.15.15" dyno=web.1 connect=16ms service=21ms status=200 bytes=1168
2015-04-21T22:14:57.484363+00:00 heroku[router]: at=info method=GET path="/sockjs/937/zd2b1gic/websocket" host=swapp-materialize.herokuapp.com request_id=3fec3070-54ce-4a5b-9cb4-2eccc8e9b789 fwd="45.56.15.15" dyno=web.1 connect=2ms service=38398ms status=101 bytes=129
2015-04-21T22:14:58.063148+00:00 heroku[router]: at=info method=GET path="/sockjs/info?cb=p4lb52df2y" host=swapp-materialize.herokuapp.com request_id=eba529ce-8454-4b2b-af59-bc0795746ab3 fwd="45.56.15.15" dyno=web.1 connect=5ms service=11ms status=200 bytes=349
2015-04-21T22:15:17.694887+00:00 heroku[router]: at=info method=GET path="/sockjs/548/uffaqcih/websocket" host=swapp-materialize.herokuapp.com request_id=142c07ae-1bfa-4625-bb6e-ad9bd1171109 fwd="45.56.15.15" dyno=web.1 connect=1ms service=19322ms status=101 bytes=129
2015-04-21T22:19:07.091234+00:00 heroku[router]: at=info method=GET path="/" host=swapp-materialize.herokuapp.com request_id=6a978d3e-d189-41e9-ab08-5a9ace8fecf5 fwd="45.56.15.15" dyno=web.1 connect=2ms service=4ms status=200 bytes=1168
2015-04-21T22:19:07.774058+00:00 heroku[router]: at=info method=GET path="/sockjs/info?cb=t7dl5xzkbs" host=swapp-materialize.herokuapp.com request_id=91d43af5-d75a-4778-a976-c55d3f360da3 fwd="45.56.15.15" dyno=web.1 connect=2ms service=3ms status=200 bytes=348

Here is the Git repo: https://github.com/ryanswapp/swapp-materialize

Migrate to the celadon cedar-14 stack required

Found that prior to git push heroku master following is required:

heroku stack:set cedar-14

Push rejected / pre-receive hook declined / failed to push some refs

Getting this errors after trying to push any meteor project to heroku:

remote: ----->  app detected
remote: -----> Installing node
remote: -----> Installing meteor
...
remote: -----> Compressing... done, 22.2MB
remote: -----> Launching... 
remote:  !     Push failed: error creating release
remote: Verifying deploy...
remote: !   Push rejected
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs

It used to work some weeks ago. Any idea?

Support for GraphicsMagick

Can I submit a PR with an extra optional script to add support to http://www.graphicsmagick.org/ ?

Latest commit broke my build

Getting this error on build after this commit bad37c4

I'm using Meteoric and have set BUILDPACK_PRELAUNCH_METEOR to 1 to get around this issue meteor/meteor#2796 as noted at https://github.com/meteoric/ionic-sass but looks like this is no longer working as a workaround.

-----> Building Meteor with ROOT_URL: https://myapp.herokuapp.com/
The iOS platform is not installed; skipping build for it.
Errors prevented bundling:
While building the application:
/tmp/build_63d6acf628976f4a375615fc39cfad54/app/client/stylesheets/main.scss:149:9:
Scss compiler error: file to import not found or unreadable:
.meteor/local/build/programs/server/assets/packages/meteoric_ionic-sass/ionic
Current dir:
/tmp/build_63d6acf628976f4a375615fc39cfad54/app/client/stylesheets/
! Push rejected, failed to compile Node.js app

Error using BUILDPACK_PRELAUNCH_METEOR workaround

I'm getting the following error when setting the BUILDPACK_PRELAUNCH_METEOR variable on heroku:

error: ios: platform is not in this project
error: android: platform is not in this project

Why is the remove-platform command required when using this option?

Update METEOR_SETTINGS at end of build process

Would it be possible to run this command at the end of the build process?

heroku config:set METEOR_SETTINGS="$(cat config/production/settings.json)"

This updates the app to use the settings file contained in the newly deployed version of the app.

Currently, an app will continue to use the old settings and this has to be run manually after every deploy to get it to use the new settings file. This can cause a moment of site breakage between when the app finishes building and deploying and when the dev can run this command if there were changes to the settings file.

This is the standard settings file location for Iron CLI apps.

Does this buildpack require enabling session affinity?

I know with other build packs you have to enable heroku's session affinity.... was wondering if that was the case for this buildpack as well.

Push rejected, Please verify your account to install this add-on plan

Background

I didn't want to add a credit card because I wanted to use the mongolab free plan. I went to mongolab, signed up for a free account and put the proper mongo URL in the config vars. Still got the above error.

Steps followed

Verbatim what was given in the README.md

Error

Push rejected, Please verify your account to install this add-on plan (please enter a credit card) For more information, see https://devcenter.heroku.
com/categories/billing Verify now at https://heroku.com/verify

Expected behavior

The app to build and deploy properly.

Temp Worakround

I then changed the buildpack to https://github.com/jordansissel/heroku-buildpack-meteor.git and it worked.
May be there's something they're doing that's not in this buildpack? The reason I'm reporting this issue is because I understand that this repo is maintained more actively.

Feel free to ask for more details

meteor authentication not working for heroku deploy

I've deployed my iron-cli meteor app to heroku using this buildpack. The app shows up (here) but I cannot log in using meteor developer accounts.

I get the error " Something went wrong: that application does not exist."

I added redirect urls:

And I also created a file config/production/env.sh where I have:

export ACCOUNTS_METEOR_ID='<my-app-id>'
export ACCOUNTS_METEOR_SECRET='<my-secret-key>'

In app/server/bootstrap.js I specify:

ServiceConfiguration.configurations.upsert(
  { service: 'meteor-developer' },
  {
    $set: {
      clientId: process.env['ACCOUNTS_METEOR_ID'],
      secret: process.env['ACCOUNTS_METEOR_SECRET'],
      loginStyle: 'popup'
    }
  }
);

This all follows the setup from the eventedmind screencast. How can I get authentication working in production with heroku?

License?

I don't see a license file on this project but sure would like to use it. Could I get permission to use it or can you add a favorable license to such as MIT?

Force-SSL

How do we enable this package's functionality on Heroku?

Buildpack is broken

Mar 30 14:54:53 libertyads-pr-43 heroku/web.1:  State changed from crashed to starting 
Mar 30 14:54:56 libertyads-pr-43 heroku/web.1:  Starting process with command `app/.meteor/heroku_build/bin/node app/.meteor/heroku_build/app/main.js` 
Mar 30 14:54:57 libertyads-pr-43 app/web.1:  bash: app/.meteor/heroku_build/bin/node: No such file or directory 
Mar 30 14:54:58 libertyads-pr-43 heroku/web.1:  State changed from starting to crashed 
Mar 30 14:54:58 libertyads-pr-43 heroku/web.1:  Process exited with status 127

Meteor fails to start after build

Hi folks,

I am having some issues launching my meteor app after the build.

Locally works fine and I am able to push successfully as well (with the build completing as per normal).

But once I attempt to open the link of the application in my server, I get a 404 as if the application was offline.

I decided to manually launch it within the Docker container and this is the error I see:

his project is already at Meteor 1.2.1, the latest release.

/root/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/fibers/future.js:245
throw(ex);
^
Error: EXDEV, rename '/app/.meteor/local/isopacks/npm-container'

Has anyone faced this before?

Use MongoLab instead of MongoHQ

Compose (MongoHQ) doesn't have a free version anymore, so I suggest change to MongoLab.

Facebook auth with custom domains not working

I'm having a problem on trying to authenticate with facebook with different domains. It works just with the domain specified in ROOT_URL variable. That means, my user only can use facebook login in domain with www (if the ROOT_URL is http://www.mydomain.com ) or without the www (if the ROOT_URL is http://mydomain.com)

I'm getting the following error message:

SecurityError: Blocked a frame with origin "http://www.mydomain.com.br" from accessing a frame with origin "http://mydomain.com.br". Protocols, domains, and ports must match.

All the possible callback urls are specified in advanced settings on facebook. This is an error maybe on meteor facebook package but I'm looking for some help here too.

Installing TypeScript

I'm trying to get the TypeScript compiler running on Heroku. So far I'm lost because I don't know how to install typescript as a dependency.

At first I put typescript as a devDependency in a package.json. I tried to put that in the root as well as the server directory.

Now I forked the repository and hardcoded npm install -g typescript which also doesn't work:

[…]
remote: Compiling TypeScript web.browser files...
remote: Errors prevented bundling:
remote: While building the application:
remote: 
remote: /tmp/build_ac7fb7c1f5d49d44191a629501dbcaf5/lib/typescript/custom_defs/collections.ts:1:1:
remote: error TS6053: File
remote: '/tmp/build_ac7fb7c1f5d49d44191a629501dbcaf5/lib/typescript/package_defs/all-definitions.d.ts'
remote: not found.
[…]

What is the proper way to add TypeScript (or any other npm module)?

Push rejected, failure creating release

Hi,

I'm for the first time trying to deploy a Meteor app to Heroku. I just started out with the todos example, added the buildpack and tried to push the comitted code. Everything seems to go fine, but somehow the push is rejected and the build fails.

Rick:todos rkplas$ git push heroku master
Counting objects: 113, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (108/108), done.
Writing objects: 100% (113/113), 247.42 KiB | 0 bytes/s, done.
Total 113 (delta 3), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote: 
remote: -----> Fetching custom git buildpack... done
remote: -----> Node.js app detected
remote: -----> Installing node
remote: -----> Installing meteor
remote: Downloading Meteor distribution
remote: ######################################################################## 100.0%
remote: 
remote: Meteor 1.0.2.1 has been installed in your home directory (~/.meteor).
remote: 
remote: Now you need to do one of the following:
remote: 
remote:   (1) Add "$HOME/.meteor" to your path, or
remote:   (2) Run this command as root:
remote:         cp "/tmp/buildpack_60aea2829a59bc7586e9d5738213406b/meteor-eDih/.meteor/packages/meteor-tool/1.0.38/meteor-tool-os.linux.x86_64/scripts/admin/launch-meteor" /usr/bin/meteor
remote: 
remote: Then to get started, take a look at 'meteor --help' or see the docs at
remote: docs.meteor.com.
remote: -----> Bundling bundle
remote: ios: removed platform
remote: android: removed platform
remote: npm WARN package.json [email protected] No description
remote: npm WARN package.json [email protected] No repository field.
remote: npm WARN package.json [email protected] No README data
remote: 
remote: > [email protected] install /tmp/build_60aea2829a59bc7586e9d5738213406b/.meteor/heroku-build/app/programs/server/node_modules/fibers
remote: > node ./build.js
remote: 
remote: `linux-x64-v8-3.14` exists; testing
remote: Binary is fine; exiting
remote: [email protected] node_modules/underscore
remote: 
remote: [email protected] node_modules/semver
remote: 
remote: [email protected] node_modules/chalk
remote: ├── [email protected]
remote: ├── [email protected]
remote: ├── [email protected]
remote: ├── [email protected] ([email protected])
remote: └── [email protected] ([email protected])
remote: 
remote: [email protected] node_modules/eachline
remote: └── [email protected]
remote: 
remote: [email protected] node_modules/source-map-support
remote: └── [email protected] ([email protected])
remote: 
remote: [email protected] node_modules/fibers
remote: -----> Adding PATH environment
remote: -----> Running extras
remote: -----> Adding MONGOHQ_URL -> MONGO_URL env
remote: -----> Adding MONGOLAB_URI -> MONGO_URL env
remote: -----> Installing phantomjs.
remote: -----> Discovering process types
remote:        Procfile declares types   -> (none)
remote:        Default types for Node.js -> web
remote: 
remote: -----> Compressing... done, 26.4MB
remote: -----> Launching... 
remote:  !     Push rejected, failure creating release
remote: 
remote: Verifying deploy...
remote: 
remote: !   Push rejected to salty-tundra-1782.
remote: 
To https://git.heroku.com/salty-tundra-1782.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/salty-tundra-1782.git'

Quick fix for broken Meteor installation script

At this moment Meteor Installation Script is broken #5445: meteor/meteor#5445
Running curl https://install.meteor.com/ | sh returns the following
The requested URL returned error: 404 Not Found

For everyone who need to deploy the app while Meteor team not yet fixed the issue, the quick fix of the buildpack using script provided in the issue:
https://github.com/alykoshin/meteor-buildpack-horse-1202-fixed

Please, do not forget revert back the url to original buildpack when the issue will be fixed to follow official Meteor versions.

Error compiling Android App

I get this when pushing my app to Heroku:

remote: => Errors executing Cordova commands:
remote:
remote:    While building Cordova app for platform Android:
remote:    Error:
remote:    /tmp/build_d85893373430c73497ef5153d1f6a7d2/.meteor/local/cordova-build/platforms/android/cordova/build:
remote:    Command failed with exit code 2 Error output:
remote:    [Error: Failed to find 'ANDROID_HOME' environment variable. Try setting
remote:    setting it manually.
remote:    Failed to find 'android' command in your 'PATH'. Try update your 'PATH' to
remote:    include path to valid SDK directory.]
remote:    at ChildProcess.whenDone
remote:    (/tmp/buildpack_d85893373430c73497ef5153d1f6a7d2/meteor-76BW/.meteor/packages/meteor-tool/.1.1.9.ltydx3++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/
cordova-lib/src/cordova/superspawn.js:139:23)
remote:    at ChildProcess.emit (events.js:98:17)
remote:    at maybeClose (child_process.js:766:16)
remote:    at Process.ChildProcess._handle.onexit (child_process.js:833:5)
remote:
remote:
remote:  !     Push rejected, failed to compile Node.js app

I don't believe it's necessary to build for platforms other than browser and server when pushing to Heroku is it?

Perhaps there should be a build step that overrides the .meteor/platforms file. This would save time and prevent errors.

meteor/meteor#2867

Thanks!

-Lee

"This version of npm lacks support for important features" when pushing to heroku

When I am pushing my code to heroku (git push heroku master), I get this WARN:

remote: -----> Bundling bundle
remote: -----> Building Meteor with ROOT_URL: https://batmobile.herokuapp.com
remote: npm WARN deprecated This version of npm lacks support for important features,
remote: npm WARN deprecated such as scoped packages, offered by the primary npm
remote: npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the
remote: npm WARN deprecated latest stable version. To upgrade to npm@2, run:
remote: npm WARN deprecated 
remote: npm WARN deprecated   npm -g install npm@latest-2
remote: npm WARN deprecated 
remote: npm WARN deprecated To upgrade to the latest stable version, run:
remote: npm WARN deprecated 
remote: npm WARN deprecated   npm -g install npm@latest
remote: npm WARN deprecated 
remote: npm WARN deprecated (Depending on how Node.js was installed on your system, you
remote: npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
remote: npm WARN deprecated on Windows, run them from an Administrator prompt.)
remote: npm WARN deprecated 
remote: npm WARN deprecated If you're running the version of npm bundled with
remote: npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
remote: npm WARN deprecated will be bundled with a version of npm@2, which has some small
remote: npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
remote: npm WARN deprecated semver behavior.
remote: npm WARN package.json [email protected] No description
remote: npm WARN package.json [email protected] No repository field.
remote: npm WARN package.json [email protected] No README data

I am using:
Meteor 1.2.1
NPM 2.14.14
Node 5.2.0

How can I solve this?

(I am relatively new to both Node and Meteor, so please let me know; and I will provide you with more information if needed :) )

Support for 1.3 (modules)

Because Meteor 1.3 includes NPM support, npm install might be required on the project repo. Are you planning on implementing support for that?

One possible issue might be that the project itself is using a newer NPM than included with the Nodejs version required by Meteor.

Why remove ios and android platform?

Why you remove ios and android platform?
https://github.com/AdmitHub/meteor-buildpack-horse/blob/master/bin/compile#L78

Hangs during "Downloading Meteor distribution"

I've been using this buildpack for months without problem. But today, when trying to git push heroku master, I can't get past around ~16% during the "Downloading Meteor distribution" step:

Counting objects: 9, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (9/9), done.
Writing objects: 100% (9/9), 1.20 KiB | 0 bytes/s, done.
Total 9 (delta 7), reused 0 (delta 0)
remote: Git submodules detected, installing:
remote: Submodule path 'packages/accounts-entry': checked out 'bc13810c0ee60b7608621a28ad203553e70c2ae1'
remote: Submodule path 'packages/chosen-package': checked out '1a3336a08702c02329f43d3950112d8d5f04b25c'
remote: Submodule path 'packages/meteor-chartjs': checked out 'f34fc5859964bb6d6627cee5b994613b34eb019d'
remote: Submodule path 'packages/meteor-typeahead': checked out '155cf1c3f08600c63b9947aaeb1a93c404b1d6a3'
remote: Submodule path 'packages/relative-time': checked out '3ebad072c0cead8fe5e6328ef88c2cc318ce9dd2'
remote: 
remote: Compressing source files... done.
remote: Building source:
remote: 
remote: -----> Fetching custom git buildpack... done
remote: -----> Node.js app detected
remote: -----> Installing node
remote: -----> Installing meteor
remote: Downloading Meteor distribution
remote: ###########                                                               15.8%

The only thing I can think of is that I haven't upgraded my heroku instance from Cedar-10 to Cedar-14. Thoughts? Help is greatly appreciated.

Push rejected: Syntax error: newline unexpected

I am getting the following error when pushing to Heroku. Looks like it's a problem installing meteor?

remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Fetching set buildpack https://github.com/AdmitHub/meteor-buildpack-horse.git... done
remote: -----> Node.js app detected
remote: -----> Installing node
remote: -----> Installing meteor
remote: /bin/sh: 2: Syntax error: newline unexpected
remote:
remote: ! Push rejected, failed to compile Node.js app
remote:
remote: Verifying deploy...
remote:
remote: ! Push rejected to grocery-beta.

Cannot find ionic scss

Hi!

I've tried the setting stack to -14 solution (but i believe that the latest version of heroku doesn't require that setting already since they have deprecated the previous stack version https://devcenter.heroku.com/articles/cedar), and i'm still getting the error of

remote: Errors prevented bundling:
remote: While building the application:
remote: /tmp/build_c76b59a4fbbd167b917775f6cee37410/client/stylesheets/app.scss:4:9:
remote: Scss compiler error: file to import not found or unreadable:
remote: .meteor/local/build/programs/server/assets/packages/meteoric_ionic-sass/ionic
remote: Current dir: /tmp/build_c76b59a4fbbd167b917775f6cee37410/client/stylesheets/
remote: 
remote: 
remote: 
remote:  !     Push rejected, failed to compile Node.js app

any help will be greatly appreciated!

Application Error with 0.9.4

I was previously using this buildpack with version 0.8.2: https://github.com/oortcloud/heroku-buildpack-meteorite.git

Here's the build log. The build completes, but I get an application error when I navigate to the app in browser.

-----> Removing .DS_Store files
-----> Fetching custom git buildpack... done
----->  app detected
-----> Installing node
-----> Installing meteor
Downloading Meteor distribution
######################################################################## 100.0%

Meteor 0.9.4 has been installed in your home directory (~/.meteor).

Now you need to do one of the following:

  (1) Add "$HOME/.meteor" to your path, or
  (2) Run this command as root:
        cp "/tmp/buildpack_6ea962a0-5f60-4547-a8ea-aad2b00b03d6/meteor-9YF6/.meteor/packages/meteor-tool/1.0.34/meteor-tool-os.linux.x86_64/scripts/admin/launch-meteor" /usr/bin/meteor

Then to get started, take a look at 'meteor --help' or see the docs at
docs.meteor.com.
-----> Bundling bundle
npm-container: updating npm dependencies -- cheerio...
npm WARN package.json [email protected] No description
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No README data

> [email protected] install /tmp/build_6ea962a0-5f60-4547-a8ea-aad2b00b03d6/.meteor/heroku_build/app/programs/server/node_modules/fibers
> node ./build.js

`linux-x64-v8-3.14` exists; testing
Binary is fine; exiting
[email protected] node_modules/progress

[email protected] node_modules/ip

[email protected] node_modules/underscore

[email protected] node_modules/semver

[email protected] node_modules/chalk
????????? [email protected]
????????? [email protected]
????????? [email protected]
????????? [email protected] ([email protected])
????????? [email protected] ([email protected])

[email protected] node_modules/source-map-support
????????? [email protected] ([email protected])

[email protected] node_modules/fibers
-----> Adding PATH environment
-----> Running extras
-----> Adding MailGun config -> MAIL_URL env
-----> Adding MONGOHQ_URL -> MONGO_URL env
-----> Installing phantomjs.
-----> Discovering process types
       Procfile declares types -> (none)
       Default types for       -> web

-----> Compressing... done, 47.6MB
-----> Launching... done, v147
       http://xxxxxxxx.herokuapp.com/ deployed to Heroku

And here are the packages I have installed, if that matters:

mrt:[email protected]

standard-app-packages
stylus
http
email
jquery
accounts-password
accounts-base

meteorhacks:npm
iron:router
natestrauser:jquery-scrollto
mizzao:jquery-ui
mizzao:bootstrap-3
mizzao:bootboxjs
dbeath:feedparser
meteorhacks:fast-render
alanning:[email protected]
sacha:[email protected]
natestrauser:[email protected]
npm-container

Edit: I should mention that the app deploys fine to Meteor servers, so it's hanging up with the buildpack somewhere. I'm not an experienced developer, so any pointers for how to solve this would be helpful. Thanks

Disable spinner/loading bar in console

This can sometimes be annoying in build/ci logs.

Apparently it's possible with an env variable:
meteor/meteor#5208

How to skip build from zero when using with meteor and dokku.

I am using meteor-buildpack-horse with dokku and meteor.
And it works perfectly when I push to dokku and deploy my app.

But every time I push to dokku, it build from installing node and meteor and it costs a lot of time.
Do you have any idea how can I skip the initial build?

Error: [remote rejected] master -> master (pre-receive hook declined)

I am having this error [remote rejected] master -> master (pre-receive hook declined) when pushing to heroku

Packages downgrading during deploy

I've noticed that more and more packages are downgrading during deploy to Heroku. It was't a problem before but now when I've started using undescrore string package it's just stopped working on Heroku servers.
How can I prevent downgrading at all?

-----> Bundling bundle
ios: platform is not in this project
android: platform is not in this project
crawler: updating npm dependencies -- crawler...

Changes to your project's package version selections:

aldeed:collection2                   downgraded from 2.3.2 to 2.3.1
aldeed:template-extension            downgraded from 3.4.0 to 3.1.1
ian:accounts-ui-bootstrap-3          downgraded from 1.2.27 to 1.2.20
particle4dev:cheerio                 downgraded from 1.1.0 to 1.0.0
reywood:iron-router-ga               downgraded from 0.5.3 to 0.4.1
underscorestring:underscore.string*  downgraded from 3.0.3 to 2.4.0


* These packages have been updated to new versions that are not backwards

build failing - appears related to phantom JS

I have a couple Meteor apps (latest version of Meteor 1.0.2) that fail to build. The error message is:

    remote: -----> Adding PATH environment
    remote: -----> Running extras
    remote: -----> Adding MONGOHQ_URL -> MONGO_URL env
    remote: -----> Adding MONGOLAB_URI -> MONGO_URL env
    remote: -----> Installing phantomjs.
    remote: bzip2: (stdin) is not a bzip2 file.
    remote: tar: Child returned status 2
    remote: tar: Error is not recoverable: exiting now
    remote:
    remote:  !     Push rejected, failed to compile Node.js app

I've forked the buildpack to try using Phantom's latest version, 2.0.0, but received the same error.

Any ideas? Anybody else experiencing this?

startup issue

When i use this buildpack deploy to a remote server,its successfuly as expected,But when the remote server reboot the app can not startup automatic .
I use dokku on the server side
🆘

Failed to start process when deploying repo with nested meteor-app directory

Trying to deploy a project with a meteor app nested in a directory called app/. It seems like the compile script knows to look for this type of setup (line 33):

[ ! -d "$APP_CHECKOUT_DIR/.meteor" ] && APP_CHECKOUT_DIR="$APP_CHECKOUT_DIR/app"

But then the app crashes with the following message in the log:

2015-07-03T20:39:40.677216+00:00 heroku[web.1]: Starting process with command '.meteor/heroku_build/bin/node .meteor/heroku_build/app/main.js'
2015-07-03T20:39:42.577897+00:00 app[web.1]: bash: .meteor/heroku_build/bin/node: No such file or directory

Could the issue be that the release script needs to take into account that the meteor app might be nested in an 'app' directory?

web: .meteor/heroku_build/bin/node .meteor/heroku_build/app/app/main.js

Push Rejected. Failed to Compile Node.js app

Hi,

For the first time I'm trying to deploy a Meteor app to Heroku. I am also using MongoLab hosted db. I just started out with the LeaderBoard example, added the buildpack and tried to push the comitted code. Everything was fine until this following error occurred.

-----> Bundling bundle
Installing Meteor 0.8.3:

'meteor' build tool (version cef2bcd356)
Package updates: accounts-base accounts-facebook accounts-github
accounts-google accounts-meetup accounts-meteor-developer accounts-oauth
accounts-password accounts-twitter accounts-ui accounts-ui-unstyled
accounts-weibo amplify appcache application-configuration
audit-argument-checks autopublish autoupdate backbone binary-heap blaze
blaze-tools bootstrap browser-policy browser-policy-common
browser-policy-content browser-policy-framing callback-hook check
code-prettify coffeescript coffeescript-test-helper ctl ctl-helper d3 deps
dev-bundle-fetcher disable-oplog ejson email facebook facts follower-livedata
force-ssl geojson-utils github google handlebars html-tools htmljs http
id-map insecure jquery jquery-history jquery-layout jquery-waypoints
js-analyze js-analyze-tests json jsparse less livedata localstorage logging
meetup meteor meteor-developer meyerweb-reset minifiers minimongo
mongo-livedata oauth oauth-encryption oauth1 oauth2 observe-sequence
ordered-dict preserve-inputs random reactive-dict reload reload-safetybelt
retry routepolicy service-configuration session sha showdown spacebars
spacebars-compiler spacebars-tests spiderable srp standard-app-packages
star-translate startup stylus templating test-helpers test-in-browser
test-in-console tinytest twitter ui underscore underscore-tests webapp weibo

'remove-platform' is not a Meteor command. See 'meteor --help'.

! Push rejected, failed to compile Node.js app

To [email protected]:testleader.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to '[email protected]:testleader.git'
D:\Meteor\backup [master +4 ~0 -0 !]>

Could not resolve host semver.io

Not sure if this is related to the buildpack, but sometimes if I push my code to heroku I get the following error-Message:

git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree push -v --tags production master:master 
Pushing to [email protected]:test.git
remote: Compressing source files... done.        
remote: Building source:        
remote: 
remote: -----> Fetching custom git buildpack... done        
remote: -----> Node.js app detected        
remote: -----> Installing node        
remote: curl: (6) Could not resolve host: semver.io        
remote: 
remote:  !     Push rejected, failed to compile Node.js app        
remote: 
remote: Verifying deploy...        
remote: 
remote: !   Push rejected to test.        
remote: 
To [email protected]:test.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to '[email protected]:test.git'
Completed with errors, see above

Typo in instructions

Instruction step 2 has a typo: heroku buildpacks:set https://github.com/AdmitHub/meteor-buildpack-horse.git

It should be buildpack:set.

Can't deploy if you have added mobile platforms

Initializing repository, done.
Counting objects: 414, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (339/339), done.
Writing objects: 100% (414/414), 233.88 KiB | 431.00 KiB/s, done.
Total 414 (delta 156), reused 0 (delta 0)

-----> Fetching custom git buildpack... done
----->  app detected
-----> Installing node
-----> Installing meteor
Downloading Meteor distribution
######################################################################## 100.0%

Meteor 1.0 has been installed in your home directory (~/.meteor).

Now you need to do one of the following:

  (1) Add "$HOME/.meteor" to your path, or
  (2) Run this command as root:
        cp "/tmp/buildpack_2318cd131e6954838a18ea3e45a6a560/meteor-EtmR/.meteor/packages/meteor-tool/1.0.35/meteor-tool-os.linux.x86_64/scripts/admin/launch-meteor" /usr/bin/meteor

Then to get started, take a look at 'meteor --help' or see the docs at
docs.meteor.com.
-----> Bundling bundle
Supply the server hostname and port in the --server option
for mobile app builds.

 !     Push rejected, failed to compile  app

METEOR_SETTINGS env var is breaking the build

There is almost no documentation on how to correctly use this env variable.

I tried giving it a path to a json file but i coudln't get it to work at all. The alternative i found was to specifiy the json directly like :

METEOR_SETTINGS = '{ "public" : { "foo" : "bar" } }'

This works and settings are loaded in my app. If i try to push the code while this variable is set, i get an error :

remote: Errors prevented isopacket load:
remote: 
remote: While loading isopacket `constraint-solver`:
remote: packages/meteor/server_environment.js:13:1: METEOR_SETTINGS are not valid JSON:
remote: {public:{ga:{id:UA-XXXXXX-YY}}}
remote: at packages/meteor/server_environment.js:13:1
remote: at <runJavaScript-2>:41:4
remote: at <runJavaScript-2>:1240:3

My current workaround is to unset the variable, deploy my code, re-set the variable. Is someone else experiencing this ?

Slug compilation very slow

I feel like the slug compilation is very slow with this buildpack. It often will take more than 8 minutes to build the app. When I've built node apps in the past they have compiled much more quickly. Does anyone have any thoughts on this?