rethink-public/handbook
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

tone down advertisey copy

Browse Source 
- index.md: 'building and shipping with Rethink Studios' -> 'building and
  shipping on our network' (it's the network, not the company)
- workflow.md + its index card: 'how we actually work day to day' ->
  'get hands on with how we dev'
- deploy.md: drop the 'see the light / ready to host whatever you've built'
  pitch for a plain 'how a project gets onto rethink-net'; trim the now-
  duplicate eligibility tip

Signed-off-by: disqualifier <dev@disqualifier.me>
This commit is contained in:
disqualifier 2026-06-29 21:23:34 -04:00
parent 78e3c34d8d
commit ed4e558dca
3 changed files with 13 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/deploy.md
View File

@ -1,13 +1,11 @@
# Deployment Guide # Deployment Guide
> Ready for your project to see the light? You may be eligible for deployment on > How a project gets onto **rethink-net** — our Ubuntu 26.x servers. Get your
> **rethink-net** — our fleet of Ubuntu 26.x servers, ready to host whatever > container to follow a few consistent rules and deploying is mostly handing us a
> you've built. > `compose.yaml`.
!!! tip "Eligible" !!! tip "What can run here"
APIs, websites, applets, bots, monitors. The whole network runs on a few APIs, websites, applets, bots, monitors.
simple, consistent rules — get your container to follow them and deploying is
mostly handing us a `compose.yaml`.
## Docker — the services account ## Docker — the services account

6
docs/index.md
View File

@ -1,7 +1,7 @@
# rethink development # rethink development
The public reference for building and shipping with Rethink Studios: our shared The reference for building and shipping on our network: the shared libraries, the
libraries, our coding standards, and how to deploy a project on our network. coding standards, and how to get a project deployed.
This is a public site — it documents generic patterns and conventions. Real This is a public site — it documents generic patterns and conventions. Real
infrastructure specifics (hostnames, internal IPs, exact topology, secrets) stay infrastructure specifics (hostnames, internal IPs, exact topology, secrets) stay
@ -29,7 +29,7 @@ out of it; examples use placeholders like `<dev>`, `<project>`, 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. plan-in-chat / build-in-Claude-Code flow, plus shell setup.
- :material-language-python: __[Virtual environments](environments.md)__ - :material-language-python: __[Virtual environments](environments.md)__

10
docs/workflow.md
View File

@ -1,10 +1,10 @@
# Workflow # Workflow
How we actually work day to day at Rethink Studios — where code lives, how we use Get hands on with how we dev — where code lives, how we use git, the AI-assisted
git, the AI-assisted dev flow we recommend, and the shell setup that ties it flow we recommend, and the shell setup that ties it together. This is the
together. This is the **our-flavored** version: why *we* do it this way and how **our-flavored** version: why *we* do it this way and how *our* setup is wired. For
*our* setup is wired. For the truly generic parts (installing WSL, learning git), the truly generic parts (installing WSL, learning git), we link the official docs
we link the official docs rather than reteach them. rather than reteach them.
!!! info "Public, sanitized" !!! info "Public, sanitized"
Examples use placeholders — `<you>`, `<key>`, `dev@<you>`, `/mnt/c/<your>/...`. Examples use placeholders — `<you>`, `<key>`, `dev@<you>`, `/mnt/c/<your>/...`.