From 8b49810eeb0205bf5b9d40a9dc9d1725d0032cab Mon Sep 17 00:00:00 2001 From: neil Date: Sun, 1 Nov 2020 15:19:57 +0000 Subject: [PATCH] adding DB libs --- Setting-up-Nextcloud-and-sncf.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Setting-up-Nextcloud-and-sncf.md b/Setting-up-Nextcloud-and-sncf.md index aa0900d..c88f6eb 100644 --- a/Setting-up-Nextcloud-and-sncf.md +++ b/Setting-up-Nextcloud-and-sncf.md @@ -115,6 +115,10 @@ Now your Nextcloud instance should be ready. Let's move on to sncf. - You are advised to enable `debug_mode` at least during the first days in production. The debug mode won't slow down sncf, but will help you to understand when something's wrong by printing a *lot* of data to stdout. 9. Compile (`cargo run --release`) and run sncf. + - sncf requires the following packages to be installed (on a Debian-based system): + - `libsqlite3-0` if you're using SQLite + - `libpq5` if you're using PostgreSQL + - `libmysql++-dev` if you're using MySQL / MariaDB. - [reverse-proxy only] Route your public-facing address to sncf instead of Nextcloud. - [reverse-proxy only] [optional] You might want to set up direct access to Nextcloud without going through sncf, for technical purposes. You can do that on a secret port or route (not `/admin/`, though). Be sure to strenghten this access (at least with basic auth) to avoid transforming it into a backdoor for evil people.