• 0 Posts
  • 7 Comments
Joined 11 months ago
cake
Cake day: November 23rd, 2024

help-circle



  • It’s a little older, so I don’t have an extensive recollection. Things I have saved are the Poettering tweet pointing out their hostname being ‘Wolfsschanze’, doing their own torch march just after Unite the Right Charlottesville happened, and the expected anti-sjw, cultural marxism rhetoric to go along with it.

    It’s a case of no one individual instance being drastic (well, perhaps except for Wolfschanze), but coming together to form a picture which I firmly file into icky-politics.


  • Sure, no argument with that - although I am happy piefed is rising as an alternative.

    I did not intend to claim moral superiority or any absolutes, which is, again, why I just tend to also provide a small disclaimer while recommending that kind of software.

    It’s more about giving a small preface to people I care about should they ever end up intending to contribute to certain projects. I don’t think that’s an unreasonable stance to take. But if you think it is and weren’t just doing a social media zinger let me know.


  • I’m always a little torn on projects like this.

    On the one hand, I know a few people who have hosted tt-rss and the software worked very well for them and their needs.

    On the other hand, software whose maintainers have fascist tendencies, or are at best super edge-lords, and which maintains a culture in the developers and community that’s just super toxic is not something I ever wish to support or be associated with.

    I have similar feelings on the hyperland project, or suckless software. What i have personally settled on is to not touch the software myself, and give a slight disclaimer when recommending it to others.

    I suppose unmaintained can be added to the disclaimer for this one now. At least we have a plethora of very nice alternatives in the rss space with projects like freshrss, miniflux, and nextcloud news.


  • But, how do folks manage this mess?

    I generally find it less of a mess to have everything encapsulated in docker deployments for my server setups. Each application has its own environment (i.e. I can treat each container as its own ‘Linux machine’ which has only the stuff installed that’s important) and they can all be interfaced with through the same cli.

    Is there an analogue to apt update, apt upgrade, systemctl restart, journalctl?

    Strictly speaking docker pull <image>, docker compose up, docker restart <container>, and docker logs <container>. But instead of finding direct equivalents to a package manager or system service supervisor, i would suggest reading up on

    1. the docker command line, with its simple docker run command and the (in the beginning) super important docker ps
    2. The concept of Dockerfiles and what exactly they encapsulate - this will really help understand how docker abstracts from single app messiness
    3. docker-compose to find the equivalent of service supervision in the container space

    Applications like immich are multi-item setups which can be made much easier while maintaining flexibility with docker-compose. In this scenario you switch from worrying about updating individual packages, and instead manage ‘compose files’, i.e. clumps of programs that work together to provide a specific service.

    Once you grok the way compose files make that management easier - since they provide the same isolation and management regardless of any outer environment, you have a plethora of tools that make manual maintenance easy (dockge, portainer,…) or, more often, make manual maintenance less necessary through automation (watchtower, ansible, komodo,…).

    I realise this can be daunting in the beginning but it is the exact use case for never having to think about downloading a new Go binary and setting up a manual unit file again.