amarillo/amarillo-core
5
0
Fork 0
Code Issues 17 Pull requests Packages Projects Releases Wiki Activity

Document the deployment process #21

New issue
Closed
opened 2024-11-11 12:57:02 +01:00 by Frank · 2 comments
Frank commented 2024-11-11 12:57:02 +01:00
Owner
Copy link
No description provided.
Csaba was assigned by Frank 2024-11-11 12:57:02 +01:00
Frank added this to the Amarillo project 2024-11-11 12:57:02 +01:00
Frank commented 2024-11-11 12:57:15 +01:00
Author
Owner
Copy link

E.g. for #20

E.g. for #20
Csaba commented 2024-11-14 11:43:09 +01:00
Owner
Copy link

Changing the base image

  1. make code changes locally
  2. docker build -t amarillo-custom-base .
  3. (optional) tag and push
    docker tag amarillo-custom-base git.gerhardt.io/amarillo/amarillo-custom-base
    docker push git.gerhardt.io/amarillo/amarillo-custom-base

Creating a derived image with different plugins (e.g mitanand)

  1. (optional) change the standard.Dockerfile as you like (e.g use different/local base image)
  2. build
    docker build -t amarillo-mitanand -f standard.Dockerfile --build-arg="PLUGINS=amarillo-metrics amarillo-grfs-exporter" --build-arg="DOCKER_REGISTRY=git.gerhardt.io" .
  3. tag and push
    docker tag amarillo-mitanand git.gerhardt.io/amarillo/amarillo-mitanand
    docker push git.gerhardt.io/amarillo/amarillo-mitanand

To deploy, run docker compose --profile enhancer --profile generator -p mitanand pull on the server

I have not tested how to install a locally changed plugin into the docker image. I looked into mounting volumes at build time, but it breaks portability so docker does not support it.

For automatically deploying the mitanand image, we can automate it easily. We can just create a mitanand.Dockerfile that has the GRFS plugin then build and deploy the mitanand instance from it in Jenkins. (or rename standard.Dockerfile and change it the same way)

### Changing the base image 1. make code changes locally 2. `docker build -t amarillo-custom-base .` 3. (optional) tag and push `docker tag amarillo-custom-base git.gerhardt.io/amarillo/amarillo-custom-base` `docker push git.gerhardt.io/amarillo/amarillo-custom-base` ### Creating a derived image with different plugins (e.g mitanand) 0. (optional) change the standard.Dockerfile as you like (e.g use different/local base image) 1. build `docker build -t amarillo-mitanand -f standard.Dockerfile --build-arg="PLUGINS=amarillo-metrics amarillo-grfs-exporter" --build-arg="DOCKER_REGISTRY=git.gerhardt.io" .` 2. tag and push `docker tag amarillo-mitanand git.gerhardt.io/amarillo/amarillo-mitanand` `docker push git.gerhardt.io/amarillo/amarillo-mitanand` To deploy, run `docker compose --profile enhancer --profile generator -p mitanand pull` on the server I have not tested how to install a locally changed plugin into the docker image. I looked into mounting volumes at build time, but it breaks portability so docker does not support it. For automatically deploying the mitanand image, we can automate it easily. We can just create a mitanand.Dockerfile that has the GRFS plugin then build and deploy the mitanand instance from it in Jenkins. (or rename standard.Dockerfile and change it the same way)
Csaba closed this issue 2024-11-14 11:43:09 +01:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dev
fastapi-enhancer
permissions
carpool-events
bearer-token
log-errors
grfs-export
docker-build-test
static-files
jenkins-test
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Amarillo
Assignees
Clear assignees
No assignees
Csaba
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: amarillo/amarillo-core#21
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?