- 23 Apr, 2018 6 commits
-
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Usage: script/lstu url --info <short> Print infos about the URL script/lstu url --remove <short> [--yes] Remove URL (ask for confirmation unless --yes is given) Will print infos about URL before confirmation script/lstu url --url <url> Search URL by its true URL (like match)
Luc Didry authored
-
- 22 Apr, 2018 17 commits
-
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
- Use woff2 format for Henny Penny font - CSS concatenation
Luc Didry authored -
© Luc Didry authored -
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
+ a few fixes
Luc Didry authored
-
- 21 Apr, 2018 13 commits
-
-
+ Better CI cache (using artifacts and dependencies) + Use services in CI instead of installed DB + Add `retry: 2` to jobs + Add code coverage
Luc Didry authored -
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
This commit is dedicated to Obrow, who is supporting me with Ğ1. Many thanks :-)
Luc Didry authored -
Luc Didry authored
-
Luc Didry authored
-
Luc Didry authored
-
- Authorize anonymous bind - Small code change This commit is dedicated to Squeeek, who is supporting me with Ğ1. Many thanks :-)
Luc Didry authored -
LDAP servers often have their users grouped into nested hierarchies, usually consisting of Organizational Units (OU). This commit extends the LDAP support so that it can locate the correct user in a server with a nested hierarchy. Different LDAP server schemas often use a different attribute for the username. For example, Microsoft Active Directory commonly uses the "sAMAccountName" as a username, while many other LDAP servers commonly use the "uid" attribute as a username. This commit extends the LDAP support so that the user can choose which attribute to use in the configuration file, using the "user_attr" configuration setting. With both of these changes in place, it now makes sense to merge the configuration settings "bind_user" and "bind_dn" together into the single configuration setting "bind_dn". The configuration settings now match my expectations as an experienced LDAP administrator. The configuration template has been updated to match these changes. In addition, the LDAP section in the configuration template has improved comments to explain the meaning of each setting.
Ira Snyder authored -
For both the MySQL and PostgreSQL database backends, allow the user to configure the maximum number of concurrent database connections. This is useful in environments where a very limited number of database connections are available. This is also useful in environments with strict policies against persistent database connections. In this case, max_connections can be set to 0, which disables persistent database connections completely.
Ira Snyder authored -
A simple copy and paste error prevents the MySQL port in the configuration from being used as part of the database connection.
Ira Snyder authored
-
- 22 Mar, 2018 4 commits