0
0
Fork
You've already forked ping
0
A docker container to ping
squirl daccf11f20
All checks were successful
build / build (push) Successful in 1m8s
updated ci and nginx
2025年12月16日 19:21:09 +01:00
.forgejo/workflows updated ci and nginx 2025年12月16日 19:21:09 +01:00
ping Initial commit 2024年08月23日 20:57:54 +02:00
.gitignore Initial commit 2024年08月23日 20:57:54 +02:00
dockerfile updated ci and nginx 2025年12月16日 19:21:09 +01:00
nginx.conf changed the network port, updated nginx 2025年09月05日 13:53:38 +02:00
readme.md changed the network port, updated nginx 2025年09月05日 13:53:38 +02:00
unlicence Initial commit 2024年08月23日 20:57:54 +02:00

Ping docker image

A web server for serving a pong response.

Usage

Start the container, and expose port 80. Goto the url of the server, and see the response pong.

Running in docker

Docker compose in a production environment:

services:
 ping:
 image: codeberg.org/squirl/ping:latest
 restart: always
 ports:
 - "8080:80"

Docker compose in a development environment (local build):

services:
 ping:
 build:
 context: .
 dockerfile: dockerfile
 restart: always
 ports:
 - "8080:80"

CI

This repo comes with automatic builds on push, and makes a release on a tag push (automatic release triggers on tag v..). CI needs to have access to the repos api. Goto the applications settings and generate a token, with repo and package read and write access. Next, add the api key to actions of the repo as a secret, under the key REGISTRY_API_KEY. Don't forget to enable actions and the package repository for the repo. Also don't forget to link the package to the repo, as this is not done automatically.

Further env variables:

  • RUNNER_CERT_PATH: Path to the docker in docker certs (in my case: /certs/client)
  • RUNNER_DOCKER_HOST: Hostname for the docker in docker instance, as define when creating the runner (in my case: codeberg-docker)
  • RUNNER_IMAGE_NAME: Image name of the container (in this case: ping)
  • RUNNER_REPO_URL: URL of the forgejo container registry (in my case: codeberg.org)