Playlist · 3 videos · 20 min
Upgrade from API Maker 3
For teams that run API Maker 3 today: what version 4 changes and what was removed, your Git branch pulled and committed again, your database opened by version 4 with the same data and the same tokens, and the two ways to move a server in place: with Launchpad, or with the installer.
The videos of this playlist
5:311. Upgrade from v3Upgrade from API Maker 3 to 4: What Changes in Your Code, Branch and Database
What moving from API Maker 3 to 4 means for a team: what version 4 is, what was removed and what takes its place, a Git branch written by API Maker 3 pulled as it is and written the version 4 way by its first commit, and a database of version 3 opened by version 4. The same data, and the same tokens.
6:282. Upgrade from v3Move an API Maker 3 Server to v4 in Place, with API Maker Launchpad
A server of API Maker 3 moved to version 4 where it is, with API Maker Launchpad: a check that changes nothing, servers it can not move refused with the reason, a review of every change to the env file and the Caddyfile, the migration run on the server itself, and everything put back, data included, when anything fails.
8:063. InstallInstall API Maker v4 on Ubuntu with One Command
One command on a fresh Ubuntu server installs API Maker version four, its MongoDB and Redis, systemd to keep it running, and Caddy in front. A new server of Calm Home goes from nothing to its admin panel in under two minutes, then upgrades with the same command, keeps every version, and grows to more servers.