problem with heroku deploy steps

[Frank Hebbert]

The process described in the docs for deploying to heroku fails at this step -- "git push heroku master:master". Using instructions from this page -- 

https://github.com/openplans/shareabouts/blob/master/doc/DEPLOY.md#deploying-to-a-paas-provider

Where was the remote set? Is there a step missing? I'm not actually doing this process, so it's possible that a step might have been skipped here rather than in the docs.

--
Frank Hebbert
OpenPlans | http://openplans.org | 720 432-2378 | @fkh

[Mjumbe Poe]

When you run `heroku apps:create ...` the Heroku utility sets up a remote for you (or it should). If you don't run create from inside of your git repo, then you'll have to set up the remote as a separate step.

...at least I'm pretty sure that's the case (almost positive).

https://devcenter.heroku.com/articles/creating-apps

- Mjumbe

-- --
Shareabouts Developers group.
Unsubscribe: https://groups.google.com/d/forum/shareabouts-dev?hl=en

[Frank Hebbert]

Mjumbe, you're right -- it works for me.

$ heroku apps:create shareaboutstest

Creating shareaboutstest... done, stack is cedar

http://shareaboutstest.herokuapp.com/ | g...@heroku.com:shareaboutstest.git

Git remote heroku added

$ git push heroku master:master

Counting objects: 7399, done.

Delta compression using up to 4 threads.

etc

I think someone wasn't working out of the right directory when trying this yesterday.

[Steven Vance]

Here's the full set of commands tried:

Monster:~ stevevance$ heroku apps:create shareabouts1
Creating shareabouts1... done, stack is cedar
http://shareabouts1.herokuapp.com/ | g...@heroku.com:shareabouts1.git
Monster:~ stevevance$ cd Sites
Monster:Sites stevevance$ cd shareabouts1
Monster:shareabouts1 stevevance$ ls
CHANGELOG.md ci requirements.txt
LICENSE.txt doc src
Procfile dotcloud.yml wsgi.py
README.md postinstall
Monster:shareabouts1 stevevance$ git push heroku master:master
fatal: 'heroku' does not appear to be a git repository
fatal: The remote end hung up unexpectedly

[Frank Hebbert]

Steven, you needed to run 

heroku apps:create shareabouts1

git push heroku master:master

from within the shareabouts1 directory (not changing directory in between steps). That's where we went wrong yesterday.

[Mjumbe Poe]

Steven,

Alternatively, since you've already created the heroku app, you could run (from within your git repository):

git remote add heroku g...@heroku.com:shareaboutstest.git

Then your git push heroku master should work.

- Mjumbe

[Eric Smith]

I am attempting to deploy a test to Heroku.

I was able to get the below to work:

$heroku apps:create shareabouttest13

Creating shareabouttest13... done, stack is cedar (I see the application was created)

Then had a failure here:

$ git push heroku master:master

fatal: Not a git repository (or any of the parent directories): .git

I am trying to follow the steps in the from here, https://github.com/openplans/shareabouts/blob/master/doc/DEPLOY.md but am stuck. I have also tried to figure out what has been said in this thread but it has not helped.

Thank you.

Eric

[Frank Hebbert]

Eric, it sounds like you are not working from a git repo, which heroku expects. If you downloaded the source code for Shareabouts as a zip file, this will be the case.

To turn your current repo into a git repo, make sure you're in the directory, then:
git init
git add .
git commit -m "My shareabouts site"

Then, run
heroku info

and get the "Git URL", which will be something like g...@heroku.com:blah.git and run this:

git remote add heroku g...@heroku.com:blah.git

Then try 

git push heroku master:master

The docs here are useful: https://devcenter.heroku.com/articles/git

--

-- --
Shareabouts Developers group.
Unsubscribe: https://groups.google.com/d/forum/shareabouts-dev?hl=en
---

You received this message because you are subscribed to the Google Groups "Shareabouts Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to shareabouts-d...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Eric Smith]

Frank,

Thank you so much, you are quick. That got me up and running. http://shareabouttest13.herokuapp.com

Now to re-update documents as they are changed I would use the  git push heroku master:master when something like the CSS or internal pages are changed?

Correct?

[Frank Hebbert]

Almost correct. You need to commit the changes to your local repo first, so git can send them off to heroku to be deployed. 

git commit -a -m "Commit message"

If you're not familiar with git, I suggest checking out the excellent documents on github. You can use git without ever using github, but their docs are good, and they have this neat tutorial: http://try.github.io/ 

There are also various GUI tools, including git for mac, if you prefer things that way.

[Eric Smith]

Thank you Frank, that makes sense. I will look into the items your mentioned.

Also, do you know the average time it takes for something to update from the time of updating to seeing it live? Just simple CSS changes? Seems to take a while if I am doing it correctly.

Thanks,

Eric

[Frank Hebbert]

Your browser might be caching the old version of the CSS. Try looking at the site in an incognito window (in Chrome, other browsers have different names for the same feature).