1
Fork 0

Compare commits

...

2 commits

Author SHA1 Message Date
b3b43742ee update
All checks were successful
continuous-integration/drone Build is passing
2024-06-07 17:47:55 -04:00
beda9b9bf4 Add bin 2024-06-07 17:47:49 -04:00
2 changed files with 15 additions and 2 deletions

View file

@ -50,4 +50,15 @@ steps:
- git clone https://codeberg.org/Hyperpipe/Hyperpipe && cd ./Hyperpipe/
- echo $ARK_PASSWORD | docker login ark.sudovanilla.org --username $ARK_USERNAME --password-stdin
- docker build -t ark.sudovanilla.org/korbs/hyperpipe:arm64 .
- docker push ark.sudovanilla.org/korbs/hyperpipe:arm64
- docker push ark.sudovanilla.org/korbs/hyperpipe:arm64
- name: Bin
environment:
ARK_USERNAME:
from_secret: ARK_USERNAME
ARK_PASSWORD:
from_secret: ARK_PASSWORD
commands:
- git clone https://github.com/w4/bin && cd ./bin/
- echo $ARK_PASSWORD | docker login ark.sudovanilla.org --username $ARK_USERNAME --password-stdin
- docker build -t ark.sudovanilla.org/korbs/bin:arm64 .
- docker push ark.sudovanilla.org/korbs/bin:arm64

View file

@ -2,4 +2,6 @@
[![Build Status](https://ci.sudovanilla.org/api/badges/Korbs/4get-build-automation/status.svg)](https://ci.sudovanilla.org/Korbs/4get-build-automation)
SudoVanilla does not pull from Docker Hub, in response to this, builds are done manually on server and pushed here to SudoVanilla Ark.
Pretty much everything is running on Docker on SudoVanilla's server, however I refuse to pull images from Docker Hub as it is proprietary. To get around this, builds are done via automation on server, with a selfhosted Drone instance, and pushed here to SudoVanilla Ark.
Another reason for this, is that some projects either don't provide an image or don't have an image available for the arm64 arch(SudoVanilla server runs on a M2 chip, Asahi Linux).