Error 702 or 300 when trying to push a Rails app

[nightscape]

Hi Trotter,

first of all thanks for your great work on the Vagrant recipe!

I get the error

Creating Application: Error 702: External URIs are not enabled for this account

when trying to vmc push myapp --runtime ruby19.
When I do a vmc push myapp

Creating Application: Error 300: Invalid application description

Unfortunately Google does not have much to say for those errors:
The 702 seems to occur when you either type a wrong URL or use an already existing one (both of which is not the case for me).
The 300 seems to occur when deploying WAR files, but I have a Rails app...
Have you experienced any of those errors?

[trotter]

Hey, I need to update the docs. You need to specify your app url as "
blah.vcap.me" instead of the default of "blah.vcap.me:8080"

• Trotter

On Fri, Mar 16, 2012 at 3:56 PM, Martin Mauch <
reply@reply.github.com

wrote:

Hi Trotter,

first of all thanks for your great work on the Vagrant recipe!

I get the error

Creating Application: Error 702: External URIs are not enabled for this
account

when trying to vmc push myapp --runtime ruby19.
When I do a vmc push myapp

Creating Application: Error 300: Invalid application description

Unfortunately Google does not have much to say for those errors:
The 702 seems to occur when you either type a wrong URL or use an already
existing one (both of which is not the case for me).
The 300 seems to occur when deploying WAR files, but I have a Rails app...
Have you experienced any of those errors?

---

Reply to this email directly or view it on GitHub:
#3

[nightscape]

NICE!!!

[trotter]

Also, cookbooks have just been updated to support a mysql service. Now you're able to deploy apps backed by a database :-)

[nightscape]

I guess creating another submodule for postgresql where I replace every occurence of mysql with postgresql is too naive :p