Skip to content

Engineer onboarding

Read the ADRs first: they are the why. Then:

Access you need

GitHub (keferboeck account repos), the DigitalOcean team, Docker Hub (keferboeckltd), Mailjet (Keferboeck account), ClickUp (Keferboeck Ltd workspace), and a droplet SSH key.

Repos and local paths

App Repo Local Serves
Website keferboeck/keferboeck-next-react ~/Development/RoR/keferboeck.com keferboeck.com
Portal keferboeck/keferboeck-portal ~/Development/RoR/georgkeferboeck/keferboeck-portal hub.keferboeck.com
Demo shops keferboeck/solidus-demos ~/Development/RoR/georgkeferboeck/solidus-demos <shop>.keferboeck.com
This KB keferboeck/keferboeck-docs ~/Development/keferboeck-docs docs.keferboeck.com

Local development

  • The website dev server and ngrok run as launchd agents with KeepAlive (com.georg.dev.keferboeck on port 3002); never start them manually, restart with launchctl kickstart -k gui/$UID/<label>.
  • The portal is standard Rails: bin/setup, bin/dev; Postgres credentials via ~/.pgpass. Run bundle exec rspec before any push — the suite is the release gate.
  • Secrets live in git-ignored .kamal/ files per repo; ask for the password manager share, never commit a value, never paste one into a chat.

Working rules

  • Tasks live in ClickUp with the mandatory structure (problem, Solution, Automated Tests, Steps to Reproduce, QA Steps) and wired dependencies.
  • UI copy: no dashes, British English, du-form German. Scroll animations replay on every section re-entry.
  • Docs, Mermaid diagrams and ADRs are part of the definition of done (PR template).
  • Deploys: see releases. Never deploy a red suite.