Oh hey! Where have we been you ask? After a few major delays due to some unexpected… let’s call it… nature being nature, we’re back with another Developer Update to keep you gals and guys in the loop! Here’s a quick rundown on where we’re at with development for the much anticipated QuickBox Pro v3.
conversions
At this point in the development, we’re handling the conversion of the 50+ software packages that QuickBox Pro includes. As we are going through and rewriting each build package, one by one, we are doing some additional quality control. This can easily put some of the more complicated build packages at around 3 to 5 hours to finalize the conversion. In short, it’s an in depth process that takes a fair amount of time and patience. We are working incredibly hard to ensure that when QuickBox Pro v3 launches, it’s a polished and easy to use product.
features
As we work on revisions, we are not only focused on rewriting the packages, but the additional inclusion of features to certain software builds. One such feature adjustment is the install of Filebot. In v2, this process is rather cumbersome and involves manual work to get it staged (ie; install, then copy your license file to the server, then you have to activate with the filebot command). What a chore! With v3 however, you’ll be able to simply copy/paste your license file directly into the CLI prompt. Here’s a quick example (tested with an expired license to confirm it calls home and works)
qb install filebot -u echo FileBot will now be installed. This process may take a few minutes... Adding additional keys and sources for FileBot... Checking and performing apt updates... Installing FileBot dependencies... Building FileBot... Configuring FileBot Would you like to use FileBot to process rTorrent downloads? [y/n]: > y Would you like to use a custom directory for processed files? [y/n] (Default: /home/echo/Media): > n Would you like to use FileBot to process Deluge downloads? [y/n]: > n Would you like to activate your license? [y/n]: > y Please copy/paste the full contents of your license file. Press ctrl+D when done to continue. > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Product: FileBot Name: [redacted] Email: [redacted] Order: P19854281 Issue-Date: 2020-11-13 Valid-Until: 2021-11-20 -----BEGIN PGP SIGNATURE----- [redacted] -----END PGP SIGNATURE----- Attempting to activate filebot_license.psm ... Initialize UserHome folder: /home/echo/.filebot/filebot-portable/data/0 Initialize Cache folder: /home/echo/.filebot/filebot-portable/data/0/cache Initialize Logs folder: /home/echo/.filebot/filebot-portable/data/0/logs Initialize TemporaryFiles folder: /home/echo/.filebot/filebot-portable/data/0/tmp Initialize new disk cache: /home/echo/.filebot/filebot-portable/data/0/cache/0 Unknown Error: P19854281 has EXPIRED on 2021-11-20 Updating database... Backing up FileBot configuration... FileBot installation complete.
Much better!
Another feature coming to v3, will be the ability to install Emby as a multi-user software. Meaning that the System Admin can set Emby-Server to the users group, and any user in said group will be able to install Emby. We’ve additionally included options to install stable versions or beta versions, at any time a stable version can be updated to a beta release. Here’s a quick preview of that command.
Install Emby stable release:qb install emby -u USERNAME
Install Emby beta release:qb install emby -u USERNAME -o beta
You can update a stable release to a beta release, should you be so bold:qb update emby -u USERNAME -o beta
Just like that!
Here’s a quick preview to proof of setup: (all developments are done on a localized/closed server environment)
We’ll be reviewing this an option for Plex as well, once we’re at that point in the conversion process, so definitely stay tuned for that!
In the meantime, catch you all next week! 💖
