Tools [active]

AppForge

A Bash CLI that turns prebuilt Node.js and Next.js artifacts into running Docker containers on an application VM, with no Git pull or build pipeline on the server.

Tech
Bash · Docker · Docker Compose · Node.js
View on GitHub ↗

Problem

Hosting several small Node.js apps on one VM tends to drift: each app gets a hand-written Dockerfile, ports are picked by memory, and updates happen differently every time. AppForge makes one config file per app the single source of truth and generates everything else from it.

What it does

  • Full lifecycle per app: create, start, stop, restart, deploy, rebuild, logs, shell, status, config, remove.
  • Two modes: an interactive menu for operators and one-shot commands for scripts or remote SSH.
  • Generates Dockerfile, docker-compose.yml, and app.env from templates (nextjs and node built in; a new type is just a new template folder).
  • Validates app IDs, Node versions, port format, port collisions between apps, and that the artifact exists.
  • Basic health check: container state plus an HTTP probe to 127.0.0.1:APP_PORT.
  • Destructive actions (remove, prune) always ask for confirmation.

It deliberately does not handle Nginx, SSL, DNS, CI/CD, or monitoring. A separate reverse proxy VM forwards traffic to VM-IP:APP_PORT.

How it works

config/apps/myapp.env
        │  render template
        ▼
generated/myapp/  (Dockerfile, docker-compose.yml, app.env)
        │  docker compose build + up
        ▼
container appforge-myapp :APP_PORT

Usage

# On the server, once
./appforge.sh setup wizard   # checks Docker, permissions, directories
./appforge.sh doctor         # read-only preflight check

# Add an app
./appforge.sh create myapp   # prompts for name, type, Node version, port

# From a laptop or CI, after building:
scp -r myapp-build/* deploy@server:/opt/appforge/apps/myapp/

# On the server
./appforge.sh deploy myapp

Configuration example

APP_ID=myapp
APP_NAME=My App

APP_TYPE=nextjs
NODE_VERSION=22

APP_PORT=3101
INTERNAL_PORT=3000

NODE_ENV=production

Any other KEY=value line (for example DATABASE_URL) is passed to the container. Values are read literally, never evaluated as shell.

Notes

  • Updating means copying a new artifact and running deploy again.
  • Templates use a single-stage build for now. Multi-stage builds and more app types (nestjs, express, static) are on the roadmap.