agaric/deploycontainer
10
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Add some versioning stuff to docs

Browse source
This commit is contained in:
Chris (wolcen) Thompson 2024-03-27 21:52:16 -04:00
parent 7a5e1de241
commit 0d127aa52f
1 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -11,10 +11,12 @@ To do a build/push to our container registry, first create a token at https://gi
Then, run: Then, run:
``` ```
docker build -t git.agaric.com/agaric/deploycontainer:latest . # finish commits and testing
git tag "0.0.X"
docker build -t git.agaric.com/agaric/deploycontainer:0.0.X
docker tag git.agaric.com/agaric/deploycontainer:0.0.X git.agaric.com/agaric/deploycontainer:latest
docker push git.agaric.com/agaric/deploycontainer:latest docker push git.agaric.com/agaric/deploycontainer:latest
``` ```
Need to verify pushing latest also includes the version...not sure
No, this is not best practice - the latest should only point to latest, and there should be a semver in use.
If you need a token for git access to git.drupalcode.org, go to https://git.drupalcode.org/-/user_settings/personal_access_tokens and grant the token api_read access. The token can be tested (i.e. inside a deploycontainer - `docker run -v .:/home/deployer -it agaric/deploycontainer:latest`) with `composer config -g gitlab-token.git.drupalcode.org {your token}` and then running composer install. If you need a token for git access to git.drupalcode.org, go to https://git.drupalcode.org/-/user_settings/personal_access_tokens and grant the token api_read access. The token can be tested (i.e. inside a deploycontainer - `docker run -v .:/home/deployer -it agaric/deploycontainer:latest`) with `composer config -g gitlab-token.git.drupalcode.org {your token}` and then running composer install.