Table of Contents
- Introduction
- Important Instructions
- Requirements
- Database
- Tables
- change_log
- data_absence
- data_booking
- data_custom_shift
- data_employee
- data_employee_access
- data_employment_period
- data_fixed_shift
- data_group
- data_group_access
- data_holiday
- data_individual_working_time
- data_leave_ban
- data_leave_entitlement
- data_leave_type
- data_membership
- data_modified_shift
- data_note
- data_overtime
- data_shift_cycle
- data_shift_cycle_assignment
- data_shift_cycle_element
- data_shift_cycle_exception
- data_shift_requirement
- data_shift_type
- data_shift_type_restriction
- data_special_period
- data_special_shift_requirement
- data_special_weekday_requirement
- data_surcharge_type
- data_user_setting
- data_user_specification
- data_working_time_model
- data_workplace
- Tables
Overview of Self-hosting Requirements
To be able to manage the database for a schedule using the Schichtplaner application, the following conditions must be met:
- You need a database server with the MySQL or MariaDB database management system installed.
- The database server must be able to establish an encrypted connection (SSL/TLS) with the application server.
- A database user must be registered who has sufficient rights to edit a Schichtplaner database and whose login information (username and password) is stored on the Schichtplaner application server.