Core components... like operating systems and engines... this was the whole reason people open sourced in the first place. You start getting it in millions of devices and it is too much power for closed-source closed-license. The GPU drivers and WiFi drivers are often the ones who pave the paths away from open source.
RoundSparrow
joined 1 year ago
Can you reword your second question? 'force searching communities' - not sure why you would want to force or automate a search.
You said this back on July 2, how is it months later?
Although I've found one area that Lemmy to kbin doesn't seem to work when bringing in older content when a new vote is done.
Instance: StarTrek.website Lemmy. comment thread: https://startrek.website/comment/2051539
The copy on kbin.social does not seem to load the thread that starts with user @jet
https://kbin.social/m/[email protected]/t/404007/Favorite-sci-fi-film-thats-not-Star-Trek/oldest
Not sure what is going on under the hood where those won't copy into kbin.
Why are comment threads no longer indented further than 2 indentations?
That seems to be the behavior of 'classic view'. Change to 'tree view'?
Testing 1..2...B
This is a reply, now 1..2...B 3
Testing, 1..2..3
Testing 1..2...B
Testing, 1..2
Did you figure this out?
The bare install is pretty complicated. The docker install isn't that bad following the directions if you are on Ubuntu 22.04. https://codeberg.org/Kbin/kbin-core/wiki/Admin-Docker-Guide
I did it yesterday and it was a bit confusing which passwords to set, the directions have you edit files and kind of just says "change the passwords"... but they are all in docker-compose.override.yml file - if you start there it's a little more clear.
I couldn't get it to start right on Ubuntu 22.04 and I tried deleting everything and starting over and kept running into the same problem. The database password wasn't set.
docker compose up
without the "-d" at the end will show you output where I saw the password wasn't right for the database. It was set the same in both files, not sure why it was wrong. I eventually issued a command directly to the database to set the password and that fixed the problem.
docker compose exec -T db psql -U kbin -c "ALTER USER kbin WITH PASSWORD 'mypassword';"
Then it all started up fine. I also figured out how to get the database on a different port than default because I normally use PosgreSQL 16 for development and kbin expects 13 in the install. So I wanted to tell kbin to use a different port. I can share that if anyone wants.
view more: next ›
lemmy.world has removed a lot of kbin.social content: https://lemmy.world/post/5289864