There is no import script anymore in the latest version of meza. Instead users should do sudo meza deploy monolith --overwrite with the appropriate backup files in place. Unfortunately this is not documented well in meza yet. This gist is intended as temporary documentation. It would be great if someone created a pull request into meza with this (cleaned up and verified) as official documentation.

There's more than one way this could be done, but this is one way. From the ground up in VirtualBox, get your VM configured. Skip this if you already have a running meza installation.

sudo ifup enp0s3
curl -L getmeza.org > doit
sudo bash doit
sudo meza setup dev-networking

Then do an initial deploy. This will install all the stuff (MariaDB, PHP, Elasticsearch, etc) plus set you up with the Demo Wiki. Again, skip this if you have a running installation.

sudo meza deploy monolith

Now copy your wiki's files to the location in /opt/meza/data/backups. For example, if your wiki's ID was launch your going to have a directory like /opt/meza/data/backups/monolith/launch. If you want to make sure you get the structure inside launch correct, you could do sudo meza backup monolith then copy the structure of demo backup files.

Then, with your launch backup files in place, run:

sudo meza create wiki monolith

This will create a wiki in your "monolith" environment (your only environment). It will prompt for wiki ID (make sure this matches your wiki ID in /opt/meza/data/backups, e.g. launch) and wiki name. Wiki name can be anything you want. While meza create wiki is running it will find the backup files and initiate your wiki with them.