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_VULTR.md2.2 KB · 71 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
# DEPLOY_VULTR.md — Gluecron on the Vultr box (149.28.119.158)

Current production home: **Vultr server at `149.28.119.158`**, which also
runs another platform. That platform's **custom Bun service owns ports 80/443
and terminates TLS**, so Gluecron does **not** use its bundled Caddy here.
Instead Gluecron runs as an app-only container on `127.0.0.1:3000` and the
existing Bun service reverse-proxies `gluecron.com` to it.

```
Internet ──443──> custom Bun service (existing) ──> 127.0.0.1:3000 (gluecron app)
```

## 1. DNS (Cloudflare, "DNS only" / grey cloud)

| Type | Name           | Content           |
|------|----------------|-------------------|
| A    | `gluecron.com` | `149.28.119.158`  |
| A    | `www.gluecron.com` | `149.28.119.158` |

Remove the old Vercel `www` CNAME and the `_vercel` TXT verification record.

## 2. One-time box setup

```sh
command -v docker >/dev/null || curl -fsSL https://get.docker.com | sh
git clone https://github.com/ccantynz-alt/Gluecron.com.git /opt/gluecron
cd /opt/gluecron
git checkout claude/site-migration-vercel-XstpK
cp .env.example .env
# Edit .env — at minimum set DATABASE_URL (Neon) and APP_BASE_URL=https://gluecron.com
nano .env
```

## 3. Deploy (app only — bundled Caddy is skipped)

`docker-compose.override.yml` publishes the app on `127.0.0.1:3000` and
disables git-over-SSH. Bring up only the `gluecron` service:

```sh
docker compose up -d --build gluecron
docker compose exec gluecron bun run db:migrate   # first deploy only
curl -s localhost:3000/healthz                     # -> ok
```

## 4. Point the existing Bun proxy at it

Add a virtual-host route in the custom Bun service so requests for
`gluecron.com` (and `www.gluecron.com`) proxy to `http://127.0.0.1:3000`.
The Bun service keeps owning TLS on :443.

## 5. Verify

```sh
curl -sI https://gluecron.com/healthz   # 200 ok, served via the Bun proxy
```

- `https://gluecron.com/healthz``ok`
- `https://gluecron.com/readyz``ok`
- `https://gluecron.com/status`  → status page

## Later redeploys

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

## Rollback

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