4 ms·

Nice to see a Python/Django implementation of ActivityPub. Having a nice, lean implementation of ActivityPub that I can customize to my liking is the only thing

by mg 4y ago

Nice to see a Python/Django implementation of ActivityPub. Having a nice, lean implementation of ActivityPub that I can customize to my liking is the only thing that keeps me from using the Fediverse more regularly. So I am watching the space closely. What I find a bit unfortunate about Takahe is the coupling with Docker. An even leaner ActivityPub implementation seems to be MicroBlogPub. I have not yet managed to set it up though. Anybody interested in collaborating on a MicroBlogPub install script that turns a fresh Ubuntu installation (or container) into a running MicroBlogPub instance?

simonw 4y ago
It's not coupled with Docker. Docker is purely one suggested way of running it - it's a classic Django app so running it directly on Ubuntu should work the same as any other Django application.
- mg 4y ago
  Great! When I saw "Prerequisites: Something that can run Docker/OCI images" in the documentation, my interpretation was that containers are needed. It also says "You need to run at least two copies of the Docker image". Maybe you want to change the wording a bit. I would also collaborate on writing a setup script for Takahe then! I really like to write a setup script instead of following manual installation guides. So for every software I try, my first step is to write a script that turns a fresh Debian installation into a running instance. (MicroBlogPub needs Python 3.10 which is not in Debian stable, so I would use Ubuntu)
  - mg 4y ago
    Hmm.. does not look good for the non-Docker setup. The developer replied with "I am deliberately avoiding offering a non-Docker install path" and closed the issue: https://github.com/jointakahe/takahe/issues/44 https://github.com/jointakahe/takahe/issues/44 Creating a non-Docker fork would then probably be an uphill battle.
    - simonw 4y ago
      Full quote: > So, I am deliberately avoiding offering a non-Docker install path that is supported right now as it leads to a lot of support burden with different OS package versions and the like! That doesn't mean you can't write and share a script for people who want to install it without Docker. It means that he doesn't want to take responsibility for non-Docker installation scripts as part of the official documentation (yet), because if he did that he'd be on the hook to keep researching and updating those scripts in the future.
    - manfre 4y ago
      The non docker install path for almost any project is to run the individual scripts from the dockerfile, plus adding the CMD to systemd or similar.
rodgerd 4y ago
> What I find a bit unfortunate about Takahe is the coupling with Docker. While I don't love it, it's very understandable for a single-dev application. Anything else involves blizzards of questions and bugs filed against people using their disto version of Django vs their downloaded version of Django and the many versions of distros and the many conventions for Python environments and... Exhausting.

by mg 4y ago

simonw 4y ago

It's not coupled with Docker. Docker is purely one suggested way of running it - it's a classic Django app so running it directly on Ubuntu should work the same as any other Django application.

mg 4y ago
Great! When I saw "Prerequisites: Something that can run Docker/OCI images" in the documentation, my interpretation was that containers are needed. It also says "You need to run at least two copies of the Docker image". Maybe you want to change the wording a bit. I would also collaborate on writing a setup script for Takahe then! I really like to write a setup script instead of following manual installation guides. So for every software I try, my first step is to write a script that turns a fresh Debian installation into a running instance. (MicroBlogPub needs Python 3.10 which is not in Debian stable, so I would use Ubuntu)
- mg 4y ago
  Hmm.. does not look good for the non-Docker setup. The developer replied with "I am deliberately avoiding offering a non-Docker install path" and closed the issue: https://github.com/jointakahe/takahe/issues/44 https://github.com/jointakahe/takahe/issues/44 Creating a non-Docker fork would then probably be an uphill battle.
  - simonw 4y ago
    Full quote: > So, I am deliberately avoiding offering a non-Docker install path that is supported right now as it leads to a lot of support burden with different OS package versions and the like! That doesn't mean you can't write and share a script for people who want to install it without Docker. It means that he doesn't want to take responsibility for non-Docker installation scripts as part of the official documentation (yet), because if he did that he'd be on the hook to keep researching and updating those scripts in the future.
  - manfre 4y ago
    The non docker install path for almost any project is to run the individual scripts from the dockerfile, plus adding the CMD to systemd or similar.

rodgerd 4y ago

> What I find a bit unfortunate about Takahe is the coupling with Docker. While I don't love it, it's very understandable for a single-dev application. Anything else involves blizzards of questions and bugs filed against people using their disto version of Django vs their downloaded version of Django and the many versions of distros and the many conventions for Python environments and... Exhausting.