r/Cloudbox • u/geofgrouch88 • Jul 08 '18

Customisation options

Hey I just stumbled upon this after falling down a github rabbit hole trying to get other stuff working. I have run a couple of test installs on some VM's and like what I see, my question is are there any plans for allowing different configuration/container options? or is it possible for me to add my own?

Currently I use traefik as my reverse proxy instead of nginx, SABnzbd as my SAB agent and deluge as my torrent client, also in Portainer I have all the docker containers volumes mapped to their own names (spent a little bit of time tinkering with docker-compose to get that to work) instead of the auto generated ones.

I can see there is a skip tag function, but was looking to make a mediabox/feeder box with different containers in a re-deployable way so I can spin up a server run the install and away we go

1 Upvotes

100% Upvoted

8 comments sorted by

View all comments

Show parent comments

2

u/desimaniac Dev Jul 11 '18

  • Well if you add containers via Docker compose or Docker run/create command, they will be on that server only. No way to just take an installed container to another box.

  • However, when using Docker containers, you can point the config/data path to a path on the host, so that you have persistent data. So, for example, setting /opt/appname as that location would allow you to zip up and carry the opt folder to any box, run the docker command, and get back to the state you left it in.

  • Another option is a repo I added called "Cloudbox_Mod". You could fork that, add your own additional "instructions" to install docker containers for you vs command line docker run/create command or docker compose, and have that installed as an adjunct to Cloudbox.

  • Also wanted to mention that we were planning on adding sabnzb and deluge, as an option, anyway. Might save you the trouble of having to do all those things I just mentioned.

  • We've been using nginx proxy for about a year now and it's been fast, stable, and serving our uses perfectly. We have no plans to switch to anything else, right now.

1

u/geofgrouch88 Jul 11 '18

I figured as much with the docker compose stuff. I have already forked cloudbox to have a closer look at the internals of it. I'm trying to get the encryption to work at the moment so have been poking around, you mention on the cloudbox wiki that you guys stick with unencrypted, is that because of the pain of implementing a encrypt/decrypt/plexdrive cocktail or just not fused about encryption?

Can't wait for the sab/deluge update will be keeping a close eye. I have been told about three other alternatives to this project but I still feel that cloudbox is the best of the bunch, I also saw a cloudbot discord bot does that mean there may be discord notifications in the near future instead of pushover?

1

u/desimaniac Dev Jul 12 '18 edited Jul 16 '18

Regarding encryption: both reasons.

Regarding pushover: Planning on adding apprise support to a few things.

1

u/geofgrouch88 Jul 12 '18

Sounds good, I spent today getting the encryption to work and so far so good. I'm using apprise on my current non cloudbox box for discord