Slyke

Is it possible to put an init container on pg to set permissions?

@MinerYang this might be caused by having the PV on the node being an NFS mounted directory.

Should I just blow the database all away and use Postgres?

Ohh, that's too bad. Basically means you can't use it behind a reverse proxy, unless you dedicate a subdomain or different port for it.

That causes a whole bunch of 404s, as it still tries to use the top level directory. 

On the Gitea demo site, it timed out after about 24 hours with the following error: ``` Migrating from https://github.com/qmk/qmk_firmware failed. error while listing repos: GET https://api.github.com/repos/qmk/qmk_firmware/pulls/9116/reviews/413400876/comments?per_page=100: 500 [] ```

Actually, if I zoom out REALLY far, like to space, I can see some weird shapes, which look like part of the input images. Moving the object around causes different...

I tested this out with the docker image of Elasticsearch and could reproduce the error. It was fixed with an initContainer: ``` initContainers: - name: perm-update image: busybox:1.36.1 imagePullPolicy: IfNotPresent...

My workaround: Edit file `./node_modules/node-red-contrib-home-assistant-websocket/dist/common/services/StorageService.js`: Change function defined on line 36 `checkPermissions()` to: ``` checkPermissions(path) { if (!path) return true; try { fs_1.default.accessSync(path, fs_1.default.constants.R_OK | fs_1.default.constants.W_OK); } catch (err) {...

It's a valid host. I'm running this inside my Kubernetes cluster and that's the service FQDN for Mosquitto. I'm seeing some logs come through: ``` notice - [19:38:56.542] [Matterbridge]: Package...