Tweak hero copy to make a visible update for pipeline test
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
+7
-5
@@ -26,12 +26,14 @@
|
||||
<main>
|
||||
<section class="hero">
|
||||
<div class="container">
|
||||
<p class="eyebrow">Deployment demo</p>
|
||||
<h1>A static site, shipped on every <code>git push</code>.</h1>
|
||||
<p class="eyebrow">Live deployment demo</p>
|
||||
<h1>Pushed, built and rolled out — all from one <code>git push</code>.</h1>
|
||||
<p class="lede">
|
||||
Gitea Actions builds the container, pushes to the internal registry,
|
||||
then Swarm does a zero-downtime rolling update behind Traefik.
|
||||
No manual steps after the first deploy.
|
||||
Gitea Actions picks up every commit on <code>main</code>, builds a
|
||||
fresh container image tagged with the commit SHA, pushes it to the
|
||||
internal registry, then SSHes into the Swarm manager for a
|
||||
zero-downtime rolling update behind Traefik. You read this line because
|
||||
the whole pipeline just ran end-to-end.
|
||||
</p>
|
||||
<div class="actions">
|
||||
<a class="btn btn-primary" href="#stack">See the stack</a>
|
||||
|
||||
Reference in New Issue
Block a user