B4L/cnx_vinyl

Private

Public Access

0 Fork 0

Files

T

History

grabowski 9ed51f4b22

Deploy test site / deploy (push) Successful in 51s

Details

Factory console and customer order status: investor demo

New page docs/factory-console.html (site /demos/factory/): the factory
application of digital-factory.md on a simulated plant day, with a
switch to the customer portal of the same orders.

Factory console (sidebar: Floor, Orders, Quality, Lab, Metal, Ledger):
- floor: five presses of the launch fleet (two Newbilt Duplex systems,
  one Classic) with the mounted order, live good / rejected counters,
  stamper plays against life, cycle time and steam; KPIs for the day;
  live optical inspection stream with record keys; alerts (stops, lab
  holds, stampers near end of life, listening reviews, long gate waits);
  stations (cutting, galvanics, stamper prep, lab, packing); orders by
  stage; good records per day
- orders list with stage filters and search; order detail with stage
  track, approvals, metal genealogy and stamper metrology, press run
  telemetry, compound lot certificate, rejects by reason, audio samples,
  packing and shipping, and the order's events
- press detail with telemetry sparklines; quality (rejects by reason,
  yield per press, audio comparison); lab (compound lots with results
  against illustrative limits, one lot on hold with re-dry and retest,
  regrind batches, hoppers); metal (baths, mounted stampers, metrology,
  archive); hash-chained event log

Customer portal (four demo customers: pressing now, waiting to approve
the test pressing, in plating, delivered): progress through every step
and the three gates, copies pressed so far with the latest copies and
their record keys, approving the test pressing books the press slot
(greedy plan of the queue gives the start time and press), and a quality
report that fills in step by step: files, lacquers, metal parts with
metrology, test pressings, the compound lot's lab results, pressing and
inspection, listening checks, packing.

Simulation: 60 days warmed up at load (about 0.7 s), then 1x to 3600x.
Stages and durations from the production timeline, Newbilt cycle times,
two shifts 06:00 to 22:00, unplanned stops, stamper life 1,000 to 2,000
plays, audio sampling first-off plus about 1 in 50 (1 in 25 near end of
life), compound lots through the lab gate and release test pressing.
All orders, values and IDs are simulated; limits are illustrative.

Linked from digital-factory.md (the factory application), traceability.md
(customer-facing view), the README and the landing page.

2026-10-16 10:17:19 +07:00

public

Factory console and customer order status: investor demo

2026-10-16 10:17:19 +07:00

build.sh

Factory console and customer order status: investor demo

2026-10-16 10:17:19 +07:00

Caddyfile

Add the cnxvinyl.lol test site with a Gitea deploy workflow

2026-10-02 20:59:38 +02:00

README.md

Deploy workflow: check the SSH key and log its fingerprint

2026-10-02 21:14:33 +02:00

README.md

Test site: cnxvinyl.lol

https://cnxvinyl.lol/ is the internal test site for this repository: demo pages from docs/ (the plant operation page first) and any static site we want to show by link. It runs on the same web server as buildfor.life (Debian VPS s1, Caddy behind Cloudflare) and is not a plant service; plant systems follow the digital factory plan. Every page and file is sent with noindex and robots.txt disallows everything; nothing is behind a login unless basic_auth in the Caddyfile is switched on.

How it is built

public/ is copied verbatim to the web root: the landing page (index.html), robots.txt, and any static site as its own directory (public/<name>/index.html is served at /<name>/).
build.sh assembles site/dist: public/ plus every entry in its DEMOS list, which copies a page out of docs/ (for example docs/plant-operation.html to /demos/plant-operation/), so the docs stay the one source. It writes version.txt (the commit) and fails on any internal link that does not resolve.
To add a demo: one line in DEMOS, one entry on the landing page. To add a static site: drop its built output in public/<name>/ and link it.
Local preview: bash site/build.sh, then open site/dist/index.html.

How it is deployed

.gitea/workflows/deploy-site.yml runs on every push to master that touches site/, an HTML page under docs/, or the workflow itself, and on demand (Actions tab, "Run workflow"). It builds, rsyncs site/dist into the idle one of /var/www/cnxvinyl.lol and /var/www/cnxvinyl.lol-prev, swaps them by rename (the blog's pattern), checks version.txt on the server, purges the Cloudflare cache when the token is set, and finally checks the public URL (warning only).

The deploy owns the whole web root: anything put into /var/www/cnxvinyl.lol by hand disappears on the next deploy. Static sites go into public/ instead.

One-time setup

DNS in Cloudflare, both proxied (orange cloud): cnxvinyl.lol CNAME s1.buildfor.life and www CNAME cnxvinyl.lol (Cloudflare flattens the apex CNAME, so the site follows s1 if its address changes). SSL/TLS mode Full (strict): "Flexible" makes a redirect loop with Caddy.
Caddy on s1: append Caddyfile to /etc/caddy/Caddyfile (the comments in it list the checks), caddy validate, then systemctl reload caddy. Caddy gets the certificate the same way it does for the buildfor.life apex.
Web root: the deploy user must be able to create and rename directories in /var/www, as it already does for the blog. If not: sudo install -d -o <deploy user> /var/www/cnxvinyl.lol /var/www/cnxvinyl.lol-prev and make /var/www writable for that user (the swap renames entries in it).
Secrets in Gitea (repo: Settings > Actions > Secrets, or user level so every repo of the account gets them): VPS_HOST, VPS_USER, VPS_SSH_KEY, optionally VPS_PORT (default 22), VPS_KNOWN_HOSTS (output of ssh-keyscan -p <port> s1.buildfor.life, pins the host key), CLOUDFLARE_ZONE_ID and CLOUDFLARE_API_TOKEN (Zone > Cache Purge on cnxvinyl.lol). The names match the blog's workflow, so the blog's deploy key and values work unchanged: s1 only checks the key against the deploy user's authorized_keys, whichever repository sends it. Gitea secrets cannot be read back, so they are entered again here from the private key file; repo secrets set on B4L/buildfor_life_web do not reach this repository, B4L organisation secrets only reach it if it moves into B4L. The blog key is deploy@s1.b4l.co.th, fingerprint SHA256:o4w7HL+EsPI3MXbbcYWGn0EykN7qeLtYg0Tc9FI1a3s, and it is the only key in /home/deploy/.ssh/authorized_keys on s1 (sshd on port 2255, so VPS_PORT is 2255). The deploy log prints the fingerprint of the key in VPS_SSH_KEY; if it differs, the server answers "Permission denied (publickey)". If the private key is gone, make a new key instead: ssh-keygen -t ed25519 -N "" -C cnx_vinyl-deploy -f cnx_vinyl-deploy, public half into the deploy user's ~/.ssh/authorized_keys on s1, private half into VPS_SSH_KEY, then delete the local copy.
Runner: the job asks for ubuntu-latest, the label the blog's runner serves. This repository is under a user account, not the B4L organisation, so a runner registered only for B4L does not pick it up; if the run stays "Waiting", register the runner for this repository or instance-wide, or move the repository into B4L.
Run the workflow once from the Actions tab and open https://cnxvinyl.lol/.