added docker files and automated build scripts

This commit is contained in:
michael-bailey 2023-11-25 20:54:05 +00:00
parent 20b1398d13
commit 3dfa71a7b1
4 changed files with 70 additions and 14 deletions

7
.dockerignore Normal file
View File

@ -0,0 +1,7 @@
.gitignore
/target
/docs
/.vscode
/.idea
/.github

View File

@ -0,0 +1,48 @@
#
name: create-docker-image
# Configures this workflow to run every time a change is pushed to the branch called `release`.
on:
push:
branches: ['master']
# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
env:
REGISTRY: ghcr.io
IMAGE_NAME: ${{ github.repository }}
# There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
jobs:
build-and-push-image:
runs-on: ubuntu-latest
# Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
permissions:
contents: read
packages: write
#
steps:
- name: Checkout repository
uses: actions/checkout@v4
# Uses the `docker/login-action` action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
- name: Log in to the Container registry
uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
with:
registry: ${{ env.REGISTRY }}
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
# This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
- name: Extract metadata (tags, labels) for Docker
id: meta
uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7
with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
# This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
# It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
# It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
- name: Build and push Docker image
uses: docker/build-push-action@f2a1d5e99d037542a71f64918e516c093c6f3fc4
with:
context: .
push: true
tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}

View File

@ -1,11 +1,12 @@
# First stage: build the server file.
FROM rust:alpine3.16 AS build
WORKDIR /app # avoid the root directory
COPY ./ ./
RUN cargo build --release --bin server
FROM rust:alpine AS build
# Second stage: actually run the server file.
FROM alpine:latest
WORKDIR /app
COPY --from=build /app/target/release/server ./server
CMD server
RUN apk add musl-dev
RUN apk upgrade --update-cache --available && \
apk add openssl-dev && \
rm -rf /var/cache/apk/*
COPY . .
CMD ["cargo", "run", "--release", "--bin", "server"]

View File

@ -20,7 +20,7 @@ path = "src/main.rs"
[dependencies]
chrono = "0.4"
clap = {version = "3.2.5", features = ["derive"]}
clap = {version = "4.4.8", features = ["derive"]}
uuid = {version = "1.1.2", features = ["serde", "v4"]}
serde = { version = "1.0", features = ["derive"] }
serde_json = "1.0"
@ -33,10 +33,10 @@ futures = "0.3.16"
async-trait = "0.1.52"
actix = "0.13"
rhai = {version = "1.7.0"}
mlua = { version = "0.8.1", features=["lua54", "async", "serde", "macros", "vendored"] }
libloading = "0.7"
toml = "0.5.9"
aquamarine = "0.1.11"
mlua = { version = "0.9.2", features=["lua54", "async", "serde", "macros", "vendored"] }
libloading = "0.8.1"
toml = "0.8.8"
aquamarine = "0.3.2"
tokio-stream = "0.1.9"
foundation = {path = '../foundation'}