You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2022. It is now read-only.
Thanks @richtera, @cliftonc and all. I just got myself successfully deployed to heroku. Nothing much to see there ( http://salsbury.io ) yet, but it works.
For posterity and potential inclusion in a FAQ somewhere, I was able to deploy with this Procfile:
You guys might to monitor your database. The nodejitsu instance's db just ran close to 500M because of the session table not being cleared of old sessions. Will need to figure this out but I just cleared the session table by hand.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thanks @richtera, @cliftonc and all. I just got myself successfully deployed to heroku. Nothing much to see there ( http://salsbury.io ) yet, but it works.
For posterity and potential inclusion in a FAQ somewhere, I was able to deploy with this Procfile:
I also did the following to my package.json:
I wonder if the .sh-based install of mongodb driver is no longer necessary?
EDIT: funny, I just temporarily broke my DNS settings -- for now its http://salsbury-io.herokuapp.com ;)
The text was updated successfully, but these errors were encountered: