The development environment is described in Programming Environment, however the CdEDB also has several specialised utility scripts, which can be found in the bin subdirectory.

  • Check performance by utilizing the test suite.

  • The entrypoint to our testing facilities, take a look at Running tests for more details.

  • Generate word lists from large text corpora (used for password strength estimation).

  • Generate a json file from the current database state. Take a look into the Test Suite for more details.

  • Generate a SQL file from an input JSON file. Take a look into the Test Suite for more details.

  • Do a brute-force attempt to find an XSS vulnerability. It is recommended to execute this using, see XSS tests.

  • Check a set of database evolutions for fitness.

  • Prepare i18n-data for spell-checking.

  • Launch a one-time use container for testing a set of database evolutions (like, but more thorough).

  • Launch a one-time use container running the test suite.

There is also a development server running at port 5000 which bypasses Apache and provides an interactive traceback explorer including a console in which expressions can be evaluated in the respective namespace. Take care to start the interactive debugger as user www-data.

To access the ldap server from a local vm, it is currently necessary to manually switch from TLS to plain TCP connections by removing the ssl parameter during server creation in ldap/ Tools like ldapsearch (from ldap-utils package) or ApacheDirectoryStudio seems to do not work properly if the certificate name differs from the hostname which is used to access the ldap server. If those tools are used within the vm, everything works fine.

It is also reasonable to increase the debug level in ldap/ from WARNING to DEBUG.