Closed alexyork closed 12 years ago
We could just run things localy for dev if where not going to use heroku for prod though?
It is harder to test on real mobile devices if we only do dev on our local machines. This is mainly a mobile app, so it is better that we can really test it on real devices.
It is on heroku now: http://trondheim-dc-2012.herokuapp.com/
hmm, we now have two repositories with duplicate code.
When I make changes to the node app in the src/ folder in this repo, how do I push that to the heroku repo?
Maybe we could just put the Procfile in this repo, running node src/app ?
That way we just have to manage this working copy, but having two remotes for it?
For dev: git push origin master
For deploying: git push heroku master
Thoughts?
I explained that in an email in quite some detail. I use git-subtree. Did you not get the email?
Oh damn, no that passed me by.
I went away and merged them tough. So this repos is the one on heroku as of now.
I think you should undo your last two commits.
All of this was working perfectly, thanks to git-subtree which I spent a couple of hours working on. We could then keep the Procfile in the src/folder and only push /src to the server, as I explained in the email.
You have also added some old files that I deleted at the weekend.... :-/
Blergh, I will. Using git-subtree is more elegant. Il fix them by tomorow.
The examples folder is deprecated and can be removed right?
Yes, the examples folder was not being used so I removed it. Make sure that you carefully examine each file that is included in a commit before committing/pushing :-)
It might be worth investigating git revert or undo (I forget the exact command) and see if you can undo these last commits... either way, just let us know when it is fixed again :-)
There, I think it is fixed now :)
Cool. Are you able to push to heroku using git-subtree? It seems to be working right now, anyway: http://trondheim-dc-2012.herokuapp.com/
You have left a package.json file in the root. Remove that if it isn't needed (it shouldn't be).
Thanks for fixing it :-)
Make sure you can:
If all of those are OK, then we are good to go :-)
Not sure if we will use heroku when we go to prod or not, but we need it whilst developing at least.