Current status
You can already self-host __frgmnt and play around with it, but I would still consider the whole thing experimental.
This is not a final installation guide. Parts of it may change, get restructured or break as the CMS keeps evolving. If you just want to explore it locally, that should already be possible.
What you need
The easiest way to get started is through the frgmnt-template repository.
The template already includes a DDEV configuration, an example .env, and a small example extension that handles a basic frontend output and also shows how custom extensions can be built.
Right now the setup assumes:
- PHP 8.4
- Apache
- MariaDB 11.4
- Composer 2
- Git LFS
Setup
Clone the template project first and start it through DDEV.
Then run composer install so the base configuration and dependencies are installed.
Note: When using DDEV, you need to run ddev composer install to run composer inside DDEV.
A minimal .env is included as an example. Database access is configured against the default DDEV database container.
You will also need to provide a TOTP_ENC_KEY.
The easiest way to generate one is:
php -r "echo base64_encode(random_bytes(32));"
After that, create a storage directory inside public.
For local development that is enough.
For a live environment, it is recommended to keep storage outside of the project directory and link it back in via symlink.
First login
Once the project is running, open the backend under the /frgmnt path of your local DDEV URL.
A default user is included:
- user: admin
- password: frgmnt-admin
After the first login, a 2FA secret will be shown. Add it to the authenticator app of your choice.
The default admin credentials are only for the initial setup and should be changed immediately!
The easiest way is to generate a new password hash in the terminal:
php -r 'echo password_hash("NEW PASSWORD", PASSWORD_ARGON2ID) . PHP_EOL;'
Then update the user either through phpMyAdmin or directly through the database CLI.
After that, you should be ready to start exploring.