dbfbd489fa
* Multi-install support, Blueprints and config changes. Initial commit * Migrating jails to blueprints, first steps. Tested Working: - Transmission - Lidarr - Sonarr - Radarr fix lidarr config (+10 squashed commit) Squashed commit: [5f14653] always link ports folders [f18f2f0] Optional (blueprint) ports mount Fixes #89 [96ef7e7] chmod all the things [129e707] same mistake... again... [e1596dc] missing reference [6da3567] Forgot one reference [d78b5b6] Update wiki.yml [cecc53a] Update filecheck.yml [5244abd] basic settings changed. More involved blueprints still need changes, such as: Bitwarden, nextcloud, Mariadb [6568e92] jails -> blueprints * Added Tested Working: - KMS - Plex - Tautulli - Organizr - InfluxDB - MariaDB Many squashed small fixes included: Make *.rc executable (+13 squashed commit) Squashed commit: [b28aa83] use .rc for rc.d config files [e940a48] some mariadb cleanup [dc27aff] testing another way [83bd91b] Mariadb root password alter instead of update, initial config for unifi [0ca3074] some light config cleanup [a0d4352] also remove database from influxdb example config (db should be created when required) [2c218cc] Prepare influxdb and remove unneeded content [1b34109] more shellcheck fixups [c96566c] Some shellcheck cleanup [8969ca7] bitwarden mostly done, some work on nextcloud and unifi [7f89bfa] initial mariadb patch [dd7e85f] missed one problem [f814cb7] Initial pseudo-compatibility patch for unifi * Enable Bitwarden support and some small fixes/tweaks Fixes #95 more bugs and typo's (+3 squashed commit) Squashed commit: [3b5213e] Bitwarden not correctly installing db [b7438a5] yeah thats not gonna cut it... >.< [e7987c2] some slight bitwarden tweaks * Enable Unifi support and some small fixes/tweaks small unifi cleanup. Unifi is working (+3 squashed commit) Squashed commit: [d906d2d] chmod unifi [545e999] Add extra sanity, remove unneeded variables from example [b8c0b24] Some small Unifi Tweaks * Nextcloud Cleanup, Some fixes, Initial support for blueprintsystem Fixes #96 Fixes #97 Fixes #98 some bloat and syntax fixes (+5 squashed commit) Squashed commit: [78f6428] Some more nextcloud cleanup and tweaks - combines multiple variables for cert system selection (Fixes #98 ) - Default to self signed cert - Force manual admin password [7cacae4] slight fixes [3d81cda] More cleanup [50496cc] small mariadb fix and more nextcloud cleanup [c1b2c20] Cleaning nextcloud - Remove external DB (Fixes #97 ) - Remove Postgresql (Fixes #96 ) - Some preparation for blueprint * Nextcloud done and.. another... (+5 squashed commit) Squashed commit: [c65751b] caddy not installed right. [e5da66b] more fixes [a33300e] Damnit, two typo's same scentence [4292a7a] another typo [1b820cf] typo and example hotfix * Introduce version checking for config file
84 lines
2.7 KiB
Markdown
84 lines
2.7 KiB
Markdown
# Transmission
|
|
|
|
## Original README from the transmission github:
|
|
|
|
https://github.com/transmission/transmission
|
|
|
|
# Transmission
|
|
|
|
## About
|
|
|
|
Transmission is a fast, easy, and free BitTorrent client. It comes in several flavors:
|
|
* A native Mac OS X GUI application
|
|
* GTK+ and Qt GUI applications for Linux, BSD, etc.
|
|
* A headless daemon for servers and routers
|
|
* A web UI for remote controlling any of the above
|
|
|
|
Visit https://transmissionbt.com/ for more information.
|
|
|
|
## Command line interface notes
|
|
|
|
Transmission is fully supported in transmission-remote, the preferred cli client.
|
|
|
|
Three standalone tools to examine, create, and edit .torrent files exist: transmission-show, transmission-create, and transmission-edit, respectively.
|
|
|
|
Prior to development of transmission-remote, the standalone client transmission-cli was created. Limited to a single torrent at a time, transmission-cli is deprecated and exists primarily to support older hardware dependent upon it. In almost all instances, transmission-remote should be used instead.
|
|
|
|
Different distributions may choose to package any or all of these tools in one or more separate packages.
|
|
|
|
## Building
|
|
|
|
Transmission has an Xcode project file (Transmission.xcodeproj) for building in Xcode.
|
|
|
|
For a more detailed description, and dependencies, visit: https://github.com/transmission/transmission/wiki
|
|
|
|
### Building a Transmission release from the command line
|
|
|
|
$ tar xf transmission-2.92.tar.xz
|
|
$ cd transmission-2.92
|
|
$ mkdir build
|
|
$ cd build
|
|
$ cmake ..
|
|
$ make
|
|
$ sudo make install
|
|
|
|
### Building Transmission from the nightly builds
|
|
|
|
Download a tarball from https://build.transmissionbt.com/job/trunk-linux/ and follow the steps from the previous section.
|
|
|
|
If you're new to building programs from source code, this is typically easier than building from Git.
|
|
|
|
### Building Transmission from Git (first time)
|
|
|
|
$ git clone https://github.com/transmission/transmission Transmission
|
|
$ cd Transmission
|
|
$ git submodule update --init
|
|
$ mkdir build
|
|
$ cd build
|
|
$ cmake ..
|
|
$ make
|
|
$ sudo make install
|
|
|
|
### Building Transmission from Git (updating)
|
|
|
|
$ cd Transmission/build
|
|
$ make clean
|
|
$ git pull --rebase --prune
|
|
$ git submodule update
|
|
$ cmake ..
|
|
$ make
|
|
$ sudo make install
|
|
|
|
## Contributing
|
|
|
|
### Code Style
|
|
|
|
You would want to setup your editor to make use of uncrustify.cfg and .jsbeautifyrc configuration files located in the root of this repository.
|
|
|
|
If for some reason you are unwilling or unable to do so, there is a shell script which you could run either directly or via docker-compose:
|
|
|
|
$ ./code_style.sh
|
|
or
|
|
$ docker-compose build --pull
|
|
$ docker-compose run --rm code_style
|