Skip to main content
Setup opens after you sign up with GitHub and install the Xerg App, before your first map. Owners and admins see it; everyone else’s mapping follows what it says.

​
Quick setup

The quick setup comes first and is already chosen. It maps every repo the app can see, except forks and archived repos, and it reads config files, env variable names, and source files’ imports and API hostnames. Choose Map N repos and the map fills in.

​
Advanced options

Open Advanced options to change what Xerg maps: Everything Xerg does here only reads.

​
Services the code no longer uses

With Find services the code no longer uses on, a service like this shows faded on the map and says Unused in its details, with where it was found: for example, a payments package in package.json and its key in .env.example, with no file importing it. Xerg only marks a service when it read every source file in the repos that list it. A repo with more source files than Xerg reads, or whose source wasn’t read, can’t prove a service is unused, so nothing there is marked. A service is also in use if it sends your app webhooks, runs beside it (Docker Compose), or is set up in Terraform or a database schema.

​
Running setup again

Next to choose repos in the workspace, choose settings (owners and admins), then Run setup again. Setup opens with your current choices; change them and choose Map N repos. Repos setup now leaves out come off the map, and the rest are mapped again. Every later Re-map all follows the same choices. Settings also has:
  • Connect another service…, for an account nothing in your code points to. See Connecting a service.
  • Clear map, which deletes the shared map for everyone after asking. Connections, setup, people and history are kept; map the repos again to start over.