What's the recommended way to set up a development environment for KBin? (kbin.social)

submitted 1 year ago by MoogleMaestro@kbin.social to c/kbinMeta@kbin.social

3 comments fedilink hide all child comments

I haven't been able to find an answer for this, so I'm hoping asking this here would be appropriate.

I'd like to try my hand at some development of Kbin but I don't exactly know how to test a web application of this scale. Obviously, the roadblock for me is understanding how to develop and test features without having a dedicated domain name -- as my understanding is that federated services heavily rely on the use of a domain name. This also would imply that the server has to be exposed to the internet, much like development of a email client.

But obviously I must be missing something here. Is there any recommended guidelines for setting up a development environment for Kbin? Ideally, a containerized approach via Docker or Podman would be ideal as I wouldn't want to muck with my host system. Additionally, is it possible to use hostnames in order to simulate and test federation capabilities? Lastly, are there any thorough reads (blogs or forum posts) that go in depth with developing federated web applications and how the development process differs from standard webdev?

you are viewing a single comment's thread
view the rest of the comments

[-] RoundSparrow@kbin.social 1 points 1 year ago

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.

this post was submitted on 06 Sep 2023

4 points (100.0% liked)

/kbin meta

2 readers

1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago