pepiscms | Content management system written on top

PepisCMS is meant to be used as a library. However, for the local development process, a Docker environment with a sample implementation project can be set using:. Once a Docker setup is started, all the generated files can be found in the tmp/ directory. If you wish to restart the environment simply use. The default admin credentials are demo@example.com / demodemo. See other useful development commands.
PepisCMS is installed as a composer dependency and then instantiated in the user directory.
attended (user)
unattended (manual)
Copy install.php file to root directory. Open install.php in your browser http://localhost/install.php. This will create a basic framework structure. Please follow the installation guide.
Install composer dependencies composer install --prefer-dist
Copy install.php file to root directory cp ./vendor/piotrpolak/pepiscms/install.php ./
Open install.php in your browser http://localhost/install.php This will create a basic framework structure. Please follow the installation guide. Directory view Copy files and create framework structure Database connection setup There are two options: native and Symfony import. When selecting native you will be asked for database host, name, user and password. If selecting Symfony import then PepisCMS tries to automatically parses Symfony parameters.yml configuration. Selecting authorization driver. You can choose from native (users are managed locally) or CAS When selecting CAS then user passwords will not be managed by PepisCMS. The local users having minimal access rights will be created upon the first user authentication (use of the system). Configuring administrator account Configuring site options Configuring installed modules You can choose which modules to be installed and add specified modules to menu and/or utilities. Success message Dashboard
PepisCMS can be installed and configured in an unattended way.
Module installation consists in enabling the module and configuring its parameters (if available). Modules that do have administration interface can be attached to an admin panel menu and/or utilities dashboard. Most modules come with predefined configuration and presentation defaults. Configuration options and presentation details are defined in a module descriptor (a class that implements ModuleDescriptableInterface). An SQL code can be executed upon module installation/uninstallation. A file containing SQL code can be optionally specified in module descriptor. To view installed modules please navigate to Start > Utilities > Installed modules.