Initial commit

Author: acrylic-style

.DS_Store

@@ -0,0 +1,59 @@
+name: Create and publish a Docker image
+
+on:
+  push:
+    branches: [ main ]
+
+# 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
+      attestations: write
+      id-token: write
+      #
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+      # 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
+        id: push
+        uses: docker/build-push-action@f2a1d5e99d037542a71f64918e516c093c6f3fc4
+        with:
+          context: .
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          build-args: |
+            APP_VERSION=${{ github.event.release.tag_name }}
+
+      # This step generates an artifact attestation for the image, which is an unforgeable statement about where and how it was built. It increases supply chain security for people who consume the image. For more information, see [Using artifact attestations to establish provenance for builds](/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
+      - name: Generate artifact attestation
+        uses: actions/attest-build-provenance@v3
+        with:
+          subject-name: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME}}
+          subject-digest: ${{ steps.push.outputs.digest }}
+          push-to-registry: true

.github/workflows/docker-publish.yml

@@ -0,0 +1,30 @@
+# dev
+.yarn/
+!.yarn/releases
+.vscode/*
+!.vscode/launch.json
+!.vscode/*.code-snippets
+.idea/workspace.xml
+.idea/usage.statistics.xml
+.idea/shelf
+
+# deps
+node_modules/
+
+# env
+.env
+.env.production
+
+# logs
+logs/
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+lerna-debug.log*
+
+# misc
+.DS_Store
+.idea/
+*.iml

.gitignore

@@ -0,0 +1,21 @@
+FROM node:24-alpine AS deps
+WORKDIR /app
+COPY package.json package-lock.json ./
+RUN npm ci
+
+FROM node:24-alpine AS build
+WORKDIR /app
+COPY --from=deps /app/node_modules ./node_modules
+COPY tsconfig.json ./
+COPY src ./src
+RUN npm run build
+
+FROM node:24-alpine AS runner
+WORKDIR /app
+ENV NODE_ENV=production
+COPY package.json package-lock.json ./
+RUN npm ci --omit=dev
+COPY --from=build /app/dist ./dist
+COPY config.yml ./config.yml
+EXPOSE 3000
+CMD ["node", "dist/index.js"]

Dockerfile

@@ -0,0 +1,60 @@
+# Deployman
+
+Minimal Hono server for deploying a binary payload to a configured location.
+
+## Requirements
+
+- Node.js 20+
+
+## Configure
+
+Create `config.yml` in the project root:
+
+```yml
+secret: foobar
+locations:
+  token: location
+  foobar: /srv/server/
+  file: /srv/server/some_file.txt
+```
+
+Behavior notes:
+- `locations` must include the provided `token`.
+- If the location path is a directory, the uploaded file is placed inside it.
+- If the location path is a file, the upload writes to that file.
+- If the location path does not exist, it is treated as a file path.
+
+## Run locally
+
+```bash
+npm install
+npm run dev
+```
+
+## Deploy a file
+
+```bash
+curl -X PUT \
+  --data-binary @foobar.jar \
+  "http://localhost:3000/deploy?secret=foobar&token=foobar&filename=foobar.jar"
+```
+
+Responses:
+- `201` on success
+- `401` when `secret` or `token` is invalid
+- `400` when `filename` contains `/` or `\`
+
+## Docker
+
+Build and run:
+
+```bash
+docker build -t deployman .
+docker run --rm -p 3000:3000 deployman
+```
+
+To use a host config file:
+
+```bash
+docker run --rm -p 3000:3000 -v "$PWD/config.yml:/app/config.yml" deployman
+```

README.md

@@ -0,0 +1,5 @@
+secret: foobar
+locations:
+  token: location
+  foobar: /tmp/
+  file: /tmp/some_file.txt