So does anybody have a walkthrough on how to set this beastie up? I'm not unfamiliar with docker and containers (I have personal Mastodon, Nextcloud, and Synapse Instances running via docker-compose)
Sort of where I'm stuck right now is what I need to change in the .env file, per the instructions here:
$ sudo apt-get install git
$ git clone https://codeberg.org/Kbin/kbin-core.git kbin
$ cd kbin
$ mkdir public/media
$ sudo chown 82:82 public/media
$ sudo chown 82:82 var
$ cp .env.example .env
$ vi .env # esc + !q + enter to exit
or
$ nano .env
Make sure you have substituted all the passwords and configured the basic services in .env file.
(yes, I know it's somewhat commented, but it's not exactly super clear) and also how to handle building it in a non-local configuration (my VPS is elsewhere, so going to kbin.localhost to do anything isn't really going to work)
I ignored the thing about kbin.localhost and everything on https://feddit.online is working well, also in my test environment. So, you can probably skip it too.
The "var" folder will not be found in the kbin folder so the chown will not work. What I did, and from other comments that I've read, I think this is what it should have been, "sudo chown 82:82 /var"
Here's my .env file without the secrets.
Where I mention a long secret, you can use this Linux command to generate a strong 32-character secret
openssl rand -hex 32
kbin variables
SERVER_NAME="feddit.online"
KBIN_DOMAIN=feddit.online
KBIN_TITLE=/kbin
KBIN_DEFAULT_LANG=en
KBIN_FEDERATION_ENABLED=true [email protected] [email protected]
KBIN_JS_ENABLED=true
KBIN_REGISTRATIONS_ENABLED=true
KBIN_API_ITEMS_PER_PAGE=25 #Frankly unsure if the next line does anything
KBIN_STORAGE_URL=https://media.feddit.online
KBIN_META_TITLE="Kbin Lab"
KBIN_META_DESCRIPTION="content aggregator and micro-blogging platform for the fediverse"
KBIN_META_KEYWORDS="kbin, content agregator, open source, fediverse"
KBIN_HEADER_LOGO=false
KBIN_CAPTCHA_ENABLED=true
Ok, so it looks like I'm going to have to do a bit of jiggery pokery, as I don't need caddy, I've already got an nginx reverse proxy running on the host. (I think they both provide similar functionality?)