You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://hellonear.xyz answers 307 to https://app.hellonear.xyz/, as deploy/README.md says it will "until that is deployed".
deploy/systemd/ has only hellonear-be, hellonear-engine and hellonear-fe. deploy.sh doesn't build apps/landing.
The landing's Choose buttons open https://app.hellonear.xyz/minds/new?template=<id>, and the app already keeps that pick through sign-in. So nothing in the app needs to change.
To deploy (James, with Axel's approval: it changes the box)
Build apps/landing in deploy.sh (next build), plus a hellonear-landing.service running next start on its own port.
Point the apex hellonear.xyz at that port on the tunnel host. It's currently on 3000, the web app, and apps/fe/next.config.js redirects it to app..
Remove the apex redirect from apps/fe/next.config.js once the apex serves the landing (FE, mine).
Copy to check before it goes live (Nabil)
"Every payment asks you first" is true by default, but since #167 the owner can let a Mind send small payments to listed accounts without asking ("Approved by your rule"). It appears in:
app/layout.tsx (the page description, shown in search results and link previews)
components/ApprovalsScroll.tsx (the section title)
components/Demo.tsx ("Stay in charge")
components/MindGraph.tsx (the Payments Mind's line)
One option is "Every payment asks you first, unless you set a rule." Your call.
@Lexirieru The deploy part is ready on the branch feat/deploy-landing (3 commits, from main at 8b9f947). May I open the PR?
What it changes
New deploy/systemd/hellonear-landing.service: next start on port 3100 (the web app keeps 3000), with the same hardening as hellonear-fe and MemoryMax=384M.
deploy/deploy.sh builds apps/landing on the deploying machine, the same way as apps/fe, and ships only its .next. The box then:
installs the landing's production dependencies;
starts and restarts hellonear-landing with the other units;
waits until port 3100 answers before it calls the deploy healthy.
Rollback stops the landing when release-old has none. The hand-edit check skips apps/landing/.next.
deploy/README.md and apps/landing/CLAUDE.md are updated.
Tests
The landing build from a clean git archive on ct-dev passes in 14 s, and the shipped .next is 11 MB.
I ran it with production dependencies only, as on the box. Results:
home 200 (293 KB) and icon 200;
/hero assets 200 with the Cache-Control from next.config.ts;
128 MB RSS;
TypeScript isn't needed at runtime.
DEPLOY_CHECK_ONLY=1 against the hosted box: box matches git 8b9f947, no new migrations, "would deploy 8da3255".
Not run: a real deploy of the branch (that needs your approval) and the apps/be integration and load tests (no backend change).
Order after the merge, so nothing breaks
The merge deploys the landing on 3100. hellonear.xyz still goes to the web app and its redirect, so nothing visible changes yet.
Me, on infra I run:
let the tunnel host in on 3100 in the container's Proxmox firewall (today only 3000 and 4000 are open);
point the apex ingress rule at 3100, with a backup of the tunnel config first.
No DNS change is needed: the apex record already goes to the tunnel.
@AncungAulia removes the apex redirect from apps/fe/next.config.js (step 3 in this issue).
Does approving the PR cover step 2 too, or do you want to approve it separately?
Demo video: without a video URL, the demo section shows its placeholder (public/demo/ is gitignored). Once the video (#10) has a public URL, it can be set as DEPLOY_LANDING_VIDEO_URL for the deploy. It's a public value, not a secret.
The copy question in this issue is for @Nabil-Aufa; this branch doesn't touch it.
Open the PR. I'll review and test it, then merge after CI passes (that merge deploys the landing on 3100, per rule 3).
Step 2 is approved together with that merge, and only after it: open 3100 to the tunnel host in the Proxmox firewall, then point the apex ingress at 3100, with a backup of the tunnel config first. Please wait for the copy below before pointing the apex. Afterwards, post on this issue:
hellonear.xyz shows the landing;
a Choose button opens app.hellonear.xyz/minds/new?template=…;
app.hellonear.xyz still works and health is ok;
the rollback (the backed-up tunnel rule).
@Nabil-Aufa before the apex goes live, please fix the copy in the issue body: "Every payment asks you first" stopped being always true with #167 (auto-approve rules). For example: "Every payment asks you first, unless you set a rule." It appears in app/layout.tsx, components/ApprovalsScroll.tsx, components/Demo.tsx and components/MindGraph.tsx. Open a PR; Axel approves the merge.
@AncungAulia after the apex serves the landing, please remove the apex redirect in apps/fe/next.config.js (step 3).
@Lexirieru The copy is fixed in #271, using the wording from this issue ("Every payment asks you first, unless you set a rule."). It's in all four places, plus the approvals subtitle, which had the same problem ("Nothing leaves the wallet until you tap Approve"). Typecheck and build pass. Once Axel merges it, the apex can point at the landing.
Step 2 done (Axel's approval on #267, after #271 was merged and deployed): https://hellonear.xyz now serves the landing page. Live revision 92f1894 (includes #271).
What changed, each with a backup first:
Proxmox firewall of the box: one new rule, port 3100 open from the tunnel host only (like 3000 and 4000). Checked: 3100 answers 200 from the tunnel host and stays blocked from the rest of the LAN.
Tunnel ingress: the hellonear.xyz rule now points at port 3100 instead of 3000. cloudflared ingress validate OK, and ingress rule https://hellonear.xyz/ matches 3100. No other rule changed.
Checks after the switch:
https://hellonear.xyz/ → 200, the landing (title "HelloNear: a Mind that can't spend more than you allow"), with the new copy ("Every payment asks you first, unless you set a rule").
The three Choose links go to https://app.hellonear.xyz/minds/new?template=general-assistant, payments-mind, email-manager; each answers 200.
https://app.hellonear.xyz/ → 200; GET https://api.hellonear.xyz/v1/health → {"ok":true,"engine":true,"revision":"92f1894"}. hellonear.jameshub.fun still redirects to app.hellonear.xyz.
All four units active, 0 http error lines; try-out end to end 22/22.
Rollback: put the hellonear.xyz rule back to port 3000 (the backed-up tunnel config) and restart cloudflared; the apex then goes back to the web app's redirect to app.hellonear.xyz. The firewall rule can stay.
@AncungAulia the apex redirect in apps/fe/next.config.js no longer gets any traffic for hellonear.xyz, so it can be removed (#266).
Activity
Lin1er commentedon Nov 12, 2026
@Lexirieru The deploy part is ready on the branch
feat/deploy-landing(3 commits, frommainat8b9f947). May I open the PR?What it changes
deploy/systemd/hellonear-landing.service:next starton port 3100 (the web app keeps 3000), with the same hardening ashellonear-feandMemoryMax=384M.deploy/deploy.shbuildsapps/landingon the deploying machine, the same way asapps/fe, and ships only its.next. The box then:hellonear-landingwith the other units;release-oldhas none. The hand-edit check skipsapps/landing/.next.deploy/README.mdandapps/landing/CLAUDE.mdare updated.Tests
git archiveon ct-dev passes in 14 s, and the shipped.nextis 11 MB./heroassets 200 with theCache-Controlfromnext.config.ts;DEPLOY_CHECK_ONLY=1against the hosted box:box matches git 8b9f947, no new migrations, "would deploy 8da3255".apps/beintegration and load tests (no backend change).Order after the merge, so nothing breaks
The merge deploys the landing on 3100.
hellonear.xyzstill goes to the web app and its redirect, so nothing visible changes yet.Me, on infra I run:
No DNS change is needed: the apex record already goes to the tunnel.
@AncungAulia removes the apex redirect from
apps/fe/next.config.js(step 3 in this issue).Does approving the PR cover step 2 too, or do you want to approve it separately?
Demo video: without a video URL, the demo section shows its placeholder (
public/demo/is gitignored). Once the video (#10) has a public URL, it can be set asDEPLOY_LANDING_VIDEO_URLfor the deploy. It's a public value, not a secret.The copy question in this issue is for @Nabil-Aufa; this branch doesn't touch it.
Lexirieru commentedon Nov 12, 2026
@Lin1er approved by Axel:
hellonear.xyzshows the landing;app.hellonear.xyz/minds/new?template=…;app.hellonear.xyzstill works and health is ok;@Nabil-Aufa before the apex goes live, please fix the copy in the issue body: "Every payment asks you first" stopped being always true with #167 (auto-approve rules). For example: "Every payment asks you first, unless you set a rule." It appears in
app/layout.tsx,components/ApprovalsScroll.tsx,components/Demo.tsxandcomponents/MindGraph.tsx. Open a PR; Axel approves the merge.@AncungAulia after the apex serves the landing, please remove the apex redirect in
apps/fe/next.config.js(step 3).Merge pull request #267 from Hellonear-AI/feat/deploy-landing
Nabil-Aufa commentedon Nov 12, 2026
@Lexirieru The copy is fixed in #271, using the wording from this issue ("Every payment asks you first, unless you set a rule."). It's in all four places, plus the approvals subtitle, which had the same problem ("Nothing leaves the wallet until you tap Approve"). Typecheck and build pass. Once Axel merges it, the apex can point at the landing.
🤖 Generated with Claude Code
Merge pull request #271 from Hellonear-AI/fix/landing-payment-copy
Lin1er commentedon Nov 12, 2026
Step 2 done (Axel's approval on #267, after #271 was merged and deployed): https://hellonear.xyz now serves the landing page. Live revision
92f1894(includes #271).What changed, each with a backup first:
hellonear.xyzrule now points at port 3100 instead of 3000.cloudflared ingress validateOK, andingress rule https://hellonear.xyz/matches 3100. No other rule changed.Checks after the switch:
https://hellonear.xyz/→ 200, the landing (title "HelloNear: a Mind that can't spend more than you allow"), with the new copy ("Every payment asks you first, unless you set a rule").https://app.hellonear.xyz/minds/new?template=general-assistant,payments-mind,email-manager; each answers 200.https://app.hellonear.xyz/→ 200;GET https://api.hellonear.xyz/v1/health→{"ok":true,"engine":true,"revision":"92f1894"}.hellonear.jameshub.funstill redirects toapp.hellonear.xyz.http errorlines; try-out end to end 22/22.Rollback: put the
hellonear.xyzrule back to port 3000 (the backed-up tunnel config) and restartcloudflared; the apex then goes back to the web app's redirect toapp.hellonear.xyz. The firewall rule can stay.@AncungAulia the apex redirect in
apps/fe/next.config.jsno longer gets any traffic forhellonear.xyz, so it can be removed (#266).Merge pull request #272 from Hellonear-AI/chore/fe-drop-apex-redirect