vikunja
/
helm-chart
2
2
Fork 5
Code Issues 7 Pull Requests Packages Projects Releases 1 Wiki Activity

Fix README.md
continuous-integration/drone/pr Build is passing Details

This commit is contained in:
perf3ct 2023-10-11 06:58:54 -07:00
parent 3ea99647e2
commit 688a055c36
No known key found for this signature in database
GPG Key ID: 569C4EEC436F5232
1 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -10,13 +10,13 @@ This Helm Chart deploys both the Vikunja [frontend](https://hub.docker.com/r/vik
## Quickstart
The majority of default values defined in `values.yaml` should be compatible for your deployment. Additionally, if you utilize an Ingress for both the API and Frontend, you will be able to access the frontend out of the box. However, it won't have any default credentials, you will need to **either** enable registration, or execute `/bin/sh` on the API container and run the following command:
The majority of default values defined in `values.yaml` should be compatible for your deployment. Additionally, if you utilize an Ingress for both the API and Frontend, you will be able to access the frontend out of the box. However, it won't have any default credentials. So, you'll need to create an account using the registration button.
```bash
./vikunja user create --email <user@email.com> --user <user1> --password <password123>
```
That should be it!
If you do **not** wish to execute the above command in order to create a new user, you'll need to enable registration by appending
## Registration (creating users)
You can disable registration (if you do not with to allow others to register on your Vikunja), by providing the following values in your `values.yaml`:
```yaml
api:
@ -26,10 +26,14 @@ api:
data:
config.yml:
service:
enableregistration: true
enableregistration: false
```
Once you've registered your user, feel free to disable registration if you don't wish for other users to register.
If you need to create another user, you could opt to execute the following command on the `api` container:
```bash
./vikunja user create --email <user@email.com> --user <user1> --password <password123>
```
### Modifying Resources