Many Projects on One Computer: Tabs, Settings and Your Editor in Sync

Intro

0:00 Several API Maker projects on one computer, each in its tab and on its own ports. Their settings, a project deleted with everything it made, and your editor kept in sync with API Maker, both ways.

Many projects, the usual way

0:13 Working on several backends usually means one running at a time, the others stopped to free their ports, settings spread over env files and scripts, containers and volumes of old projects left behind, and code edited in a browser tab, far from your editor. With Launchpad, projects run side by side, each on its own ports, every setting of a project on one page, a project deleted with everything it made, and a folder of your computer in sync with API Maker.

0:44 In this video : the projects of this computer, a tab for each, Project Settings, deleting a project, the Local Client, and how it syncs.

The projects of this computer

0:54 The Projects card of the welcome screen. Running : Calm Home for Business, in Full Docker, with the processor and memory of its containers. Recent : every project opened on this computer, each with its stack, the version of API Maker, its MongoDB and Redis and every database, with their logos. Calm Home API is pinned ; a folder of a USB drive that is gone says so. The search looks at names, folders, versions and databases : postgres seventeen finds the projects with a PostgreSQL seventeen.

1:30 The play button starts a project in the background : try-oracle, a project for trying Oracle, starts on ports of its own, and says when it runs. Running now lists both, each with Admin panel, Open and Stop. Open : the business project opens in its tab, its dashboard on screen. The other projects keep running.

A tab for each

1:52 Each project opens in a tab of its own, and each tab remembers its page. The plus opens a list of the running and recent projects, and Open a folder. Typing finds a project, and Enter opens it. A right click on a tab : close it, the project keeps running ; close the others ; stop the project ; show its folder. Tabs can be dragged to reorder them, and closed with a middle click.

2:18 The project picker of the sidebar lists the running and recent projects too. And the keyboard : command and a number go to a tab, command T opens the plus, command W closes a tab.

Project Settings

2:31 Project Settings, for the project on screen. The architecture : Native or Full Docker, switched while the project is stopped. The version of API Maker : the one installed, one native program, and every version of npm, to install another. The versions of what it runs with : its MongoDB, its Redis and every database, as video fifty six showed. Its name, and its license key : the key of local runs, or your own.

3:00 Its ports, and where the database ports can be reached from. Extra environment variables for API Maker : here the time zone of its schedulers ; they go into the env file the app writes. And the danger zone, to delete the project.

Deleting a project

3:15 The Oracle trial is over. The bin of a recent project deletes it for good : the confirmation lists what goes, its containers, volumes and networks, and the folder with its size. Files of the folder that Launchpad did not make are pointed out first. Its name, typed, and it is gone, from the disk and from the list.

The Local Client

3:36 The Local Client page keeps a folder of this computer in sync with API Maker, both ways : edit custom APIs, schemas, schedulers, hooks and every other item in your editor, and what you save in the admin panel lands on the disk. Its card : sent, received, deleted, the full syncs, the git branch with its changed and unpushed files. Open in : every editor found on this computer, the terminal and the file manager.

4:06 The console shows the local client as it works : each item with the icon of its category. Filters : what was received, what went wrong, here a utility class API Maker could not save, fixed a minute later, or everything. A sync that stops by itself turns the card red, with the reason. Set up another folder : where is the code kept? GitHub, GitLab or another git host, with a token API Maker keeps encrypted, or a git repository on this computer, recommended : versioned, and nothing leaves this computer.

4:40 The folder, then set up and start : the repository is made and attached to API Maker, every item is committed, checked out, a sync token is made, the files of the local client are written, and it starts. Ready to code.

How it syncs

4:55 How it works. The local client is the one that ships with API Maker, a small Node.js program : Launchpad downloads Node.js for it once, kept for every folder. It talks to API Maker over its WebSocket. A repository made on this computer is a bare git repository, served on one two seven point zero point zero point one, with a secret in its address : API Maker pushes and fetches there.

5:22 And when the app is gone, a watchdog stops the local client.

Recap

5:27 To sum up. Projects side by side, each in its tab, on its own ports. Every setting of a project on one page. A project deleted with everything it made. And your editor in sync with API Maker, both ways. Next : Launchpad, API Maker on your own servers. API Maker. Build faster, spend smarter, deliver better.