Closed joe-gz closed 8 years ago
I should note that we are also getting the below error right before the issue above:
Wed, 09 Dec 2015 14:09:32 GMT express-session deprecated undefined resave option; provide resave option at index.js:29:9
I thought that was due to the env.js issue, but i think it might be separate?
Take a look at how environment variables are handled here:
So I've set the api_key we have as a variable in heroku already, but don't I still need the env.js file for local work?
¿Por que no los dos?
if(app.settings.env == "development"){
var env = require("./env.js");
}else{
var env = process.env;
}
That's kind-of a hacky way of handrolling it. You also might look into Figaro for Node.
I'ma close this, but please open a new one if necessary!
thanks robin! I'll keep you posted
Hi, I'm working on deploying right now, and I think I've gone through all the steps, but I'm getting an error due to our hidden env.js file i believe:
I think that is coming straight from the index.js file, as we have:
where heroku is not understand my require("./env") at the top there. I've been searching for a few hours, but I can't find any documentation on an error like this. any thoughts? Thanks!