Skip to content
Blysis
Documentation

First steps

The installer prints an address and a password. Open the address and the setup wizard takes it from there.

The setup wizard

It asks for four things and each has a sensible default:

  1. The site's name and description. Both are settings you can change later; they appear in the navigation, the page titles and the search results.
  2. The first administrator. The password the installer printed is a temporary one. Change it here, and use an address you can receive mail at: it is what a password reset goes to.
  3. The language. English and Turkish both ship. Whichever you pick, the other stays available to visitors, and every module's strings arrive in both.
  4. A starting set of modules. You can skip this and install nothing; the marketplace is one click away afterwards and nothing installed here is harder to remove than anything installed later.

Before anyone else arrives

Five settings are worth a minute each, and every one of them is easier to change now than after a hundred people have signed up.

The site URL. Settings, then Site Config. It is what an email link, a payment callback and a share card are built from. Getting it wrong produces links that work for you, on the machine, and for nobody else.

Email. Without a working sender, a password reset produces a queued message and a confused member. The email module takes SMTP details, and there is a test button beside them.

Registration. Whether anyone can sign up, whether an address has to be verified, and which role a new account lands in. The default is open with verification on.

Roles. The core ships a small ladder: member, staff, admin. A role has a priority, and what a role can do is a set of permissions rather than a position on the ladder. Give staff the permissions they need rather than the role above them.

Backups. Run blysis backup once by hand so you have seen it work, and read where it wrote the file. A backup you have never restored is a file, not a backup.

What the admin panel is arranged by

The panel is grouped by the job rather than by where the code lives: Content, Commerce, Community, People, Design, System, Settings. A module's screens appear in the group it declared, in your language, and disappear when it is disabled with its data left alone.