-
Notifications
You must be signed in to change notification settings - Fork 12
Konfiguration
-
copy the
.env.distfile and rename it to.envcp .env.dist .env -
open
.envwith a text editor and adjust it-
set the application language via
LOCALEAvailable
de(German) anden(English) -
set
APP_ENV(prod|dev)Use dev during development, otherwise use prod
-
generate and set a random value for
APP_SECRETe.g. via
openssl rand 23 | sha1sum -
under
DATABASE_URLset the database parameters. -
adjust
DB_SERVER_VERSIONaccording to the comments in the file
-
To be able to send emails from the application (conversations), an external mail provider must exist. The credentials are entered in the MAILER_URL parameter in the .env file.
e.g.:
MAILER_DSN= smtp://username:password@yourdomain.tld:port/?encryption=tls
adjust the remaining mail parameters according to the examples in the file
The salutation field for guests can be configured via the following parameter:
CUSTOMER_SALUTATIONS="Ms,Mr,Family"
You can specify any number of salutations separated by a , (comma).
Since version 4.0.0, passwordless login is possible in FewohBee. Three parameters are available for this:
RELYING_PARTY_ID=example.com
RELYING_PARTY_NAME="FewohBee"
PASSKEY_ENABLED=false
Passkeys are disabled by default (PASSKEY_ENABLED). To use the feature, RELYING_PARTY_ID must be set to the domain name under which the application is accessed.
A valid SSL certificate must exist for this domain, otherwise the login may not work correctly.
PASSKEY_ENABLED must also be set to true.
When passkey login is enabled, an additional button appears on the login screen to allow login. Users must log in once in advance with username and password. Under "Profile" each user can register for passwordless login. It is possible to store multiple devices that can be used for passwordless login (e.g. Chrome, iCloud Keychain, etc.). The user is guided through the process by the respective operating system / browser.
By default, the application checks when creating a new user and when changing a password whether it is secure. A password is considered insecure if it has appeared in the Have I Been Pwned database. This check can be configured via the following parameter.
USE_PASSWORD_BLACKLIST=true