SFaulken

joined 1 year ago
[–] SFaulken@kbin.social 10 points 1 year ago

I don't care about beeper one way or another, but that bloody image with the post, it needs to die in a fire.

[–] SFaulken@kbin.social 5 points 1 year ago (2 children)

I will never claim they are authentic, or even great, but I will destroy the 2 for a buck tacos.

[–] SFaulken@kbin.social 1 points 1 year ago

That's XMMP different thing =P

[–] SFaulken@kbin.social 1 points 1 year ago

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?)

[–] SFaulken@kbin.social 2 points 1 year ago (2 children)

Hot Damn, thanks. That should get me headed in the right direction anyway.

 

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)

So yeah, ELI5.

[–] SFaulken@kbin.social 30 points 1 year ago (2 children)

I mean, that's sort of what xdg is intended to accomplish, with making $HOME/.config be the place, but it's kind of up to the individual software developers to comply. (Yes, I know, this doesn't really apply to Windows/Mac OS) But yeah, it would really be nice if configs/config locations were even remotely standardized.

[–] SFaulken@kbin.social 3 points 1 year ago

I've been daily driving openSUSE Aeon/Kalpa for the better part of two years now. I don't see any good reason to return to a traditional distribution for a desktop machine. I very much know what I'm doing as a linux user/admin, having been using it for years, and the no-fuss/no-hassle nature of an immutable system is exactly what I want for my workstations. And ultimately my servers.