Server Gameplan

- [x] Add in skeleton command line
- Current idea is something like `dist-server ((start | stop) [--tracker | --seeder | --database) | (add PACKAGE_PATH …)`
- So basically just three subcommands where two manage running the two different servers used by the server portion and the third adds in new packages
- May be worth it to eventually add in some basic status command
- [x] Test out running `opentracker` for the tracker server so that we can build off this for the actual implementation
- [x] Test out adding torrents with `transmission-daemon` and `transmission-cli`
- [x] ~~Add in logic for detecting that all required software is installed~~ (Considered unnecessary)
- [x] ~~`opentracker`~~
- [x] ~~`transmission-cli` and `transmission-daemon`~~
- [x] ~~`intermodal`~~
- [x] ~~Add in logic for detecting if something is running~~ (Nixed)
- [x] ~~`named-file-server`~~
- [x] ~~`opentracker`~~
- [x] ~~`transmission-daemon`~~
- [x] Flesh out subcommand functionality
- [x] `start`
- [x] Need to setup distributing the database through a webserver
- (Experiments of this have already been done with rocket, but look into tide too)
- [x] Figure out what needs to be done to run `transmission-daemon` and `opentracker`
- [x] `stop` - Should be as simple as sending signals to all the processes
- [x] `add`
- [x] Add logic for verifying that a package has the correct structure
- [x] Add in a manifest for the package with some basic metadata
- [x] Compress all the files
- [x] Generate the torrent file
- [x] Add the compressed package and torrent file to a location known by the seeder and add the torrent to the seeder
- [x] Add the entry to the database
- [x] ~~Add the infohash to `opentracker`'s whitelist~~ (Nixed for simplicity)