Deploy

The website deployment pipeline allow us to ensure the quality of the production build.

Environments

The website has 3 different environments:

Development:

https://advertising-dev.limbo-dev.awsma.nyt.net/⁠

⁠

Staging:

https://advertising-stg.limbo-dev.awsma.nyt.net/⁠

⁠

Production:

https://advertising.nytimes.com/⁠

⁠

👉 You must be using our company VPN to access dev and stage environments.

Continuous delivery is managed by

Drone⁠

. The

.drone.yml⁠

file in the root of the project runs a pipeline every time that a branch repository is pushed.

When a branch named feature/<feature-name> is pushed it triggers a build and deploy of Development and Staging environment.

When a branch is merged into main it triggers a build and deploy in Production.

The Drone file indicate also the

Vault secrets⁠

used by each builds to generate their own dotenv file. At the moment:

Development and Staging both use nytimes/infosec-stink/secret/dotenv_dev.b64 .

Production uses nytimes/infosec-stink/secret/dotenv.b64 .

Please be sure to update the secrets to match your local .env.local file, if you modify it.

Secrets are stored in base64 format. To update them you could follow this process.

With a terminal in your /web folder execute this command to generate a base64 encoded string of your modified dotenv file:

base64 -i .env.local > .env.local.b64

Update the secret used by the environment you are working on via the

Vault web UI⁠

Alternatively, update the secret via command line. Read the Vault page for more information.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.