How do I auto run extension install command on Heroku when provisioning DB using pipelines?
up vote
1
down vote
favorite
I'm using the Heroku Pipelines feature to auto create a review app whenever I create a new PR in github. This will provision a new DB for you and migrate all your database schema. When migrating this schema I receive this error:
AttributeError: 'DatabaseOperations' object has no attribute 'geo_db_type'
I want to use PostGIS which means I need to run CREATE EXTENSION postgis;
on the db after it's automatically provisioned. My hunch is that I'm getting this error because the extension isn't installed yet by the time it runs python manage.py migrate. How would I run this in an automated way when it's building my review app?
postgresql heroku postgis geodjango heroku-postgres
asked Nov 19 at 0:32
Brian O'Neill
315136
add a comment |
up vote
1
down vote
favorite
I'm using the Heroku Pipelines feature to auto create a review app whenever I create a new PR in github. This will provision a new DB for you and migrate all your database schema. When migrating this schema I receive this error:
AttributeError: 'DatabaseOperations' object has no attribute 'geo_db_type'
I want to use PostGIS which means I need to run CREATE EXTENSION postgis;
on the db after it's automatically provisioned. My hunch is that I'm getting this error because the extension isn't installed yet by the time it runs python manage.py migrate. How would I run this in an automated way when it's building my review app?
postgresql heroku postgis geodjango heroku-postgres
asked Nov 19 at 0:32
Brian O'Neill
315136
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm using the Heroku Pipelines feature to auto create a review app whenever I create a new PR in github. This will provision a new DB for you and migrate all your database schema. When migrating this schema I receive this error:
AttributeError: 'DatabaseOperations' object has no attribute 'geo_db_type'
I want to use PostGIS which means I need to run CREATE EXTENSION postgis;
on the db after it's automatically provisioned. My hunch is that I'm getting this error because the extension isn't installed yet by the time it runs python manage.py migrate. How would I run this in an automated way when it's building my review app?
postgresql heroku postgis geodjango heroku-postgres
asked Nov 19 at 0:32
Brian O'Neill
315136
I'm using the Heroku Pipelines feature to auto create a review app whenever I create a new PR in github. This will provision a new DB for you and migrate all your database schema. When migrating this schema I receive this error:
AttributeError: 'DatabaseOperations' object has no attribute 'geo_db_type'
I want to use PostGIS which means I need to run CREATE EXTENSION postgis;
on the db after it's automatically provisioned. My hunch is that I'm getting this error because the extension isn't installed yet by the time it runs python manage.py migrate. How would I run this in an automated way when it's building my review app?
postgresql heroku postgis geodjango heroku-postgres
postgresql heroku postgis geodjango heroku-postgres
asked Nov 19 at 0:32
Brian O'Neill
315136
asked Nov 19 at 0:32
Brian O'Neill
315136
asked Nov 19 at 0:32
Brian O'Neill
315136
asked Nov 19 at 0:32
Brian O'Neill
315136
asked Nov 19 at 0:32
Brian O'Neill
315136
315136
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
It's a bit of a kludge since review apps don't support it natively yet but you could teach your postdeploy script a new trick. Something like this:
"postdeploy": "echo 'CREATE EXTENSION IF NOT EXISTS postgis;' | psql $DATABASE_URL && --run your migrations here--"
This will pipe in the extension creation prior to running your migrations which should solve the troubles you're seeing.
answered Nov 19 at 15:36
RangerRanger
1,0121922
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
It's a bit of a kludge since review apps don't support it natively yet but you could teach your postdeploy script a new trick. Something like this:
"postdeploy": "echo 'CREATE EXTENSION IF NOT EXISTS postgis;' | psql $DATABASE_URL && --run your migrations here--"
This will pipe in the extension creation prior to running your migrations which should solve the troubles you're seeing.
answered Nov 19 at 15:36
RangerRanger
1,0121922
add a comment |
up vote
1
down vote
accepted
It's a bit of a kludge since review apps don't support it natively yet but you could teach your postdeploy script a new trick. Something like this:
"postdeploy": "echo 'CREATE EXTENSION IF NOT EXISTS postgis;' | psql $DATABASE_URL && --run your migrations here--"
This will pipe in the extension creation prior to running your migrations which should solve the troubles you're seeing.
answered Nov 19 at 15:36
RangerRanger
1,0121922
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
It's a bit of a kludge since review apps don't support it natively yet but you could teach your postdeploy script a new trick. Something like this:
"postdeploy": "echo 'CREATE EXTENSION IF NOT EXISTS postgis;' | psql $DATABASE_URL && --run your migrations here--"
This will pipe in the extension creation prior to running your migrations which should solve the troubles you're seeing.
answered Nov 19 at 15:36
RangerRanger
1,0121922
It's a bit of a kludge since review apps don't support it natively yet but you could teach your postdeploy script a new trick. Something like this:
"postdeploy": "echo 'CREATE EXTENSION IF NOT EXISTS postgis;' | psql $DATABASE_URL && --run your migrations here--"
This will pipe in the extension creation prior to running your migrations which should solve the troubles you're seeing.
answered Nov 19 at 15:36
RangerRanger
1,0121922
answered Nov 19 at 15:36
RangerRanger
1,0121922
answered Nov 19 at 15:36
RangerRanger
1,0121922
answered Nov 19 at 15:36
RangerRanger
1,0121922
1,0121922
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53366894%2fhow-do-i-auto-run-extension-install-command-on-heroku-when-provisioning-db-using%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
