Pre-launch — Gluecron is in final validation. Public signups and git hosting for non-owner users open after launch review.
CodeIssuesDiscussionsWikiPull RequestsProjectsCommitsActionsReleasesContributorsPulse● GatesSecuritySettingsDeploymentsPipelineInsightsAgents✨ Explain✨ Ask AI✨ Workspace✨ Spec✨ Tests▓ Debt Map✨ NL Search🏛 Archaeology
claude/adoring-hopper-5x74bqclaude/affectionate-feynman-ykrf1hclaude/architecture-audit-design-wxprenclaude/build-status-update-3MXsfclaude/charming-meitner-mllb5rclaude/compare-gate-gluecron-s4mFQclaude/confident-faraday-tikcwbclaude/continue-work-XMTlIclaude/crontech-gluecron-deploy-7MIECclaude/crontech-platform-setup-SeKfwclaude/design-2026claude/ecstatic-ptolemy-jMdigclaude/enhance-github-integration-QNHdGclaude/fix-aa-loop-issue-PonMQclaude/fix-actions-and-processclaude/fix-desktop-errors-XqoW8claude/fix-red-workflowsclaude/fix-website-access-6FKJNclaude/gatetest-integration-hardeningclaude/github-audit-improvements-bDFr9claude/gluecron-launch-status-FoMRlclaude/hopeful-lamport-olfCTclaude/issue-to-pr-and-protectionsclaude/jolly-heisenberg-2sg1Qclaude/launch-preparation-QmTb6claude/new-session-xk1l7claude/plan-platform-architecture-kkN4yclaude/platform-analysis-roadmap-1nUGLclaude/platform-launch-assessment-8dWV8claude/polish-platform-release-AeDrUclaude/resume-previous-work-KzyLwclaude/review-crontech-handoff-qYEVqclaude/review-project-completeness-lHhS2claude/review-readme-docs-ulqPKclaude/serene-edison-rj87weclaude/setup-multi-repo-dev-BCwNQclaude/ship-fixes-and-tests-Jvz1cclaude/site-audit-competitive-pctlwgclaude/site-migration-vercel-XstpKclaude/standalone-product-repos-XHFTDcopilot/feat-smart-empty-states-keyboard-first-enhancementcopilot/feat-smart-morning-digest-review-context-restorecopilot/fix-and-process-workflowscopilot/update-ai-powered-code-reviewfeat/debt-mapfeat/push-policy-codeowners-hardeningfeat/smart-digest-contextfeat/stage-impactfeat/t1-secret-migrationfeat/u-polishfeat/w-self-hostfeat/w2-claude-configfix/agent-journey-orphan-sweepgatetest/auto-fix-1776586424172gatetest/auto-fix-1776586534814gatetest/auto-fix-1776590685143gatetest/auto-fix-1776590808199mainops/redeploy-retriggerstyle/dxt-cta-themeworktree-agent-a3377aad30d55da26worktree-agent-a7ef607b7ee1d6c74
DEPLOY_METAL.md2.2 KB · 81 lines
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
# DEPLOY_METAL.md — metal-box deploy (interim)

This is the shortest path to gluecron.com being live on the existing Vultr
box at `45.76.171.37`. It's a stop-gap — everything migrates onto Crontech
once Crontech is absorbing hosting, and DNS gets flipped (to Fly.io briefly
or straight to Crontech) at that point. Don't polish this; throw it away
later.

## What's already in place

- DNS: `gluecron.com` and `www.gluecron.com` A records point at
  `45.76.171.37`. Proxy status is "DNS only" in Cloudflare — keep it that
  way for the cert handshake.
- `Dockerfile`, `docker-compose.yml`, and `Caddyfile` are all in the repo.
  `docker compose up -d` brings up both the app and Caddy (auto-HTTPS via
  Let's Encrypt).
- App exposes `/healthz`, `/readyz`, `/status` per BUILD_BIBLE §2.6.

## One-time box setup

1. SSH in: `ssh root@45.76.171.37`
2. Install Docker (skip if already installed):
   ```sh
   curl -fsSL https://get.docker.com | sh
   ```
3. Clone the repo:
   ```sh
   git clone https://github.com/ccantynz-alt/Gluecron.com.git /opt/gluecron
   cd /opt/gluecron
   ```
4. Create `.env` (copy from `.env.example` and fill the real values — at
   minimum `DATABASE_URL` pointing at Neon):
   ```sh
   cp .env.example .env
   vim .env
   ```

## Deploy

```sh
cd /opt/gluecron
git pull
docker compose up -d --build
```

First run: Caddy requests a Let's Encrypt cert. Watch:
```sh
docker compose logs -f caddy
```

Once you see `certificate obtained successfully`, hit:
- `https://gluecron.com/healthz``ok`
- `https://gluecron.com/readyz``ok`
- `https://gluecron.com/status` → status page

## First-time DB migration

After the container is up:
```sh
docker compose exec gluecron bun run db:migrate
```

## Later redeploys

```sh
cd /opt/gluecron && git pull && docker compose up -d --build
```

## Rollback

```sh
cd /opt/gluecron && git checkout <prev-sha> && docker compose up -d --build
```

## When Crontech absorbs this

1. Point DNS at the Crontech edge (Caddy on the Crontech box, or whatever
   Crontech routes through).
2. Push gluecron.com via git to Crontech — BLK-009 deploy pipeline builds
   and serves it.
3. Tear down this box. Nothing here is worth preserving.