Update readme with some basic instructions
This commit is contained in:
parent
69b1e798d7
commit
d2c8279d88
1 changed files with 18 additions and 2 deletions
20
README.md
20
README.md
|
@ -1,3 +1,19 @@
|
||||||
# deploycontainer
|
# DEPLOY CONTAINER
|
||||||
|
|
||||||
A container for use with ForgeJo actions to deploy a Drupal site.
|
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.
|
||||||
|
|
Loading…
Reference in a new issue