Back office of MONARC
 
 
Go to file
Ruslan Baidan dc96289c36 Updated the composer with the latest versions of core and backoffice to use Laminas. 2020-02-21 15:25:17 +01:00
INSTALL
config Migrated to Laminas. 2020-02-21 11:46:10 +01:00
db-bootstrap
deliveries/cases
public Migrated to Laminas. 2020-02-21 11:46:10 +01:00
scripts
vagrant
.gitignore
AUTHORS Updated README and AUTHORS file. 2020-02-21 11:51:09 +01:00
LICENSE
README.md Updated README and AUTHORS file. 2020-02-21 11:51:09 +01:00
VERSION.json Updated README and AUTHORS file. 2020-02-21 11:51:09 +01:00
composer.json Updated the composer with the latest versions of core and backoffice to use Laminas. 2020-02-21 15:25:17 +01:00
composer.lock Updated the composer with the latest versions of core and backoffice to use Laminas. 2020-02-21 15:25:17 +01:00
package.json Updated README and AUTHORS file. 2020-02-21 11:51:09 +01:00

README.md

MONARC - Back Office

The back office is especially needed if you want to manage several clients. For more information you can have a look at the differences with MONARC itself or you can check the MONARC architecture.

Documentation

You will find a user guide and a technical guide on the MONARC website.

For installation instructions see INSTALL.

License

This software is licensed under GNU Affero General Public License version 3

For more information, the list of authors and contributors is available.

Data provided with MONARC (threats, assets, vulnerabilities, referentials, etc.) are licensed under CC0 1.0 Universal (CC0 1.0) - Public Domain Dedication. These objects are available through the MONARC Objects Sharing Plarform. If a specific author wants to license an object under a different license, a pull request can be requested.