diff --git a/docs/deploy.md b/docs/deploy.md index 9d1c6f3..8d686d0 100644 --- a/docs/deploy.md +++ b/docs/deploy.md @@ -1,13 +1,11 @@ # Deployment Guide -> Ready for your project to see the light? You may be eligible for deployment on -> **rethink-net** — our fleet of Ubuntu 26.x servers, ready to host whatever -> you've built. +> How a project gets onto **rethink-net** — our Ubuntu 26.x servers. Get your +> container to follow a few consistent rules and deploying is mostly handing us a +> `compose.yaml`. -!!! tip "Eligible" - APIs, websites, applets, bots, monitors. The whole network runs on a few - simple, consistent rules — get your container to follow them and deploying is - mostly handing us a `compose.yaml`. +!!! tip "What can run here" + APIs, websites, applets, bots, monitors. ## Docker — the services account diff --git a/docs/index.md b/docs/index.md index e971e65..e30de5e 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,7 +1,7 @@ # rethink development -The public reference for building and shipping with Rethink Studios: our shared -libraries, our coding standards, and how to deploy a project on our network. +The reference for building and shipping on our network: the shared libraries, the +coding standards, and how to get a project deployed. This is a public site — it documents generic patterns and conventions. Real infrastructure specifics (hostnames, internal IPs, exact topology, secrets) stay @@ -29,7 +29,7 @@ out of it; examples use placeholders like ``, ``, and `/srv/...`. --- - How we actually work day to day — our Gitea, git habits, and the + Get hands on with how we dev — our Gitea, git habits, and the plan-in-chat / build-in-Claude-Code flow, plus shell setup. - :material-language-python: __[Virtual environments](environments.md)__ diff --git a/docs/workflow.md b/docs/workflow.md index f1076ae..c647626 100644 --- a/docs/workflow.md +++ b/docs/workflow.md @@ -1,10 +1,10 @@ # Workflow -How we actually work day to day at Rethink Studios — where code lives, how we use -git, the AI-assisted dev flow we recommend, and the shell setup that ties it -together. This is the **our-flavored** version: why *we* do it this way and how -*our* setup is wired. For the truly generic parts (installing WSL, learning git), -we link the official docs rather than reteach them. +Get hands on with how we dev — where code lives, how we use git, the AI-assisted +flow we recommend, and the shell setup that ties it together. This is the +**our-flavored** version: why *we* do it this way and how *our* setup is wired. For +the truly generic parts (installing WSL, learning git), we link the official docs +rather than reteach them. !!! info "Public, sanitized" Examples use placeholders — ``, ``, `dev@`, `/mnt/c//...`.