diff --git a/.github/workflows/docker.yml b/.github/workflows/docker.yml index 0e500bab..d3855356 100644 --- a/.github/workflows/docker.yml +++ b/.github/workflows/docker.yml @@ -10,13 +10,16 @@ on: # schedule: # - cron: '30 11 20 */3 *' -env: - REGISTRY_IMAGE: ghcr.io/${{ github.repository_owner }}/vs-fltk - jobs: build-env-image: runs-on: ubuntu-24.04 steps: + - name: set lower case owner name + run: | + echo "OWNER_LC=${OWNER,,}" >>${GITHUB_ENV} + env: + OWNER: '${{ github.repository_owner }}' + REGISTRY_IMAGE: ghcr.io/${{ env.OWNER }}/vs-fltk - name: Checkout uses: actions/checkout@v4 diff --git a/docker/.env.example b/docker/.env.example new file mode 100644 index 00000000..6386f103 --- /dev/null +++ b/docker/.env.example @@ -0,0 +1,5 @@ +HOSTUID=1000 +HOSTGID=1000 +IMAGE="ghcr.io/karurochori/vs-fltk:build-env" +ENTRYPOINT:$PWD/docker/default-entry.sh +SOURCE_ROOT=$PWD \ No newline at end of file diff --git a/docker/README.md b/docker/README.md index 4ad86142..a94d3635 100644 --- a/docker/README.md +++ b/docker/README.md @@ -8,7 +8,7 @@ file in /docker. The contents should be similar to: ```text HOSTUID=1000 HOSTGID=1000 -IMAGE="ghcr.io/KaruroChori/vs-fltk:build-env" +IMAGE="ghcr.io/karurochori/vs-fltk:build-env" ENTRYPOINT:$PWD/docker/default-entry.sh SOURCE_ROOT=$PWD ``` @@ -35,7 +35,7 @@ To run the image without using compose: docker run -it --rm -v \ --entrypoint=$PWD/docker/default-entry.sh \ -v $PWD:/workspace \ - ghcr.io/KaruroChori/vs-fltk:build-env + ghcr.io/karurochori/vs-fltk:build-env ``` --> @@ -58,7 +58,7 @@ information about working with containers. You may, for example, want to You can pull the image manually: - docker pull ghcr.io/KaruroChori/vs-fltk:build-env + docker pull ghcr.io/karurochori/vs-fltk:build-env If you use `docker-compose` or `docker run ...` the image will be pulled automatically the first time. diff --git a/docs/for-developers.md b/docs/for-developers.md index 06bddb7d..e2560476 100644 --- a/docs/for-developers.md +++ b/docs/for-developers.md @@ -205,7 +205,7 @@ Log levels are: - **VERBOSE** to be emitted when running the program in verbose mode only - **DEBUG** to be emitted always when running a debug build or in debugging mode. -Each messagge must specify their semantic type and log level (normal by default). Usually: +Each message must specify their semantic type and log level (normal by default). Usually: - `panic` messages have a `silent` log level - `ok` and `continue` messages are usually `verbose`