boulder

History

Jacob Hoffman-Andrews dd05ace030 Set up databases with restrictive user permissions. Fixes https://github.com/letsencrypt/boulder/issues/898 Also removes currently-unused 'development' DB, and do initial migrations in parallel, which shortens create_db.sh from 20 seconds to 10 seconds. Changes ResetTestDatabase into two functions, one each for SA and Policy DBs, which take care of setting up the DB connection using a special higher-privileged user called test_setup.	2015-10-16 15:50:57 -07:00
..
README.md	add goose as the migration tool	2015-08-25 12:02:31 -07:00
db_users-ca.sql	Add missing user / permissions	2015-08-26 20:14:29 -07:00

Jacob Hoffman-Andrews dd05ace030 Set up databases with restrictive user permissions.

Fixes https://github.com/letsencrypt/boulder/issues/898

Also removes currently-unused 'development' DB, and do initial migrations in
parallel, which shortens create_db.sh from 20 seconds to 10 seconds.

Changes ResetTestDatabase into two functions, one each for SA and Policy DBs,
which take care of setting up the DB connection using a special higher-privileged
user called test_setup.

2015-10-16 15:50:57 -07:00

README.md

add goose as the migration tool

2015-08-25 12:02:31 -07:00

db_users-ca.sql

Add missing user / permissions

2015-08-26 20:14:29 -07:00

README.md

The sql files here define the database user relationships between the various databases and services. Implementors should use these as starting points for their own configuration. The actual schemas are managed by goose and can be found in ./ca/_db and ./sa/_db.

The currently supported database is MariaDB 10.

The databases that boulder requires to operate in development and testing can be created using test/create_db.sh. It uses the root MariaDB user, so if you have disabled that account you may have to adjust the file or recreate the commands.