ghost/.docker/development.entrypoint.sh

#!/bin/bash

# Mounting local code into the container overwrites the `node_modules` directories
# so we need to install dependencies again
yarn install --frozen-lockfile --prefer-offline

yarn nx run-many -t build:ts

# Execute the CMD
exec "$@"
Added opt-in `ghost` service to docker compose (#21938) ref https://linear.app/ghost/issue/ENG-1957/add-ghost-service-to-base-docker-compose-setup - Currently our `compose.yml` file only runs Ghost's supporting services, and it's expected that you'll run Ghost locally on your host machine. This commit adds a `ghost` service to our `compose.yml` file, so you can optionally run Ghost itself in a container using docker compose. - The `ghost` service is opt-in using [docker compose profiles](https://docs.docker.com/compose/how-tos/profiles/), to maintain the current behavior of only running supporting services as the default. - This commit also fixes an issue in the Dockerfile: the `WORKDIR` arg, which is used to optionally specify an alternative working directory, is not propagated from one build stage to the next, so it has to be manually added as an `ARG` in each stage. This was necessary to use the same Dockerfile for devcontainers (which require the WORKDIR to be `/workspaces/ghost`) and docker compose, where we use `/home/ghost` in alignment with the production image. 2025-01-07 14:16:43 -08:00			`#!/bin/bash`

			# Mounting local code into the container overwrites the `node_modules` directories
			`# so we need to install dependencies again`
			`yarn install --frozen-lockfile --prefer-offline`

Added docker:setup yarn script (#22058) ref https://linear.app/ghost/issue/ENG-1959/extend-setupjs-to-modify-config-as-appropriate-for-full-docker-dev - When switching from local development to docker, there are a few configuration parameters that need to be updated to e.g. point to the right database host within the docker network. - Setting these values with environment variables doesn't work well because the configuration passed via environment overrides the configuration set in tests, and thus points tests to the wrong database. - This commit adds a yarn docker:setup command to the root of the repo, to make it easier to get started with a full docker compose based workflow. It edits you config.local.json file to update the necessary settings for running Ghost in docker compose. - It also updates the clean.js script such that it will run successfully regardless of whether it is run locally or in docker. - Finally, this commit also adds convenience commands for developing and running tests in docker compose 2025-01-27 21:37:40 -08:00			`yarn nx run-many -t build:ts`

Added opt-in `ghost` service to docker compose (#21938) ref https://linear.app/ghost/issue/ENG-1957/add-ghost-service-to-base-docker-compose-setup - Currently our `compose.yml` file only runs Ghost's supporting services, and it's expected that you'll run Ghost locally on your host machine. This commit adds a `ghost` service to our `compose.yml` file, so you can optionally run Ghost itself in a container using docker compose. - The `ghost` service is opt-in using [docker compose profiles](https://docs.docker.com/compose/how-tos/profiles/), to maintain the current behavior of only running supporting services as the default. - This commit also fixes an issue in the Dockerfile: the `WORKDIR` arg, which is used to optionally specify an alternative working directory, is not propagated from one build stage to the next, so it has to be manually added as an `ARG` in each stage. This was necessary to use the same Dockerfile for devcontainers (which require the WORKDIR to be `/workspaces/ghost`) and docker compose, where we use `/home/ghost` in alignment with the production image. 2025-01-07 14:16:43 -08:00			`# Execute the CMD`
			`exec "$@"`