Heroku error after deploying a locally functional Shareabouts app

[Linn Davis]

Hi all,

I've got my app all configured and have pushed it to Heroku, but I'm running into a snag -- and banging my brains against the wall trying to figure out what's going on. And I'm hoping someone can help?!

Here's the situation: The app runs just fine on my local machine, but when I push it to Heroku -- which it does successfully -- and try to access it, it gives me this infuriating error:

mapping values are not allowed here
in "/app/src/flavors/ciity/config.yml", line 32, column 28

Line 32 in the config document is the "label:" line pertaining to the first place_type item. I can't attach the full config.yml document right now because I'm sending this from my phone, but I'll try to do that soon. As far as I can tell it looks completely in order -- no syntax weirdness or problematic punctuation marks lying around or anything.

Oh, and here's the URL for the heroku app, where you can see the full text of the error message: http://ciity.herokuapp.com/ .

Any ideas right off the bat? Thanks very much in advance!

Cheers,
Linn

[Mjumbe Poe]

Hi Linn,

I pushed up your config file along with the default Shareabouts flavor to Heroku a instance. This is the result: http://quiet-mesa-3500.herokuapp.com/. Plenty of stuff is not working (understandably, due to missing images and such), but the config was parsed just fine. Try uploading your project to a completely new Heroku app. If that doesn't work, it might be some other part of the flavor.

- Mjumbe

--
-- --
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.

[Linn Davis]

Hi Mjumbe,

Thanks very much for the email and for working on my issue. Much appreciated. In the future, I very much hope I can contribute back to Shareabouts (I have a couple feature ideas!) in exchange for your help getting my site off the ground now.

