altf4arnold/datatracker
1
0
Fork 0
Code Issues Pull requests Actions 3 Packages Projects Releases Wiki Activity
datatracker/dev/deploy-to-container
History
Robert Sparks e5c4a9f298
feat: additional filesystem monitoring (#8405) 
* feat: additional filesystem monitoring

* chore: rename setting for tmp directory

* fix: restructure path to new endpoint

---------

Co-authored-by: Jennifer Richards <jennifer@staff.ietf.org>
2025-01-09 13:07:51 -06:00
..
.editorconfig ci: deploy-to-container tool 2022-10-26 00:04:02 -04:00
.gitignore ci: deploy-to-container tool 2022-10-26 00:04:02 -04:00
.npmrc ci: deploy-to-container tool 2022-10-26 00:04:02 -04:00
cli.js ci: fix deploy-to-container script 2024-05-16 16:34:38 -04:00
package-lock.json chore(deps): bump nanoid in /dev/deploy-to-container in the npm group (#8293) 2024-12-13 19:15:44 -05:00
package.json chore(deps): bump nanoid in /dev/deploy-to-container in the npm group (#8293) 2024-12-13 19:15:44 -05:00
README.md ci: deploy to container tool cleanup + docs 2022-10-26 00:10:29 -04:00
refresh.js ci: add disable daily DB refresh flag 2024-01-03 21:24:44 -05:00
settings_local.py feat: additional filesystem monitoring (#8405) 2025-01-09 13:07:51 -06:00
start.sh chore: remove rfc editor sync from sandbox deploy startup 2023-12-22 08:18:43 -06:00

README.md

Datatracker Deploy to Container Tool

This tool takes a release.tar.gz build file and deploys it as a container, along with its own database container.

Requirements

  • Node 16.x or later
  • Docker

Usage

  1. From the dev/deploy-to-container directory, run the command:
npm install
  1. Make sure you have a release.tar.gz tarball in the project root directory.
  2. From the project root directory (back up 2 levels), run the command: (replacing the branch and domain arguments)
node ./dev/deploy-to-container/cli.js --branch main --domain something.com

A container named dt-app-BRANCH and dt-db-BRANCH (where BRANCH is the argument provided above) will be created.