Deploy a Node.js App with Cloud66

Deploy a Node.js app with an encrypted .env.vault file on Cloud66.

Initial setup

Create an index.js file, if you haven't already done so.

// index.js
const PORT = process.env.PORT || 3000
const http = require('http')
const server = http.createServer((req, res) => {
  res.statusCode = 200
  res.setHeader('Content-Type', 'text/plain')
  res.end(`Hello ${process.env.HELLO}`)
})

server.listen(PORT, () => {
  console.log(`Server running on port:${PORT}/`)
})

Add an empty package.json file (needed for the Docker build).

{}

Add a Dockerfile.

# Dockerfile
FROM node:16
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm install
COPY . .
EXPOSE 3000
CMD node index.js

Commit that to code, push it up to GitHub, and connect it to your Cloud66 account.

app.cloud66.com

On the next screen, make sure to set the local port to 3000, http to 80, https to 443.

app.cloud66.com

Confirm everything looks good and click 'Start Deployment'.

app.cloud66.com

Visit your app.

yourapp running on cloud66

Once deployed, your app will say 'Hello undefined' as it doesn’t have a way to access the environment variable yet. Let’s do that next.

Install dotenv

Install dotenv.

npm install dotenv --save # Requires dotenv >= 16.1.0

Create a .env file in the root of your project.

# .env
HELLO="World"

As early as possible in your application, import and configure dotenv.

// index.js
require('dotenv').config()
console.log(process.env) // remove this after you've confirmed it is working

const PORT = process.env.PORT || 3000
const http = require('http')
...

Try running it locally.

docker build -t docker-nodejs . && docker run --rm -it -p 3000:3000 --init docker-nodejs
{
  ...
  HELLO: 'World'
}
Server running on port:3000/

Perfect. process.env now has the keys and values you defined in your .env file.

localhost

That covers the local development build. Let's solve for production next.

Build .env.vault

Push your latest .env file changes and edit your production secrets. Learn more about syncing

npx dotenv-vault@latest push
npx dotenv-vault@latest open production

Use the UI to configure those secrets per environment.

www.dotenv.org

Then build your encrypted .env.vault file.

npx dotenv-vault@latest build

Its contents should look something like this.

#/-------------------.env.vault---------------------/
#/         cloud-agnostic vaulting standard         /
#/   [how it works](https://dotenv.org/env-vault)   /
#/--------------------------------------------------/

# development
DOTENV_VAULT_DEVELOPMENT="/HqNgQWsf6Oh6XB9pI/CGkdgCe6d4/vWZHgP50RRoDTzkzPQk/xOaQs="
DOTENV_VAULT_DEVELOPMENT_VERSION=2

# production
DOTENV_VAULT_PRODUCTION="x26PuIKQ/xZ5eKrYomKngM+dO/9v1vxhwslE/zjHdg3l+H6q6PheB5GVDVIbZg=="
DOTENV_VAULT_PRODUCTION_VERSION=2

Set DOTENV_KEY

Fetch your production DOTENV_KEY.

npx dotenv-vault@latest keys production
# outputs: dotenv://:[email protected]/vault/.env.vault?environment=production

Set DOTENV_KEY on Cloud66.

app.cloud66.com

Deploy

Commit those changes safely to code and deploy.

That's it! On deploy, your .env.vault file will be decrypted and its production secrets injected as environment variables – just in time.

You'll know things worked correctly when you see 'Loading env from encrypted .env.vault' in your logs. If a DOTENV_KEY is not set (for example when developing on your local machine) it will fall back to standard dotenv functionality.

app.cloud66.com