You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
msquare abf4b1da30 check if logged in before sign up 7 years ago
config Change defaultvalue for initial vouchers 7 years ago
db Formatting & Docstrings 7 years ago
import camp 2011 export 14 years ago
includes check if logged in before sign up 7 years ago
locale rephrase more naturally 7 years ago
public font size for stats 7 years ago
src Formatting & Docstrings 7 years ago
templates introduce new shift signup state for not arrived angels 7 years ago
tests Updated translation / Formatting / Test 7 years ago
themes font size for stats 7 years ago
.gitignore Fixed exceptionHandler to catch PdoExceptions, formatting 7 years ago
.gitlab-ci.yml Formatting & Docstrings 7 years ago
LICENSE directory renames and cleanup 14 years ago
README.md Formatting & Docstrings 7 years ago
composer.json Refactored ExceptionHandler 7 years ago
deploy.sh Added dokumentation for tests, gitlab and deployments 7 years ago
phpunit.xml Merge branch 'noc0lour:fix_setup_bugs', closes #335 7 years ago

README.md

Codacy Badge GPL

Engelsystem

Please visit https://engelsystem.de for a feature list.

To report bugs use engelsystem/issues

Installation

Requirements:

  • PHP >= 7.0.0
  • MySQL-Server >= 5.5 or MariaDB-Server >= 5.5
  • Webserver, i.e. lighttpd, nginx, or Apache

Directions:

  • Clone the master branch: git clone https://github.com/engelsystem/engelsystem.git

  • Install Composer

  • Install project dependencies:

    composer install
    

    On production systems it is recommended to use

    composer install --no-dev
    composer dump-autoload --optimize
    

    to install the engelsystem

  • The webserver must have write access to the 'import' directory and read access for all other directories

  • The webserver must point to the public directory.

  • Recommended: Directory Listing should be disabled.

  • There must a be MySQL database created with a user who has full rights to that database.

  • It must be created by the db/install.sql and db/update.sql files.

  • If necessary, create a config/config.php to override values from config/config.default.php.

  • In the browser, login with credentials admin:asdfasdf and change the password.

Engelsystem can now be used.

Session Settings:

  • Make sure the config allows for sessions.
  • Both Apache and Nginx allow for different VirtualHost configurations.

Development

Since the engelsystem is open source, you can help to improve the system. We really love to get pull requests containing fixes or implementations of our Github issues.

Please create single pull requests for every feature instead of creating one big monster of pull request containing a complete rewrite.

Testing

To run the unit tests use

vendor/bin/phpunit --testsuite Unit

If a database is configured and the engelsystem is allowed to mess around with some files, you can run feature tests. The tests can potentially delete some database entries, so they should never be run on a production system!

vendor/bin/phpunit --testsuite Feature
# or for unit- and feature tests:
vendor/bin/phpunit

CI & Build Pipeline

The engelsystem can be tested and automatically deployed to a testing/staging/production environment. This functionality requires a GitLab server with a running docker minion.

To use the deployment features the following secret variables need to be defined (if undefined the step will be skipped):

SSH_PRIVATE_KEY         # The ssh private key
STAGING_REMOTE          # The staging server, e.g. user@remote.host
STAGING_REMOTE_PATH     # The psth on the remote server, e.g. /var/www/engelsystem
PRODUCTION_REMOTE       # Same as STAGING_REMOTE but for the production environment
PRODUCTION_REMOTE_PATH  # Same as STAGING_REMOTE_PATH but for the production environment

deploy.sh

The deploy.sh script can be used to deploy the engelsystem. It uses rsync to deploy the application to a server over ssh.

For usage see ./deploy.sh -h

Codestyle

Please ensure that your pull requests follow PSR-2 and PSR-4.