From d2c8279d8852b3215d50a649bff32fe843d5f357 Mon Sep 17 00:00:00 2001 From: "Chris (wolcen) Thompson" Date: Tue, 26 Mar 2024 17:43:15 -0400 Subject: [PATCH] Update readme with some basic instructions --- README.md | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index af84990..77c14a6 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,19 @@ -# deploycontainer +# DEPLOY CONTAINER -A container for use with ForgeJo actions to deploy a Drupal site. \ No newline at end of file +A container for use with ForgeJo runner/actions to deploy a Drupal site. + +It is based on the PHP image, adding node, composer, and a few other items we need. + +Given node is included, most forgejo/actions *should* work, but some may have other dependencies. + +To do a build/push to our container registry, first create a token at https://git.agaric.com/user/settings and login using your user name and that token with: +`docker login git.agaric.com` + +Then, run: +``` +docker build -t agaric/deploycontainer:latest . +docker tag agaric/deploycontainer:latest git.agaric.com/agaric/deploycontainer:latest +docker push git.agaric.com/agaric/deploycontainer:latest +``` + +No, this is not best practice - the latest should only point to latest, and there should be a semver in use.