Deployment and management tools for an entire streaming platform that can reside on a server (local, remote, hosted, VPS) with media files stored on cloud services like Google Drive or Dropbox.
MIT License
33
stars
10
forks
source link
Using service account json file while configuring rclone, breaks omnimount container deployment. #52
When deploying OmniStream for the first time, I encountered this issue:
While configuring rclone, if you use a service account JSON file to authenticate (Ex. ~/mySA.json), the omnimount container fails to deploy as the absolute path to mySA.json does not exist within it.
Two workarounds:
Create a /config/ directory and put mySA.json in it in the host running the containers and manually copy it to ~/OmniStream/config/omnimount/, then use /config/mySA.json while configuring rclone.
Edit ~/.config/rclone/rclone.conf and replace the line service_account_file = with service_account_credentials = and paste mySA.json contents (remove line breaks).
When deploying OmniStream for the first time, I encountered this issue:
While configuring rclone, if you use a service account JSON file to authenticate (Ex.
~/mySA.json), the omnimount container fails to deploy as the absolute path tomySA.jsondoes not exist within it.Two workarounds:
/config/directory and putmySA.jsonin it in the host running the containers and manually copy it to~/OmniStream/config/omnimount/, then use/config/mySA.jsonwhile configuring rclone.~/.config/rclone/rclone.confand replace the lineservice_account_file =withservice_account_credentials =and pastemySA.jsoncontents (remove line breaks).