Skip to content
Clawdie Clawdie

Setup Instructions

Setup Instructions

Section titled “Setup Instructions”

This page covers the current localization setup path.

What you need

Section titled “What you need”
  • the Clawdie repo checked out on the host
  • a Crowdin API token
  • a working cms jail with the Astro docs project already provisioned

The docs runtime is not set up as a separate standalone Astro install anymore.

Step 1: Configure Crowdin access

Section titled “Step 1: Configure Crowdin access”

You can provide the token in any one of these ways.

Option A: token file

Section titled “Option A: token file”
Terminal window
mkdir -p ~/.config/clawdie
echo "tskey-your-token-here" > ~/.config/clawdie/crowdin-token
chmod 600 ~/.config/clawdie/crowdin-token

Option B: environment file

Section titled “Option B: environment file”
Terminal window
cd /home/<agent>/clawdie-ai
echo 'CROWDIN_PERSONAL_TOKEN=tskey-your-token-here' >> .env

Option C: shell environment

Section titled “Option C: shell environment”
Terminal window
export CROWDIN_PERSONAL_TOKEN=tskey-your-token-here

Step 2: Verify Crowdin connectivity

Section titled “Step 2: Verify Crowdin connectivity”

Run from the host repo root:

Terminal window
cd /home/<agent>/clawdie-ai
./scripts/crowdin-sync.sh --status

If this works, the localization sync scripts can see your token.

Step 3: Push source strings

Section titled “Step 3: Push source strings”

When English source docs change:

Terminal window
cd /home/<agent>/clawdie-ai
./scripts/crowdin-sync.sh --push

This publishes source markdown from docs/public/ to the Crowdin project.

Step 4: Pull translations back into the repo

Section titled “Step 4: Pull translations back into the repo”

After translators have updated a locale:

Terminal window
cd /home/<agent>/clawdie-ai
./scripts/crowdin-sync.sh --pull

This updates translated markdown under paths like:

  • docs/public/sl/
  • docs/public/de/
  • docs/public/hr/

Step 5: Deploy localized docs

Section titled “Step 5: Deploy localized docs”

Deploy still happens through the shared Astro project in the cms jail:

Terminal window
cd /usr/home/<tenant>/<tenant>-site
npm run deploy

That command:

  1. syncs host-side docs content into the Astro tree
  2. builds the static site
  3. deploys it into the cms jail webroot

Step 6: Verify

Section titled “Step 6: Verify”

Check the live site:

Terminal window
curl -sI https://docs.clawdie.si/
curl -sI https://docs.clawdie.si/en/

Then verify any locale-specific pages you expected to change.

Notes

Section titled “Notes”
  • Edit markdown on the host, not inside the jail.
  • Crowdin manages translations, not deployment.
  • Astro deployment is shared with the docs publishing flow, not a separate localization runtime.