diff --git a/docs/getting_started/docker.html b/docs/getting_started/docker.html index b39ea763..6be80d09 100644 --- a/docs/getting_started/docker.html +++ b/docs/getting_started/docker.html @@ -152,7 +152,7 @@
6. Restrict DB files access even more
After rauthy has done the first start, you could harden the access rights of the SQLite files even more.
diff --git a/docs/getting_started/k8s.html b/docs/getting_started/k8s.html
index 40ef4689..e3566575 100644
--- a/docs/getting_started/k8s.html
+++ b/docs/getting_started/k8s.html
@@ -308,7 +308,7 @@
DB_MIGRATE_FROM
(explained later) can be used with any combination of image / databaseAt the time of writing, you can run Rauthy either with Docker or inside Kubernetes.
+All the examples in this documentation are using the *-lite
images and therefore SQLite. If you want to use Postgres
+in production, you need to use the "default" container images.
DB_MIGRATE_FROM
(explained later) can be used with any combination of image / databaseAt the time of writing, you can run Rauthy either with Docker or inside Kubernetes.
+All the examples in this documentation are using the *-lite
images and therefore SQLite. If you want to use Postgres
+in production, you need to use the "default" container images.
For getting a first look at rauthy, you can start it with docker (or any other container runtime) on your localhost. @@ -259,7 +269,7 @@
6. Restrict DB files access even more
After rauthy has done the first start, you could harden the access rights of the SQLite files even more.
@@ -525,7 +535,7 @@