Using Magic with SQLite

In this tutorial we will cover the following parts of Magic and Hyperlambda.

The default “docker-compose.yml” file for Magic will create a MySQL Docker container. If you instead want to use SQLite, you’ll need a slightly modified “docker-compose.yml” file. Below is a complete docker-compose file, except it doesn’t create a MySQL docker container at all. This is because SQLite allows you to simply use your file system as your “connection string” and connect directly to a file, making it significantly easier to use since there’s no network configuration, or explicit requirement to even have a database server installed at all.

version: "3.3"


    image: aistamagic/magic-backend:latest
      - db
    restart: always
      - "4444:4444"
      - etc_magic_folder_sqlite:/magic/files/etc
      - modules_magic_folder_sqlite:/magic/files/modules
      - config_magic_folder_sqlite:/magic/config

    image: aistamagic/magic-frontend:latest
      - backend
    restart: always
      - "5555:80"


If you create a file named “docker-compose.yml” and save it to any directory on your machine with the above content, for then to run the following command in that same directory, this will start Magic for you without any database servers at all, allowing you to use SQLite’s integrated file system adapter.

docker-compose up

Configuring Magic

When you configure Magic, you’ll need to choose the “sqlite” database type. Afterwards you’ll need to keep the existing connection string as is.

The rest of the process is similar to the MySQL equivalent, and implies crudifying your backend, creating a key pair, and running the assumptions. You also need to have Docker installed on your development machine.

Notice, since SQLite is based upon the file system, this implies that in order to create a new database, you’ll need to create an empty “xxx.db” file inside your “/data/” folder. To see your “/data/” folder make sure you enable for “System files” in Hyper IDE, select the data folder, and create for instance a new empty file called “sakila.db”. Then go to the SQL menu item, purge your server-side cache, for then to load up the “sakila” script that’s been ported to SQLite that you can find by clicking the “Load” button. Make sure you select your newly created “sakila” database before you execute the script.