# Disclaimer

Glewlwyd can take a central place in a system where applications and environments need authentication and authorization, be aware of the risks: bugs, non discovered vulnerabilities, etc.

It's recommended not to use Glewlwyd in production, more likely to test OAuth2/OpenID behavior, MFA connections, or IdP in general. You can also explore its functionalities and help yourself with its source code for other implementations.

If you intend to use it in production, it's highly recommended to follow the documentation and enable only the features you will use.

# Upgrade database

If you upgrade the glewlwyd package from Debian Bullseye, you must run the following SQL scripts:

/usr/share/doc/glewlwyd/upgrade-2.6-core.{mariadb,postgre,sqlite3}.sql
/usr/share/doc/glewlwyd/upgrade-2.7-core.{mariadb,postgre,sqlite3}.sql

Run the script corresponding to your database.

# Serve static web files

In the current version, it's not recommended to use glewlwyd's static file server to serve the front-end application in /usr/share/glewlwyd/webapp. It's recommended to use a static file server instead, such as Apache or NGINX.

THe following example provides an Apache configuration to serve the static files, and proxify the API.

<VirtualHost *:80>
  ProxyPass /config http://localhost:4593/config
  ProxyPass /api http://localhost:4593/api

  DocumentRoot /usr/share/glewlwyd/webapp/
</VirtualHost>
