Hi everyone, You may have noticed a small change on the website. From now on, upvotes work just like on Lemmy - they are equivalent to Mastodon's "favourite." You can boost a post using the button that replaced "favourite." Another change is that you can now rate and boost your own posts. Boosting has a one-time effect - it elevates the post to the top of the "Active" list, adds points used for the "Hot" section, and appears as a boost on other instances.
A language selection dropdown has been added to the footer - thank you all for that!
It seems that the Docker update has also brought significant improvements.
Now, I want to focus on bringing the instance creation instructions to a satisfactory state.
I promise to get back to your questions and comments as soon as possible - there have been quite a few of them. But for now, I need to keep an eye on the queue charts to make sure I don't stumble and accidentally cause problems for other instances ;)
Oh, and here's some good news: my application for Fast Forward has been accepted, and I'll do my best to make it truly thrilling here soon ;p
Meanwhile, I'll be away for a bit, but I'm constantly monitoring reports, the matrix, email, and mentions.
Have a great day!
@ernest Great work!
I haven't take a deeper look to the code. I just read the current version of instance creation instruction, Dockerfile, and docker-compose.yml. There are somethings I don't understand, which you might find useful in improving docker related stuff. (1/2)
@ernest
In the Dockerfile, the kbin-core repository has already been copied to the image. Why we need to mount the repository as volume again with
./:/srv/appin docker-compose.yml? Is it because the front end javascript is built outside the image? (and why those yarn command are not automated in Dockerfile?)The docker-compose.yml has caddy as reserve proxy. Will it be safe if I directly turn it off, and use my own nginx reserve proxy with my own certificate? (2/2)