deployment issue about pup

[swyxio]

in case it matters, i am using this buildpack: https://github.com/AdmitHub/meteor-buildpack-horse

[Davidlab]

You need to start Meteor with npm start which will in return call the command meteor --settings settings-development.json from the start script in your package.json file. This will set the value of 'OAuth' during startup.

[swyxio]

thats obviously only for running it in dev on local machine right? what about when i need to run it in production on heroku. that is what i call deployment.

[justin88]

Did you write your own settings-production.json? See details here:

• http://cleverbeagle.com/pup/v1/the-basics/settings
• http://cleverbeagle.com/pup/v1/file-structure

[swyxio]

hello, yes, i did write my own settings-production.json. however it seemed like it wasnt deploying correctly on heroku. i havent managed to figure out how to fix it the "correct" way but i have commented out the oauth check for now in pup.

[joserocha3]

@sw-yx did you add a config variable for METEOR_SETTINGS to your app on the heroku dashboard?

Choose your app -> settings -> reveal config vars -> add METEOR_SETTINGS and paste in the json from your settings file, then redeploy.

This is specific to heroku. Other hosting providers allow you to upload your settings during build. I have it running here.

[joserocha3]

On a side note, if you are not going to enter oauth values then set your METEOR_SETTINGS config var to this. That will avoid the oauth buttons from getting a setup.

{
  "private": {},
  "public" :{}
}

[swyxio]

ahh. i will try this. this sounds very promising. thanks very much @joserocha3, closing for now. may want to put this (Heroku deployment notes) somewhere in the docs (maybe its obvious and i'm just a newbie).