recipe-maintainers/lasuite-docs
0
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Update README

Browse Source
This commit is contained in:
notplants
2026-01-08 18:02:50 -05:00
parent 0bd2f0e830
commit be7f21b4d4
1 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@ -30,7 +30,7 @@ You should then be able to visit the landing page of your app, but not yet to lo
lasuite-docs **requires** an OpenID Connect (OIDC) single sign-on provider; deployment has been tested with [Keycloak](https://git.coopcloud.tech/coop-cloud/keycloak), which we recommend, or you could also try [Authentik](https://git.coopcloud.tech/coop-cloud/authentik), both of which are installable using Co-op Cloud.
Instructions for integrating keycloak with drive after deploying it, are below.
Instructions for integrating keycloak with docs after deploying it, are below.
* In keycloak, create a realm (save the name of this realm, you will need it later)
* Within that realm, create a client
@ -41,7 +41,9 @@ Instructions for integrating keycloak with drive after deploying it, are below.
- Client authentication: True
- PKCE method: none
* Within the client tab, for your client, click on "Credentials". Click on the the copy button to copy "Client Secret" so you can insert this into your coop cloud deployment in the next step.
* `abra app secret insert <app-name> oidc_rp_client_secret v1 <yoursecret>`
* `abra app secret insert <app-name> oidc_rpcs v2 <yoursecret>`
* `abra app config <app-name>` # set SECRET_OIDC_RPCS_VERSION=v2
* Now create a user for this client within keycloak. Within the Users tab, click "Add User". Any username and password works. Save this info.
You then additionally need to modify the config of docs to point to your keycloak deployment.
@ -72,10 +74,9 @@ DJANGO_EMAIL_FROM=noreply@example.com
You then need to insert the password for your smtp server as a secret:
`abra app secret insert <app-name> email_pass v1 <youremailpass>`
* `abra app secret insert <app-name> email_pass v2 <youremailpass>`
* `abra app config <app-name>` # set SECRET_EMAIL_PASS_VERSION=v2
Then redeploy the app, and automated e-mail sending should work (for example for inviting someone to collaborate on a document):
Then redeploy the app, and automated e-mail sending should work:
`abra app deploy <app-name> --force`