A workspace each
Developers sign in with their own account and API path, and change APIs, schemas and settings without touching the work of others.
Team & delivery
Developer Accounts
A whole team works on one development server, each developer in a workspace of their own.
The admin creates an account for each developer. Every account has its own login, API path, secrets and Git branch, and database name masking gives it its own copy of each database under the same name. Nobody overwrites anybody, and nothing has to be renamed before a pull request.
See it live
Step through it, slow it down, or open the full canvas.
api-maker/features/developer-accountsLive- Developers
- 2accounts
- Databases
- 3one each
- Renames
- 0before a PR
- Secrets
- 0in Git
A workspace for every developer. The admin creates as many developer accounts as needed. Each one has its own login and API path, so people never overwrite each other.
How it works
A workspace for every developer.
The admin creates as many developer accounts as needed. Each one has its own login and API path, so people never overwrite each other.
Same names, their own database.
Everyone writes database main. Database name masking runs priya's calls on main_priya and omar's on main_omar, so nothing is renamed before a pull request.
Secrets stay with each developer.
Each account has its own secrets, with its own connection strings and keys. They are never pushed to Git.
Pull, push, diff and revert in API Maker.
Each developer works on a branch without leaving API Maker. What reaches Git says main, like every other branch.
Nothing runs twice behind your back.
Schedulers of developer accounts never run in the background, only the admin's do. Developers run them from the API testing page when they want.
What you get
Database name masking
Everyone writes the database main in code and requests. For priya it runs on main_priya, for omar on main_omar.
Own secrets
Each account has its own secrets, with its own connection strings and keys. They never go to Git.
Git from the panel
Each developer pulls, commits, pushes and reverts on a branch. What reaches Git uses the real database names.
Safe by default
Schedulers of developer accounts never run in the background. Developers run them by hand when they need to.
One server for the team
Development happens on a shared server, so there is nothing to install on each machine. API Maker Local Run is there for those who want it locally.
An example
Three developers, one sprint
Priya adds an orders API, Omar changes the product schema and Lin writes a migration, at the same time on the same server. Each works on their own branch and their own copy of the database, then opens a pull request as usual.
Good to know
- Masked databases are separate databases: create and fill the copy of each developer, for example with migration scripts.
Questions
Who can create developer accounts?
The admin user, from Dev Accounts in the Utility menu. The API path and the email of each account must be unique.
Do developers need a server each?
No. Developer accounts share one server. Each one works in its own space on it.
Learn more
Documentation