Skip to Content

← All guides

Developer: git access & source control (core team)

Core Developer / Architect / Admin: clone VPS git remotes (businessite, businessite_core, sanitized grok-sessions), open /businessite/core/scm. Chat discovers remotes; laptop git + Grok Build edits code. scm help · my scm · open scm · guide developer-git.

Download PDF How-to videos

Chat commands

guide developer-git · scm help · git help · my scm · git remotes · open scm · grok sessions · /businessite/core/scm

Who can access source control?

After Appoint on a core-team post, these roles get SCM access on any layer (Data · System · User · Security · App):

  • Developer
  • Architect
  • Admin

Analyst and non-members are denied at /businessite/core/scm (see UAT “Core developer source control”). Managers / BusinesSite Managers can always open the portal.

What chat can vs cannot do

In BusinesSite chatOn your laptop
Discover remotes · show clone commands · open SCM portal · link to Grok sessions · this guide SSH clone · branch · commit · push · run Grok Build / IDE against the working tree

MVP rule: chat is discover + open only. It does not execute git, edit files, commit, or push.

Chat commands

guide developer-git
scm help · git help
my scm · git remotes · clone businessite
open scm
grok sessions

Also: /businessite/chat (web) or BusinesSite RC2 mobile.

VPS remotes (SSH)

Host: 156.155.253.114 (SSH config alias businessite-vps). Ask Ops for your key on the allow-list before first clone.

# BusinesSite Odoo module (main product code)
git clone ssh://root@156.155.253.114/opt/git/businessite.git
cd businessite
git checkout localhost-dev
git pull

# Core team + SCM portal module
git clone ssh://root@156.155.253.114/opt/git/businessite_core.git
cd businessite_core
git checkout localhost-dev

# Flutter hubs (separate remotes — also listed on /businessite/core/scm)
mkdir -p ~/APP/DEV/mobile && cd ~/APP/DEV/mobile
git clone ssh://root@156.155.253.114/opt/git/businessite_rc2.git
git clone ssh://root@156.155.253.114/opt/git/businessite_ta13.git
git clone ssh://root@156.155.253.114/opt/git/businessite_app.git      # TA5
git clone ssh://root@156.155.253.114/opt/git/businessite_rc1.git
git clone ssh://root@156.155.253.114/opt/git/businessite_ta8.git
git clone ssh://root@156.155.253.114/opt/git/schoollms_mobile.git
# then: cd <app> && git checkout localhost-dev

# Sanitized Grok Build transcripts (no auth.json / terminals)
git clone ssh://root@156.155.253.114/opt/git/grok-sessions.git ~/scm/grok-sessions

Signing keys (android/key.properties, *.jks) are not in these remotes — obtain release credentials from Ops separately.

Live cards + copy-paste commands also appear on /businessite/core/scm after you are appointed.

Branches (do not force-push shared lines)

  • localhost-dev — current laptop / personal work line
  • cloud-dev · cloud-qa · master — shared; promote via review / UAT gates

Full workflow notes: module doc docs/GIT_WORKFLOW.md.

Day-to-day after clone

  1. Mount or symlink the clone into your personal Odoo addons (see your SLUG setup guide).
  2. Develop + run QA agents / UAT on Dev (qa status in chat).
  3. Push a feature branch; open review; promote Dev→QA only after gate + notify.
  4. Use Grok Build locally against the clone; share sanitized sessions via the grok-sessions repo / portal.

Verify you have access

  1. Confirm appointment: layer + role = Developer (or Architect/Admin) on /businessite/core/setup.
  2. Re-login so the SCM security group syncs.
  3. Chat: scm help then my scm — you should see clone blocks, not a lock message.
  4. Browser: /businessite/core/scm lists remotes (not the denied page).
  5. Laptop: git ls-remote ssh://root@156.155.253.114/opt/git/businessite.git

Related

Leave any multi-step flow: say stop or cancel. Say continue to stay.