For DevOps engineers
A DevOps engineer's path through EasyCode: the desktop app on every machine, the network, repos, the runner and your CI.
What does EasyCode do for DevOps?
EasyCode runs on your team's own machines. The desktop app holds a local runner that drives each person's harness on
their own login, and talks to EasyCode over HTTPS. Code stays in your repos on GitHub. Branches and pull requests are
pushed with each person's own git and gh, so your branch rules, git hooks and CI apply as they do today.
Your job is to get the app onto machines, let it through the network, connect the repos, and keep the runner healthy.
Your path
Follow these pages in order. Each line says why it matters to you.
Roll out the app
- Quickstart for org admins: make the org, invite people and set who can do what.
- Desktop app: installers for macOS (Apple silicon and Intel), Windows and Linux (AppImage and deb), and how updates arrive.
- Harnesses on your own login: each person installs and signs in to their harness. EasyCode never reads those credentials.
- Network and firewall: the hosts the app, the runner and the harnesses must reach.
Connect the code
- Products and repos: install the GitHub App on the repos your products use.
- Org, members and teamspaces: who sees which products and sessions.
- Set up knowledge for a repo: scans run on a desktop app, so plan which machines hold which repos.
Keep it healthy
- The
easycodeCLI:easycode runnerruns only the local runner,easycode matrixsmoke-tests each harness driver, andeasycode cleanupremoves EasyCode's hidden refs and stale isolated worktrees. - Settings: runner settings such as
repos.cloneRoot,repos.searchRootsandisolation.depDirs. - Troubleshooting: what to check when the runner or a harness won't start.
See it end to end
- Set up your org: the admin's first run as a walkthrough of real screens.
- Onboard a team: bringing a whole team in, machine by machine.
Can I turn off automatic updates?
Yes, with a machine policy your device management drops in a system folder. The desktop app reads one key from it,
autoUpdate:
/Library/Application Support/EasyCode/policy.json{ "autoUpdate": false }If the file is there but isn't valid JSON, updates stay off, since someone meant to set a policy.
What happens when a push fails?
The app tells the person why, on the machine that ran it. A git hook that fails stops the push. A rejected login means
git or gh must be signed in again on that machine. Without gh signed in, Create PR opens GitHub's compare page
instead. While a workflow gate is open, nothing is pushed.
What is set for the whole org?
- Session policy, in org settings: whether Session content and Session titles sync to the cloud, and Keep content for (days).
- Modules: which parts of EasyCode your org has. EasyCode staff set them, and can pause a feature with a kill
switch such as
syncorbrowser. See Kill switches and modules. - Security and privacy: what leaves a machine and where data lives.
Something wrong or missing? Suggest a change