Skip to content

Commit 2f5c2c6

Browse files
committed
Enhance README with new data syncing commands and update image tag to version 2.2.3
1 parent 1ae380a commit 2f5c2c6

File tree

2 files changed

+42
-1
lines changed

2 files changed

+42
-1
lines changed

choose-native-plants/README.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,47 @@ $POD_NAME = kubectl get pods -n choose-native-plants -l app.kubernetes.io/name=c
5757
kubectl exec -it $POD_NAME -n choose-native-plants -c choose-native-plants-app -- node download --skip-images
5858
```
5959

60+
### Syncing Data Down (Database Only)
61+
62+
To sync data down from Linode Object Storage without images (equivalent to `npm run sync:down:db`), use this command:
63+
64+
```powershell
65+
$POD_NAME = kubectl get pods -n choose-native-plants -l app.kubernetes.io/name=choose-native-plants -o jsonpath='{.items[0].metadata.name}'
66+
kubectl exec -it $POD_NAME -n choose-native-plants -c choose-native-plants-app -- npm run sync:down:db
67+
```
68+
69+
Alternatively, you can run the script directly:
70+
71+
```powershell
72+
$POD_NAME = kubectl get pods -n choose-native-plants -l app.kubernetes.io/name=choose-native-plants -o jsonpath='{.items[0].metadata.name}'
73+
kubectl exec -it $POD_NAME -n choose-native-plants -c choose-native-plants-app -- node scripts/sync-down.js --skip-images
74+
```
75+
76+
### Fast Update Data (Download and Massage)
77+
78+
To download data without images and then process it (equivalent to `npm run fast-update-data`), use this command:
79+
80+
```powershell
81+
$POD_NAME = kubectl get pods -n choose-native-plants -l app.kubernetes.io/name=choose-native-plants -o jsonpath='{.items[0].metadata.name}'
82+
kubectl exec -it $POD_NAME -n choose-native-plants -c choose-native-plants-app -- npm run fast-update-data
83+
```
84+
85+
This command combines downloading data (without images) and massaging the data in a single operation.
86+
87+
**Note:** This is a long-running command that may take several minutes. If you see a websocket error (`websocket: close 1006 (abnormal closure): unexpected EOF`), the command may have completed successfully in the pod despite the connection error. You can verify completion by checking the pod logs:
88+
89+
```powershell
90+
$POD_NAME = kubectl get pods -n choose-native-plants -l app.kubernetes.io/name=choose-native-plants -o jsonpath='{.items[0].metadata.name}'
91+
kubectl logs $POD_NAME -n choose-native-plants -c choose-native-plants-app --tail=50
92+
```
93+
94+
Alternatively, for long-running commands, you can run them without the interactive flag (`-it`) to avoid connection issues:
95+
96+
```powershell
97+
$POD_NAME = kubectl get pods -n choose-native-plants -l app.kubernetes.io/name=choose-native-plants -o jsonpath='{.items[0].metadata.name}'
98+
kubectl exec $POD_NAME -n choose-native-plants -c choose-native-plants-app -- npm run fast-update-data
99+
```
100+
60101
### Massaging Data
61102

62103
To process the data, use this command:

choose-native-plants/release-values.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
app:
22
image:
3-
tag: "2.2.1"
3+
tag: "2.2.3"
44
env:
55
- name: NODE_OPTIONS
66
value: "--openssl-legacy-provider --max-old-space-size=3072"

0 commit comments

Comments
 (0)