Skip to main content

Altus Tech Services repository instructions

Altus Tech Services repository instructions

Local development

Arthur runs this repository through shell helpers defined outside the repository. The two modes are alternatives and intentionally use the same port; they are never run simultaneously.

jekyll-serve ats uses:

  • repository: ~/workspace/zey-enterprises/web-altustechservices
  • JEKYLL_ENV=production
  • config: _config.yml
  • host: 0.0.0.0
  • port: 4004

jekyll-serve ats-dev uses:

  • repository: ~/workspace/zey-enterprises/web-altustechservices
  • JEKYLL_ENV=production
  • config: _config.yml,_config_dev.yml
  • host: 0.0.0.0
  • port: 4004

The helper runs Jekyll's normal watch/regeneration behavior and uses watchexec to restart Jekyll when the relevant config changes. Ordinary source edits and changes to _config.yml or _config_dev.yml are therefore handled automatically.

During normal interactive development:

  • Do not run bundle exec jekyll build.
  • Do not start another Jekyll server.
  • Do not run repeated production builds after edits.
  • Assume Arthur has the appropriate ATS server running at http://127.0.0.1:4004.
  • After edits, wait briefly for automatic regeneration or restart, then inspect the already-running site at port 4004.
  • If the server is not reachable, report that instead of silently starting another server.

Deployment safety

  • Do not commit or push unless Arthur explicitly requests it.
  • The tracked pre-push hook is scripts/git-hooks/pre-push; the active local copy belongs at .git/hooks/pre-push with executable permissions.
  • Never test the dev or staging hook path by pushing to a real remote unless Arthur explicitly requests that push.