Anyhow, I tried deploying to a brand new Heroku app and still had problems. First it wouldn't deploy because it seemed to be looking for a particular app name (the old name) to deploy to -- and this app didn't exist anymore (because I had deleted it). Then it was still having problems, so I cloned the default flavor again (thinking I'd start fresh again), inserted my config file and tried again. Then it wouldn't deploy because there wasn't a git repository in the right place (do I have that right?). So I waded around in Heroku's docs and thought I got that settled. And then this happened:

(env)linn:shareabouts-master admin$ git push heroku master
error: src refspec master does not match any .
error: failed to push some refs to 'g...@heroku.com:glacial-eyrie-1399.git'

And now I really have no idea. Is there some way to wipe any references to my previous deployments and just start all over? Or maybe I should just download and install Shareabouts again and start over?

Thanks for any advice you might have.

Cheers,

Linn

You received this message because you are subscribed to a topic in the Google Groups "Shareabouts Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/shareabouts-dev/98zfj9eHy7I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to shareabouts-d...@googlegroups.com.

[Linn Davis]

Hi Mjumbe,

Okay, I downloaded an all new copy of Shareabouts, set it all up again according to the online docs, tested it all locally (works fine) created a brand new heroku account, created a heroku app, pushed to Heroku and ... got this:

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

Any ideas? When this happened before, I think I messed around with git in some way to get it "working" -- at least got things up upload to Heroku -- but then, of course, the app didn't actually work in the end. So now that I've started fresh, I don't want to mess it up again. Any help would be soooo greatly appreciated.

Cheers,
Linn

Linn Davis

September 26, 2013 7:20 PM

Hi Mjumbe,

Thanks very much for the email and for working on my issue. Much appreciated. In the future, I very much hope I can contribute back to Shareabouts (I have a couple feature ideas!) in exchange for your help getting my site off the ground now.

Anyhow, I tried deploying to a brand new Heroku app and still had problems. First it wouldn't deploy because it seemed to be looking for a particular app name (the old name) to deploy to -- and this app didn't exist anymore (because I had deleted it). Then it was still having problems, so I cloned the default flavor again (thinking I'd start fresh again), inserted my config file and tried again. Then it wouldn't deploy because there wasn't a git repository in the right place (do I have that right?). So I waded around in Heroku's docs and thought I got that settled. And then this happened:

(env)linn:shareabouts-master admin$ git push heroku master
error: src refspec master does not match any .
error: failed to push some refs to 'g...@heroku.com:glacial-eyrie-1399.git'

And now I really have no idea. Is there some way to wipe any references to my previous deployments and just start all over? Or maybe I should just download and install Shareabouts again and start over?

Thanks for any advice you might have.

Cheers,

Linn

On Monday, September 16, 2013, Mjumbe Poe wrote:

Mjumbe Poe

September 16, 2013 2:03 PM

Hi Linn,

I pushed up your config file along with the default Shareabouts flavor to Heroku a instance. This is the result: http://quiet-mesa-3500.herokuapp.com/. Plenty of stuff is not working (understandably, due to missing images and such), but the config was parsed just fine. Try uploading your project to a completely new Heroku app. If that doesn't work, it might be some other part of the flavor.

- Mjumbe

--
-- --
Shareabouts Developers group.
Unsubscribe: https://groups.google.com/d/forum/shareabouts-dev?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "Shareabouts Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/shareabouts-dev/98zfj9eHy7I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to shareabouts-d...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Linn Davis

September 12, 2013 11:58 AM

[Linn Davis]

Aaaaalright, sorry to send yet another email to the list, but I think you'll like this one...

I got it working! Finally! Aghgh.

Here's what I did, just for future reference:

(env)host-244-174:shareabouts-master admin$ heroku apps:create ciity
Creating ciity... done, stack is cedar
http://ciity.herokuapp.com/ | g...@heroku.com:ciity.git
(env)host-244-174:shareabouts-master admin$ git init
Initialized empty Git repository in /Users/admin/Documents/shareabouts-master/.git/
(env)host-244-174:shareabouts-master admin$ git add .
(env)host-244-174:shareabouts-master admin$ git commit -m 'first commit'
...
...
...
(env)host-244-174:shareabouts-master admin$ heroku git:remote -a ciity
Git remote heroku added
(env)host-244-174:shareabouts-master admin$ git push heroku master:master

And that did it. The app, in very, preliminary form, is now online. I don't know enough about all this stuff to know whether those steps would be necessary for everyone -- or if I had to go through all that only because I'd messed something up previously -- but if they are necessary for everyone, please add them to the CONFIG.md file; it would have made things much easier for a relative newbie like me.

Thanks again for all your help.

I have another couple questions that are completely unrelated to this business -- and hopefully much simpler -- but I'll at least save them for tomorrow. ;)

Have a great day.

Cheers,
Linn

Linn Davis

September 30, 2013 8:47 PM

[Frank Hebbert]

Hi Linn --

As you discovered, Heroku depends on git for deploying code. This is a useful intro: https://devcenter.heroku.com/articles/git

How did you get the Shareabouts code to start with? If you fork the repository on github before starting work, you get the git setup for free (i.e. no extra steps). Here's a good intro to forking: https://help.github.com/articles/fork-a-repo

For future reference, you can fork Shareabouts and set it up like this:

Go to https://github.com/openplans/shareabouts and fork the repo (create your own copy of the shareabouts client)

In terminal, run these commands:

git clone https://github.com/[your github username]/shareabouts.git 

cd shareabouts

virtualenv env

source env/bin/activate

pip install -r requirements.txt

(...local configuration happens here...)

heroku apps:create shareaboutstest

git push heroku master:master

Putting your Ciity fork of Shareabouts on github will also enable other people to help with future features or troubleshooting by looking at your code.

Frank

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.

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

[Linn Davis]

Hey Frank,

Ah, that's awesome advice. Yes, I'd love to track via Github; I'm just kind of flying by the seat of my pants, so I did whatever the magic of stackoverflow and the Heroku dev center pointed me toward. And it did finally work, though I'm sure it wasn't elegant.

You asked where I acquired Shareabouts: I simply downloaded the .zip file from the main Github page, unzipped it on my laptop and went from there. ;) Flying by the seat of my pants, see? The instructions that you wrote in the email below would have been absolute gold in that original ReadMe document, if you wanted to add it there. I was able to follow the steps there easily enough, and the addition of these tips about forking the Github repo would have closed the last gap.

On my next deploy -- after I make changes to the app locally -- can I get setup on github at that point? Or did I need to have done that at the very beginning? i.e. Can I right my wrong here -- and use Github -- without starting all over again?

And one other question: when I deploy next time, will "git push heroku master" automatically push to the same heroku app that I'm working with now?

Thanks!
Linn

Frank Hebbert

September 30, 2013 9:30 PM

Hi Linn --

As you discovered, Heroku depends on git for deploying code. This is a useful intro: https://devcenter.heroku.com/articles/git

How did you get the Shareabouts code to start with? If you fork the repository on github before starting work, you get the git setup for free (i.e. no extra steps). Here's a good intro to forking: https://help.github.com/articles/fork-a-repo

For future reference, you can fork Shareabouts and set it up like this:

Go to https://github.com/openplans/shareabouts and fork the repo (create your own copy of the shareabouts client)

In terminal, run these commands:

git clone https://github.com/[your github username]/shareabouts.git 

cd shareabouts

virtualenv env

source env/bin/activate

pip install -r requirements.txt

(...local configuration happens here...)

heroku apps:create shareaboutstest

git push heroku master:master

Putting your Ciity fork of Shareabouts on github will also enable other people to help with future features or troubleshooting by looking at your code.

Frank

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

[Frank Hebbert]

Hi Linn --

Answers in line below.

You asked where I acquired Shareabouts: I simply downloaded the .zip file from the main Github page, unzipped it on my laptop and went from there. ;) Flying by the seat of my pants, see? The instructions that you wrote in the email below would have been absolute gold in that original ReadMe document, if you wanted to add it there. I was able to follow the steps there easily enough, and the addition of these tips about forking the Github repo would have closed the last gap.

