Skip to main content

ship:oci.tap

The ship:oci.tap builds & publishes a container image for the tap service. In other words, it builds the itsmorio/morio-tap container image and publishes it.

Run npm run ship:oci.tap in the root to trigger this script.

Under the hood, this will run:

Terminal
./scripts/ship-container.sh tap
note

Container differences between development and release channel images​

This lists the differences between container images used in the develop environment (develop builds) and the container images used in the various release channels (channel builds).

These differences apply only to the containers we build/publish ourselves.
Containers we use as-is from upstream are not different between release channels.

Container contents​

  • Development builds map the local source code in the container so you can make changes to the code running within without having to enter the container
  • Channel builds bundle the source code inside the container

PM2 configuration​

For those containers using the PM2 process manager (core, api, tap):

  • Development builds run a PM2 config that includes watch mode where changes to the source code will trigger a restart.
  • Production containers use the PM2 process manager to run the NodeJS code

Container namespace​

  • Development builds use the morio namespace (which cannot be published on Dockerhub)
  • Production builds use the itsmorio namespace