Update self-host kube example to Huly v424 (#126)

Signed-off-by: Alexander Onnikov <Alexander.Onnikov@xored.com>
This commit is contained in:
Alexander Onnikov
2025-02-03 13:07:30 +07:00
committed by GitHub
parent 7d47534de7
commit f86156a656
13 changed files with 60 additions and 33 deletions
+1 -1
View File
@@ -1,4 +1,4 @@
HULY_VERSION=v0.6.411
HULY_VERSION=v0.6.424
DOCKER_NAME=huly
# The address of the host or server from which you will access your Huly instance.
+24
View File
@@ -1,5 +1,29 @@
# Huly Migration
This document describes the changes required to update Huly from one version to another. Most of updates require updating Docker containers versions.
Though, some updates may require updating other configuration options. In this case, you should review the updated configuration options and update them accordingly.
## v0.6.424
Web-push keys have been moved from the `front` service to the `ses` service. If you are using the `ses` service, you will need to update the configuration:
```yaml
front:
...
environment:
...
# Remove the following lines
# - PUSH_PUBLIC_KEY=your public key
# - PUSH_PRIVATE_KEY=your private key
ses:
...
environment:
...
# Add the following lines
- PUSH_PUBLIC_KEY=your public key
- PUSH_PRIVATE_KEY=your private key
```
## v0.6.411
No changes required.
+25 -22
View File
@@ -66,19 +66,19 @@ sudo apt-get install npm
Install web-push using npm
```
```bash
sudo npm install -g web-push
```
Generate VAPID Keys. Run the following command to generate a VAPID key pair:
```
```bash
web-push generate-vapid-keys
```
It will generate both keys that looks like this:
```
```bash
=======================================
Public Key:
@@ -92,9 +92,9 @@ asdfsadfasdfsfd
Keep these keys secure, as you will need them to set up your push notification service on the server.
Add these keys into `compose.yaml` in section `services:front:environment`:
Add these keys into `compose.yaml` in section `services:ses:environment`:
```
```yaml
- PUSH_PUBLIC_KEY=your public key
- PUSH_PRIVATE_KEY=your private key
```
@@ -105,21 +105,22 @@ Add these keys into `compose.yaml` in section `services:front:environment`:
2. [Create new policy](https://us-east-1.console.aws.amazon.com/iam/home?region=eu-central-1#/policies/create) with
following permissions:
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ses:SendEmail",
"ses:SendRawEmail"
],
"Resource": "*"
}
]
}
```
```yaml
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ses:SendEmail",
"ses:SendRawEmail"
],
"Resource": "*"
}
]
}
```
3. [Create separate IAM user](https://us-east-1.console.aws.amazon.com/iam/home?region=eu-central-1#/users/create) for
SES API access. Assign previously created policy to this user during creation.
@@ -128,7 +129,7 @@ Add these keys into `compose.yaml` in section `services:front:environment`:
```yaml
ses:
image: hardcoreeng/ses:v0.6.411
image: hardcoreeng/ses:v0.6.424
container_name: ses
expose:
- 3335
@@ -136,6 +137,8 @@ Add these keys into `compose.yaml` in section `services:front:environment`:
- SOURCE=<EMAIL_FROM>
- ACCESS_KEY=<SES_ACCESS_KEY>
- SECRET_KEY=<SES_SECRET_KEY>
- PUSH_PUBLIC_KEY=<PUSH_PUBLIC_KEY>
- PUSH_PRIVATE_KEY=<PUSH_PRIVATE_KEY>
- REGION=<SES_REGION>
- PORT=3335
restart: unless-stopped
@@ -169,7 +172,7 @@ self-hosted Huly, perform the following steps:
```yaml
love:
image: hardcoreeng/love:v0.6.411
image: hardcoreeng/love:v0.6.424
container_name: love
ports:
- 8096:8096
+1 -1
View File
@@ -57,7 +57,7 @@ spec:
configMapKeyRef:
name: huly-config
key: TRANSACTOR_URL
image: hardcoreeng/account:v0.6.411
image: hardcoreeng/account:v0.6.424
name: account
ports:
- containerPort: 3000
@@ -32,7 +32,7 @@ spec:
secretKeyRef:
name: huly-secret
key: SERVER_SECRET
image: hardcoreeng/collaborator:v0.6.411
image: hardcoreeng/collaborator:v0.6.424
name: collaborator
ports:
- containerPort: 3078
+1 -1
View File
@@ -69,7 +69,7 @@ spec:
value: http://stats
- name: DESKTOP_UPDATES_CHANNEL
value: selfhost
image: hardcoreeng/front:v0.6.411
image: hardcoreeng/front:v0.6.424
name: front
ports:
- containerPort: 8080
+1 -1
View File
@@ -47,7 +47,7 @@ spec:
value: http://account
- name: STATS_URL
value: http://stats
image: hardcoreeng/fulltext:v0.6.411
image: hardcoreeng/fulltext:v0.6.424
name: fulltext
ports:
- containerPort: 4700
+1 -1
View File
@@ -15,7 +15,7 @@ spec:
app: rekoni
spec:
containers:
- image: hardcoreeng/rekoni-service:v0.6.411
- image: hardcoreeng/rekoni-service:v0.6.424
name: rekoni
env:
- name: SECRET
+1 -1
View File
@@ -15,7 +15,7 @@ spec:
app: stats
spec:
containers:
- image: hardcoreeng/stats:v0.6.411
- image: hardcoreeng/stats:v0.6.424
name: stats
env:
- name: PORT
+1 -1
View File
@@ -51,7 +51,7 @@ spec:
secretKeyRef:
name: huly-secret
key: SERVER_SECRET
image: hardcoreeng/transactor:v0.6.411
image: hardcoreeng/transactor:v0.6.424
name: transactor
ports:
- containerPort: 3333
+1 -1
View File
@@ -47,7 +47,7 @@ spec:
secretKeyRef:
name: huly-secret
key: SERVER_SECRET
image: hardcoreeng/workspace:v0.6.411
image: hardcoreeng/workspace:v0.6.424
name: workspace
resources:
limits:
+1 -1
View File
@@ -1,6 +1,6 @@
#!/usr/bin/env bash
HULY_VERSION="v0.6.411"
HULY_VERSION="v0.6.424"
DOCKER_NAME="huly"
CONFIG_FILE="huly.conf"
+1 -1
View File
@@ -14,7 +14,7 @@ if [ -z "$LETSENCRYPT_EMAIL" ]; then
exit 1
fi
export HULY_VERSION="v0.6.411"
export HULY_VERSION="v0.6.424"
export HULY_SECRET="secret"
export SERVER_ADDRESS=$DOMAIN_NAME
export LETSENCRYPT_EMAIL=$LETSENCRYPT_EMAIL