-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment on Heroku... #52
Comments
I tried doing this too:
Should the user name and password go somewhere else? |
I haven't handled the url case yet, but you can do this: # config/databases.coffee
module.exports =
mongodb:
development:
name: "example-development"
port: 27017
host: "127.0.0.1"
test:
name: "example-test"
port: 27017
host: "127.0.0.1"
staging:
name: "example-staging"
port: 27017
host: "127.0.0.1"
# mongodb://heroku_app123123123:[email protected]:33591/heroku_app123123123
production:
name: "heroku_app123123123"
port: 33591
host: "ds077519.mongolab.com"
username: "heroku_app123123123"
password: "ajsdifjasdfklasjdfa" Does that work? |
Hi Thanks. Yes it worked. I'm getting close now. The app works, but the bootstrap assets, css etc aren't available. I ran cake assets:bundle and then committed the assets to the repo. For testing purposes is it possible to just include the assets, or should they always be uploaded to s3? Thank you very much for your help. |
Nice! Yeah, I got a little carried away in not wanting to commit "compiled" things to repos and added the So, just open that file, remove those lines, re-commit, and re-push your code, should work then.
|
Thanks. I changed the .gitignore file, but no luck. I noticed that if I run I'll review the docs. I noticed the files in the assets directory are binary. Should I not have done the cake assets:bundle step? Thanks again for all the advice. Best |
Oh ok you're right, looks like the http headers for gzip still haven't been updated. Try doing what he did and comment out the gzip code. I will fix this soon, but the default should gzip since it's the most optimized. Basically, if you get rid of gzip the node server will serve the minified version properly, and heroku should show them. If you get through this I'd love to get a pull request with fixes. Let me know how it goes. |
Thanks. I'll let you know how it goes and hopefully get a pull request for you. |
You can try these two plugins, see if they allow you to serve gzipped files locally: I don't have the time at the moment to test this out, but that's where I'd start to get gzipping working. |
Cool. Thanks. I'll take a look this evening and tomorrow. |
Still working on it. Got busy so I haven't finished. A couple notes. I tried using both gzippo and connect-gzip by adding to the tower/server/application.js file
or
And then changing
testing both, this one is for connect-gzip. Am I in the right area? Also, I noticed that if I comment out ./node_modules/tower/lib/server/application/assets.js, line 60
And bundle the assets, then run locally as production, I get some css, but there is javascript error "ReferenceError: Can't find variable: DesignIO" Where should I look for that. Hopefully I'll have more time in the next couple of days and I can continue working on it. Thanks |
I recommend to add stuff about MongoHQ config settings here: https://github.com/viatropos/tower/wiki/heroku Have to search all issues to solve same trouble |
I think I'm close to having a test deployed on heroku. Sorry I keep bugging you.
I configured my heroku app with the MongoHQ add on. What I get for a connection is
In my database.coffee file, I tried adding this as the host:
But I end up with an error:
I assume I need to configure a connection uri instead of the host and port, but I'm not sure where to go about doing this. Any advice would be greatly appreciated.
The text was updated successfully, but these errors were encountered: