search

PhilanthropyDataCommons / deploy

Deployment scripts for Philanthropy Data Commons service
GNU Affero General Public License v3.0
2 stars 2 forks source link

Deploy `service` to api.pdco #65

Closed jasonaowen closed 1 year ago

jasonaowen commented 1 year ago

Currently, the production back-end instance is living in a subdirectory on pilot.philanthropydatacommons.org, along with Keycloak.

During today's team meeting, we decided to instead deploy the service at api.philanthropydatacommons.org.

This follows standard application patterns, and should avoid future turbulence if/when we sunset pilot.pdco: partners and other applications that are using the API will not have to change hostnames. That will also let us avoid any cookie issues that come from two apps sharing the same domain name, and it also sets us up to disentangle the deployment of the service from the deployment of Keycloak (although we do not necessarily need to tackle that just yet).

See also https://github.com/PhilanthropyDataCommons/deploy/issues/66

bickelj commented 1 year ago

At the moment, the service repository is agnostic with regard to target environment hostname or domain name. All the specifics are in the deploy repository (and even that is relatively agnostic). This is as good a place as any to track progress, though. The change to api.[pdco] is pending the creation of the subdomain at the moment.

bickelj commented 1 year ago

OK, I changed my mind about where this ticket should live because I went to deploy to find it and it wasn't there. If it is clearly better to track it over in service, please move it back.

bickelj commented 1 year ago

The steps done (first on test, then on prod) were:

  1. Change the /home/reverse-proxy/proxy.conf to reflect the new subdomains,
  2. generate a new certificate for the new subdomain,
  3. restart the reverse proxy container.

And document the change in internal svn notes.

jasonaowen commented 1 year ago

Thanks for the quick work, and for the detailed notes, @bickelj!