vaultwarden
/
vaultwarden-alternativa-bitwarden
mirror of https://github.com/dani-garcia/vaultwarden.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
vaultwarden-alternativa-bit.../hooks
History
BlackDex 20535065d7 Build Docker Hub images via Github Actions 
Since docker hub stopped Autobuild, we need to switch to something else.
This will trigger building of images on Github Actions and pushes them
to Docker Hub.

You only need to add 3 secrets before you merge this PR to have it working directly.

- DOCKERHUB_USERNAME : The username of the account you are going to push the builds to
- DOCKERHUB_TOKEN : The token needed to login and push builds
- DOCKERHUB_REPO : The repo name in the following form `index.docker.io/<user>/<repo>`
  So for vaultwarden that would be `index.docker.io/vaultwarden/server`

Also some small modifications to the other workflows.
 		2021-08-28 17:29:13 +02:00
..
README.md Project renaming 2021-04-27 23:18:32 +02:00
arches.sh Use Docker Buildx for multi-arch builds 2021-01-09 02:33:36 -08:00
build Project renaming 2021-04-27 23:18:32 +02:00
pre_build Add `org.opencontainers` labels to Docker images 2021-01-18 01:10:41 -08:00
push Build Docker Hub images via Github Actions 2021-08-28 17:29:13 +02:00

README.md

The hooks in this directory are used to create multi-arch images using Docker Hub automated builds.

Docker Hub hooks provide these predefined environment variables:

  • SOURCE_BRANCH: the name of the branch or the tag that is currently being tested.
  • SOURCE_COMMIT: the SHA1 hash of the commit being tested.
  • COMMIT_MSG: the message from the commit being tested and built.
  • DOCKER_REPO: the name of the Docker repository being built.
  • DOCKERFILE_PATH: the dockerfile currently being built.
  • DOCKER_TAG: the Docker repository tag being built.
  • IMAGE_NAME: the name and tag of the Docker repository being built. (This variable is a combination of DOCKER_REPO:DOCKER_TAG.)

The current multi-arch image build relies on the original vaultwarden Dockerfiles, which use cross-compilation for architectures other than amd64, and don't yet support all arch/distro combinations. However, cross-compilation is much faster than QEMU-based builds (e.g., using docker buildx). This situation may need to be revisited at some point.

References