helm VS Transmission

When using the Nextcloud Helm Charts, how do you execute OCC commands within a Kubernetes the pod? I've tried:

I'm running Nextcloud in Kubernetes, using Nextcloud's Helm Chart. With a default installation (no apps or configuration changes), I get the following errors in the logs:

In each namespace you would deploy a nextcloud instance via whatever method you like. For example, the nextcloud helm chart.

I'm using the official helm chart to install nextcloud: https://github.com/nextcloud/helm

A nextcloud installation (you can install via helm within the same k8s cluster)

There is already a GitHub issue: https://github.com/nextcloud/helm/issues/10

I'm not a Nextcloud expert, but your config file looks okay compared to some instances deployed using the nextcloud helm chart.The resulting config uses APCu for memcache.local ('memcache.local' => '\OC\Memcache\APCu') as recommended in the memory caching documentation.

For nextcloud in particular, what you want can be done. I've seen it done in their kubernetes helm chart (https://github.com/nextcloud/helm) .

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

Grab this file. Install Transmission on Mac or Deluge on Win. Optional: run a VPN if you're in the US(mostly) and worried about your ISP sending you a cease-and-desist notice. Open the file using the app you installed. Wait. It should start within a minute or two and download progress will be seen. Speed depends on how many people are sharing it. Any issues, let me know.

Why "NO TORRENT"? Just get TransmissionBT and torrent whatever you want

Its intresting you mention that, before reading your reply I went and created a post in the Q n A section, asking for help about this very thing and I linked to the same GitHub issue you linked to here. I have yet to get a reply lol.here

transmission can run as a headless server with a web gui

Get a VPN like Windscribe(set windscribe firewall to on instead of auto), forward your port via their website. Use a good torrent client like https://transmissionbt.com/ set that port in the options, and add a blocklist https://github.com/Naunter/BT\_BlockLists/raw/master/bt\_blocklists.gz