Upgrade from API Maker 3 to 4: What Changes in Your Code, Branch and Database

Intro

0:00 From API Maker 3 to 4 : what changes on your servers, what was removed and what takes its place, and what happens to your Git branch and your database. The same data, and the same tokens.

A new major version, the usual way

0:13 A new major version of a backend usually means code rewritten for a new framework, data to migrate, new tokens for every app, and a weekend with no way back. Here, the same APIs on the same data, the same tokens, your branch pulled as it is, and a short list of what to check. In this video : what version four is, what was removed, your branch, pulled, its packages, the first commit, your database, what to check, and your servers.

What version four is

0:41 Version four is the same framework, rebuilt in Rust : one program, one process per server, with a thread for every core. Code in eight languages, each with its own packages and runtime. The APIs and the WebSockets on one port : behind Caddy, nothing changes for your apps. And the admin panel is served by API Maker itself : api_maker_fe is gone.

What was removed

1:07 Some parts of version three are gone. UI Maker : build your screens as SSR websites, or in your own frontend. The store and its third party APIs : their utility classes and packages stay, the pull keeps them. The header x-am-secret, gone since three point three : code reads its secrets with getSecret. The Register page : root makes the accounts. Notes, too. And nothing is installed in a sandbox unless the account lists it, in the packages of its language.

Your branch, pulled

1:41 Acme ran API Maker 3. Lena, their developer, first tries their branch on an account of version four of its own. Git Integration : the repository of Acme, and main, its working branch. Pull : the account takes what the branch holds. Yes, and the steps on the server, live. A warning : this branch was written by API Maker 3. The panel lists what was not pulled : the third party API, and a form of UI Maker.

2:12 lodash and moment, which every sandbox of version three had, are now packages of the account, at the same versions, and so is the client of S3 the third party API brought. Its three custom APIs are there.

Its packages

2:27 Sandbox Settings, JavaScript : the three packages, each at the version API Maker 3 had. From now on, a package the code takes is listed here, or it is not installed.

The first commit

2:40 The first commit writes the branch the way version four does. Check status. The custom APIs move to their folders of today, and the panel marks them Modified : the same items, under their new names. Collapsed, the changes by part. Deleted : the parts version four does not have. Added : the files every project of version four has. All of them. A message : the branch, written by API Maker 4.

3:09 Commit to main, and confirm : nothing is left to commit. In the repository : two commits, the one API Maker 3 wrote, and the first of API Maker 4. Before it, the parts by their names : Custom APIs, with a space. After it : custom_apis, utility_classes, and nothing of UI Maker or of the store. And git follows the code of Order Age across the move : both commits are in its history.

Your database

3:39 A server of version four started on the database of version three does the same, once, for every account : it lists the packages the code takes, and gives each WebSocket event back the code that says who may connect. A database version three never ran on is left as it is. With the secrets of the env file kept, as the installer and Launchpad keep them, the data is the same, and so are the tokens of your apps.

What to check

4:06 Before the move : try your branch on an account of version four of its own, as Lena did. Run your test cases, videos thirty seven and sixty three, and the security report, video twenty seven. Sandboxes run Debian now, not Alpine : a program of the system your code calls goes in the Dockerfile of its language. And keep a copy of the database until you are sure.

Your servers

4:30 Then the servers. On the server itself, the installer of video sixty one moves it in place. Or from your computer, the V3 to V4 Migration of Launchpad, in the next video : checked first, and everything put back if anything fails.

Recap

4:47 To sum up. One program in Rust, eight languages, one port, and the panel served by API Maker. UI Maker and the store are gone ; their packages and utility classes stay. A branch of version three is pulled as it is, and the first commit writes it the version four way. The same data, and the same tokens. Next : a server moved in place, with Launchpad. API Maker.

5:14 Build faster, spend smarter, deliver better.