deploycontainer/README.md

# DEPLOY CONTAINER

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/applications. Grant the token read/write access to the "package" option. Use this token along with your user name to login with:
`docker login git.agaric.com`

Then, run:
```
docker build -t 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.

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.
Update readme with some basic instructions 2024-03-26 21:43:15 +00:00			`# DEPLOY CONTAINER`
Initial commit 2024-03-25 17:05:14 +00:00
Update readme with some basic instructions 2024-03-26 21:43:15 +00:00			`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.`

Add notes about using tokens, etc Also improve user experience: cd to home 2024-03-26 22:11:12 +00:00			`To do a build/push to our container registry, first create a token at https://git.agaric.com/user/settings/applications. Grant the token read/write access to the "package" option. Use this token along with your user name to login with:`
Update readme with some basic instructions 2024-03-26 21:43:15 +00:00			`docker login git.agaric.com`

			`Then, run:`
			```
Reduce layer count and update docs 2024-03-28 01:49:39 +00:00			`docker build -t git.agaric.com/agaric/deploycontainer:latest .`
Update readme with some basic instructions 2024-03-26 21:43:15 +00:00			`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.`
Add notes about using tokens, etc Also improve user experience: cd to home 2024-03-26 22:11:12 +00:00
			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.