Projects

+ New page

development/ — how to develop for hutfx.com

What belongs here: everything a developer needs — workflow, technology, snippets, rules of the house. Start with the workflow doc, then the quick reference below.

Contents

Quick reference — rules of the house

• Repo: github.com/hutfx/lab-engine — main = production, active_work = integration.
• One task = one NEW branch from current active_work = one PR. Never add commits to a branch whose PR is already open. Descriptive branch names (feature/audio-sync), never tmp/fix2.
• PRs target active_work; reviewer: petya5q. Merge only by hutfx/petya5q — agents never merge. active_work → main sync is manual by sato/petya only.
• Your dev environment: http://<name>.hutfx.com, code at /home/<name>/dev/hutfx/, DB hutfx_<name>, Samba \\192.168.0.3\<name>, details in ~/ACCESS.md in your home. New env: dev-spawn <name> [branch] on hut.
• Docs: only in this wiki (~/workspace/HUTFX-project/DOCS/), never in the website repo.
• Never reset existing mailbox/service passwords without asking.

Technology stack

Snippets

# daily loop (in your clone)
git fetch origin
git checkout -b feature/<name> origin/active_work
# ...work, commit as sato20011 noreply...
git fetch origin && git rebase origin/active_work   # if active_work moved
git push -u origin feature/<name>                   # then open PR -> active_work

# refresh your env after a merge
/home/sato/bin/update.sh

# spawn a new test env (on hut, sato)
/home/sato/bin/dev-spawn <name> <branch>

# SSH to your env:  ssh -p 2022 <name>@192.168.0.3
# Samba from Windows: \\192.168.0.3\<name>   (user <name>, samba pass set by owner)