Replies: 1 comment
|
If you want control over what changes on the host, I would not pipe the installer directly to EDDI_DIR=$PWD/eddi-test bash install.sh --db=postgres --with-auth --with-monitoringThe README also documents the manual Compose route. PostgreSQL, Keycloak auth, monitoring, and NATS are separate compose overlays, so you can start from the generated files or run the same For Pocket-ID/your own OIDC provider, the shipped auth overlay is Keycloak-specific because it sets |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I usually avoid install scripts as I am not knowledgeable enough to read and understand them in my own, but I had ChatGPT look it through, and it got its OK ;-)
I would like to avoid install scripts messing up my machine, but it seems the installer only creates one cli tool.
I would like to go with the PostgreSQL option, the monitoring option and NATS JetStream.
I already run my own IDP (Pocket-ID) for OIDC, but the docs mostly reference keycloak. Is there an option I might have missed using my own IDP?
Usually I also like to edit my compose files as I micro-segment each stack into its own macvlan and I prefer bind mounts to named volumes.
Any tips on how to proceed? Use the installer and select the desired features then edit the compose fields manually according to the stated preferences?
Any tips are much appreciated.
All reactions