Thanks for the feedback, I created a ticket about adding this to the documentation.

This is a good primer on getting set up if you're not an experienced developer, by Aaron Fraint -- http://afraint.webfactional.com/post/Shareabouts_deployment/

 

On my next deploy -- after I make changes to the app locally -- can I get setup on github at that point? Or did I need to have done that at the very beginning? i.e. Can I right my wrong here -- and use Github -- without starting all over again?

Now you have a local git repo, you can connect it to github by creating an empty repo on github and following the instructions (it will show you the exact commands to connect your existing local repo to your new github pages site, so you can copy and paste). You don't need to start over.

 

And one other question: when I deploy next time, will "git push heroku master" automatically push to the same heroku app that I'm working with now?

Yes. 

Looking forward to seeing the site!

Frank

[Linn Davis]

Frank,

Thanks very much for the links and the answers to my various questions once again. And for wanting update the documentation -- that's really fantastic. I'll follow your tips for setting up on github.

I have a couple other config questions and suggestions, but I'll submit those as separate emails when I get a chance.

Thanks again,
Linn

Frank Hebbert

October 3, 2013 11:01 AM

--
-- --
Shareabouts Developers group.
Unsubscribe: https://groups.google.com/d/forum/shareabouts-dev?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "Shareabouts Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/shareabouts-dev/98zfj9eHy7I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to shareabouts-d...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Linn Davis

September 30, 2013 9:51 PM

Hey Frank,

Ah, that's awesome advice. Yes, I'd love to track via Github; I'm just kind of flying by the seat of my pants, so I did whatever the magic of stackoverflow and the Heroku dev center pointed me toward. And it did finally work, though I'm sure it wasn't elegant.

You asked where I acquired Shareabouts: I simply downloaded the .zip file from the main Github page, unzipped it on my laptop and went from there. ;) Flying by the seat of my pants, see? The instructions that you wrote in the email below would have been absolute gold in that original ReadMe document, if you wanted to add it there. I was able to follow the steps there easily enough, and the addition of these tips about forking the Github repo would have closed the last gap.

On my next deploy -- after I make changes to the app locally -- can I get setup on github at that point? Or did I need to have done that at the very beginning? i.e. Can I right my wrong here -- and use Github -- without starting all over again?

And one other question: when I deploy next time, will "git push heroku master" automatically push to the same heroku app that I'm working with now?

Thanks!
Linn

Frank Hebbert

September 30, 2013 9:30 PM

Hi Linn --

As you discovered, Heroku depends on git for deploying code. This is a useful intro: https://devcenter.heroku.com/articles/git

How did you get the Shareabouts code to start with? If you fork the repository on github before starting work, you get the git setup for free (i.e. no extra steps). Here's a good intro to forking: https://help.github.com/articles/fork-a-repo

For future reference, you can fork Shareabouts and set it up like this:

Go to https://github.com/openplans/shareabouts and fork the repo (create your own copy of the shareabouts client)

In terminal, run these commands:

git clone https://github.com/[your github username]/shareabouts.git 

cd shareabouts

virtualenv env

source env/bin/activate

pip install -r requirements.txt

(...local configuration happens here...)

heroku apps:create shareaboutstest

git push heroku master:master

Putting your Ciity fork of Shareabouts on github will also enable other people to help with future features or troubleshooting by looking at your code.

Frank

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