Dtube Permanente v0.2 quick start guide - One Love IPFS

Intro / Commentary

In preparation for release v0.2 i decided to make a quick start guide. Anyone interested in setting a Permanente bot/server/client/headmaster. This is the place to go. I was going for a single post, containing everything. Though that's too much work for me at one time. I still have lots of code review to do. Release planned tomorrow or the day after. However you can fetch the latest code on dev-01 branch.
Anyone not familiar with this project please visit Project gitlab v0.2 Announcement, or Onelove ipfs blog post (written by @graylan). These are a few helpful resources to understand what this project is about. I haven't gotten around to writing an official descriptive post. If you have any direct questions comment below, i would be happy to answer them. It will help me get an idea of what the community wants to know. I will be writing more documentation soon, just you wait. It will be so easy your grandma could setup it up. (that was a joke, i will have to test that theory!)

I encourage you to give me feedback! thoughts! whatever is on your mind!

quick start guide / documentation

Remember although this is a quick start guide it is not designed for plug and play. All of the following documentation should be applicable to v0.2 once released.

Linux/MacOSX Compilation

1. Download git clone https://gitlab.com/vaultec/dtubepermanente.git
2. Change directory cd dtubepermanente
3. (Optional) Change branch to dev git checkout dev-01
   (If you want latest changes)
4. Compile mvn clean compile assembly:single
5. Copy all jars to current directory cp target/*.jar .

quick entire command: git clone https://gitlab.com/vaultec/dtubepermanente.git; cd dtubepermanente; mvn clean compile assembly:single; cp target/*.jar .

Usage

Server/Bot:

usage: Permanente v0.2
 -a,--api                 When flag is set, API server is started
 -ap,--apiport <arg>      Set API port, 0-65563
 -bot,--bot               Starts discord bot. TODO
 -bt,--bot.token <arg>    Specify discord bot token. (defaults to config
                          without) TODO
 -cf,--configfile <arg>   Specify config file location.
 -d,--default             Use default configuration location.
                          (%Workingdirectory%/Config.json) RECOMMENDED
 -fh,--ipfshost <arg>     Specify ipfs host, must be in ipfs host format.
                          (defaults to localhost:5001)
 -h,--headmaster          Operate a headmaster on API. (Enables API)
 -s,--saveconfig          Saves configuration that is specified.
 -st,--exitonsave         Exits program after data save.

Client:

usage: Permanente Client v0.2
 -cf,--configfile <arg>   Specify config file location.
 -d,--default             Use default configuration location.
                          (%Workingdirectory%/ClientConfig.json)
                          RECOMMENDED
 -h,--headmaster <arg>    Specify headmaster URL. (Overrides config)
 -s,--saveconfig          Saves configuration that is specified.
 -st,--exitonsave         Exits program after data save.
 -t,--token <arg>         Specify authentication token.(Overrides config)
 -u,--userid <arg>        Specify userid. (Overrides config)

Other settings are not built into command line arguments, but fully changeable via config.json and clientconfig.json

See config.java and clientconfig.java

I would suggest using option --default --api for beginners. Use the demo web interface (should work without issue) you should start seeing Qm hashes in the log and in dat.json entries there too.

If you want to talk to me directly. join one love discord. You should find me under dev role as Asuska | @vaultec

OFFICIAL release signing key
For the advanced users who want to verify releases.
All binary releases should be signed.

IPFS hash: QmVhPvcQ3rdMKRxjonjqcNDDaYuwHJYEh4HpSrR6yLe77p
Fingerprint: 75D07488ACA53CD0ED96D429CA9811860B0B9520
IPFS link

-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEXBm98BYJKwYBBAHaRw8BAQdAwssGVUdGVfSla4ellhUY3TL6T9tkY3ZjXOoE
FbaPGUa0F1ZhdWx0ZWMgUmVsZWFzZSBTaWduaW5niJYEExYIAD4WIQR10HSIrKU8
0O2W1CnKmBGGCwuVIAUCXBm98AIbAwUJA8NMUAULCQgHAgYVCgkICwIEFgIDAQIe
AQIXgAAKCRDKmBGGCwuVIDdgAQDSnjUgNNZnwuEtFWAmfYkpx/GaDRno/ECkMubX
qyhVbwD/R3bMWgORUNz9xckghPGn/FlLs3iNNKW8DLOWuenVRwK4OARcGb3wEgor
BgEEAZdVAQUBAQdACKMhnR3tJDx4bKK8OdUmGjzWbKzKSq/iQxDBOCj2RTYDAQgH
iH4EGBYIACYWIQR10HSIrKU80O2W1CnKmBGGCwuVIAUCXBm98AIbDAUJA8NMUAAK
CRDKmBGGCwuVIH9TAQDwLkPc6/9eV9GjIoqWS32Y6Z5ExA5p3leRD4f3p0dcogD6
AwXOU17R4KavhRtORRzvckZ/YTWGVPkhevaOPh9MVgo=
=n6IJ
-----END PGP PUBLIC KEY BLOCK-----

Note if this key is ever deemed insecure it will be immediately revoked and a new key will be issued

-- @vaultec