Make provisioning from scratch work #645
Conversation
| @@ -19,7 +19,7 @@ postgresql_port: 5432 | |||
| postgresql_version: "9.4" | |||
| postgresql_package_version: "9.4.*.pgdg14.04+1" | |||
| postgresql_support_repository_channel: "main" | |||
| postgresql_support_libpq_version: "9.5.*.pgdg14.04+1" | |||
| postgresql_support_libpq_version: "9.3.4-1" | |||
There was a problem hiding this comment.
I'd feel more comfortable if we find a way to make this at least 9.4; JSONB fields weren't introduced until Postgres 9.4, so it'd be nice if all the versions can match up. I'm not sure whether we're actually using libpq though, so if it's not breaking anything for you locally we can punt and make a separate issue for it.
There was a problem hiding this comment.
These are the versions available in the services VM:
$ sudo apt-cache show libpq-dev | grep Version
Version: 10.1-1.pgdg14.04+1
Version: 9.3.20-0ubuntu0.14.04
Version: 9.3.4-1Nothing bad seems to be happening locally, though I haven't exercised much of the app. It might make sense to open a separate (probably small) issue
There was a problem hiding this comment.
Yeah, we're relying on the azavea.postgresql-support role to install libpq-dev. The azavea.postgresql role seems to have support for installing a wide range of postgres versions, but the azavea.postgresql-support role doesn't seem to have been updated quite as much. If using 9.4 for the version doesn't work we'll probably need an ops issue to add support to that role.
| @@ -1,4 +1,4 @@ | |||
| FROM quay.io/azavea/static-core:0.1.0 | |||
| FROM node:4-slim | |||
There was a problem hiding this comment.
Once this is merged I think we can let ops know that they can remove this image from Quay; I assume it's not being used anywhere else.
There was a problem hiding this comment.
It's in their sprint now
| @@ -97,6 +107,17 @@ To load mock interventions, run `python scripts/load_interventions.py --authz 'T | |||
|
|
|||
| To generate black spot and load forecast training inputs, run `python scripts/generate_training_input.py /path/to/roads.shp /path/to/records.csv`. | |||
|
|
|||
| ### Costs | |||
|
|
|||
| You can't request records with associated costs successfully until you configure some costs. | |||
There was a problem hiding this comment.
Wait, are you saying that all record requests fail if this isn't configured? We should probably make an issue for that if so, it's not supposed to impact the rest of the app.
There was a problem hiding this comment.
Not all records requests (like, you can hit /api/records/ successfully), but you can't hit /api/records/costs/, which is required for a lot of the app. I think you can view the records list but I don't remember.
Overview
This PR makes several small changes to make provisioning from scratch cooperate given changes that have occurred in the state of dependencies since this project's dev environment was setup.
Specifically, it explicitly sets
bower's registry, separately installsbower, changes thelibpqversion to something that's in the postgresql PPA, upgrades the base images for some containers tonode:4-slimfrom our oldstatic-corecontainers.Testing
vagrant provision