mirror/lldap
1
0
Fork 0
mirror of https://github.com/nitnelave/lldap.git synced 2023-04-12 14:25:13 +00:00
Code Issues Projects Releases Wiki Activity

feedback round 1

Browse Source
This commit is contained in:
Austin 2023-03-17 16:28:03 +00:00 committed by nitnelave
parent b538cdd4bc
commit be7ba2f2b0
2 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/migration.md → docs/database_migration.md
View File

@ -1,27 +1,27 @@
# Migration
Existing servers can migrate from one database backend to another. This page includes guidance for migrating from sqlite - similar concepts apply when migrating from databases of other types.
Existing servers can migrate from one database backend to another. This page includes guidance for migrating from SQLite - similar concepts apply when migrating from databases of other types.
NOTE: [pgloader](https://github.com/dimitri/pgloader) is a tool that can easily migrate to postgres from other databases. Consider it if your target database is postgres
NOTE: [pgloader](https://github.com/dimitri/pgloader) is a tool that can easily migrate to PostgreSQL from other databases. Consider it if your target database is PostgreSQL
The process is as follows:
1. Create a dump of existing data.
2. Change all `CREATE TABLE ...` lines to `DELETE FROM tablename;`. We will later have lldap create the schema for us, so we want to clear out existing data to replace it with the original data.
2. Change all `CREATE TABLE ...` lines to `DELETE FROM tablename;`. We will later have LLDAP create the schema for us, so we want to clear out existing data to replace it with the original data.
3. Do any syntax fixes for the target db syntax
4. Change your lldap config database_url to point to the new target and restart.
5. After lldap has started, stop it.
4. Change your LLDAP config database_url to point to the new target and restart.
5. After LLDAP has started, stop it.
6. Execute the manicured dump file against the new database.
The steps below assume you already have Postgres or MySQL set up with an empty database for lldap to use.
The steps below assume you already have PostgreSQL or MySQL set up with an empty database for LLDAP to use.
## Create a dump
First, we must dump the existing data to a file. The dump must be tweaked slightly according to your target db. See below for commands
### Postgres
### PostgreSQL
Postgres uses a different hex string format and doesn't support `PRAGMA`.
PostgreSQL uses a different hex string format and doesn't support `PRAGMA`.
```
sqlite3 /path/to/lldap/config/users.db .dump | \
@ -42,9 +42,9 @@ sqlite3 /path/to/lldap/config/users.db .dump | \
## Generate New Schema
Modify your `database_url` in `lldap_config.toml` (or `LLDAP_DATABASE_URL` in the env) to point to your new database. Restart lldap and check the logs to ensure there were no errors connecting and creating the tables. After that, stop lldap. Now we can import our original data!
Modify your `database_url` in `lldap_config.toml` (or `LLDAP_DATABASE_URL` in the env) to point to your new database. Restart LLDAP and check the logs to ensure there were no errors connecting and creating the tables. After that, stop LLDAP. Now we can import our original data!
### Postgres
### PostgreSQL
`psql -d <database> -U <username> -W < /path/to/dump.sql`
@ -54,4 +54,4 @@ Modify your `database_url` in `lldap_config.toml` (or `LLDAP_DATABASE_URL` in th
## Finish
If all succeeds, you're all set to start lldap with your new database!
If all succeeds, you're all set to start LLDAP with your new database!

2
lldap_config.docker_template.toml
View File

@ -75,7 +75,7 @@
#ldap_user_pass = "REPLACE_WITH_PASSWORD"
## Database URL.
## This encodes the type of database (SQlite, MySQL, and PostgreSQL)
## This encodes the type of database (SQlite, MySQL, or PostgreSQL)
## , the path, the user, password, and sometimes the mode (when
## relevant).
## Note: SQlite should come with "?mode=rwc" to create the DB