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?

  • e569668@fedia.io
    3·
    1 year ago

    I believe you should be able to run it all locally without a hostname. The guides for doing so are here, depending on how you want to:
    https://codeberg.org/Kbin/kbin-core/wiki/Admin-Bare-Metal-Guide
    https://codeberg.org/Kbin/kbin-core/wiki/Admin-Docker-Guide

    Someone just went through this themselves in the matrix kbin development channel so you could also potentially find help there if you’re having issues. One thing that came up during that is https://codeberg.org/Kbin/kbin-core/pulls/132 has a bunch of changes to those docs which might make it easier

  • ryan@the.coolest.zone
    1·
    1 year ago

    My development/testbed instance is hosted on its own Hetzner server via a separate subdomain of my existing domain. It does need to be exposed to the internet to test federation, and it does need a domain to my current understanding (in that I haven’t tried it with just an IP address). Email is a very good analogy, as the original well-known federated web communication tool. :)

    There is a way to install and run kbin via docker, that’s what I use for both my dev and prod setups.

    I would highly recommend familiarizing yourself with the ActivityPub spec to understand what you’re looking at, and try GETting a few comments, threads etc via Postman. ActivityPub, much like email, is peer to peer, account to account. An activity comes from one actor to another. So understanding kbin necessitates understanding things like “a magazine is also an actor” and “the reason threads and microblogs are different is because they have different activity types.”

    Once you’ve got a handle on that, the psql database will make a lot more sense when you explore it, and you can connect all the dots together. Even though I do not have more than a rudimentary grasp on PHP, with the current understanding of ActivityPub and the database I have I’m slowly putting all the pieces together. :)

  • RoundSparrow@kbin.social
    1·
    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.