mirror of
https://github.com/lukevella/rallly-selfhosted.git
synced 2025-12-10 02:42:49 +01:00
fixed blank line, added more info to README, fixed spelling of a comment
This commit is contained in:
parent
6d47452796
commit
c1ded052df
@ -14,6 +14,7 @@ This directory contains base Kubernetes manifests to self-host Rallly. It separa
|
|||||||
- **Important:** Do not commit the `secrets.yaml` file with real credentials to version control.
|
- **Important:** Do not commit the `secrets.yaml` file with real credentials to version control.
|
||||||
- Update `POSTGRES_PASSWORD` and `SECRET_PASSWORD` (use `openssl rand -hex 32` to generate).
|
- Update `POSTGRES_PASSWORD` and `SECRET_PASSWORD` (use `openssl rand -hex 32` to generate).
|
||||||
- **Critical:** Ensure the password in `DATABASE_URL` matches `POSTGRES_PASSWORD`. Both must use the same value.
|
- **Critical:** Ensure the password in `DATABASE_URL` matches `POSTGRES_PASSWORD`. Both must use the same value.
|
||||||
|
- **Format:** The `DATABASE_URL` format should look like this: `postgres://<user>:<password>@<postgres-service-name>:5432/<db-name>`.
|
||||||
|
|
||||||
2. **Config (`rallly-config.yaml`):**
|
2. **Config (`rallly-config.yaml`):**
|
||||||
- Update `NEXT_PUBLIC_BASE_URL` to match your domain.
|
- Update `NEXT_PUBLIC_BASE_URL` to match your domain.
|
||||||
@ -43,6 +44,12 @@ kubectl apply -f rallly.yaml
|
|||||||
kubectl apply -f ingress.yaml
|
kubectl apply -f ingress.yaml
|
||||||
```
|
```
|
||||||
|
|
||||||
|
**Note:** If you update `secrets.yaml` or `rallly-config.yaml` _after_ deployment, you must restart the Rallly pods for changes to take effect:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
kubectl rollout restart deployment rallly
|
||||||
|
```
|
||||||
|
|
||||||
## Verification
|
## Verification
|
||||||
|
|
||||||
Check that the pods are running:
|
Check that the pods are running:
|
||||||
|
|||||||
@ -26,7 +26,7 @@ spec:
|
|||||||
app: rallly
|
app: rallly
|
||||||
strategy:
|
strategy:
|
||||||
type: RollingUpdate
|
type: RollingUpdate
|
||||||
# Zero-donwtime deployment strategy
|
# Zero-downtime deployment strategy
|
||||||
rollingUpdate:
|
rollingUpdate:
|
||||||
maxUnavailable: 0
|
maxUnavailable: 0
|
||||||
maxSurge: 1
|
maxSurge: 1
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user