Add Tech stack section to README.

fb5dd1872dcf · AtlantisPleb · · parent f10182149815

Add Tech stack section to README.

Lists the core technology choices: Elixir on the BEAM, Phoenix and
LiveView, PostgreSQL, Google Cloud, Tailwind CSS, and Basecoat.

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-Authored-By
Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Not deployed through the forge lane

No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.

Changed files

  • modified README.md

Diff

1 file changed, +9 -0

README.md modified +9

@@ -18,6 +18,15 @@ Starting fresh lets us build a forge that is open, contributor-friendly, and def

18 18
- **Release upgrades (relups):** deploys use Erlang/OTP release upgrade patterns for zero-downtime updates.
19 19
- **Live surfaces:** pages update for every connected viewer at the same time through Phoenix PubSub.
20 20
21
## Tech stack
22
23
- **Elixir on the BEAM** — the runtime for hot reload, release upgrades, and live, concurrent page updates.
24
- **Phoenix and Phoenix LiveView** — web framework and live UI layer.
25
- **PostgreSQL** — primary database.
26
- **Google Cloud** — hosting and infrastructure.
27
- **Tailwind CSS** — styling.
28
- **Basecoat** — UI component library.
29
21 30
## First deliverable: Issues and projects
22 31
23 32
The first public surface is an issue and project tracker. We will use it to run OpenAgents.com's own development. You can:

This page updates live while a promote is in flight · changelog