starryoccultist

  • 0 Posts
  • 16 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle



  • minor issue: it’s podman-compose instead of podman compose. The hyphen feels like a step back because we moved from docker-compose to docker compose. But thT’s not a real issue.

    podman does not autostart containers after boot. You have to manually start them, or write a start script. Or create a systemd unit for each of them.

    I’m also currently migrating all of my self-hosted services from docker to podman. Look into using Quadlet and systemd rather than podman-compose: https://www.redhat.com/sysadmin/quadlet-podman

    Your Quadlet .container files will end up looking very similar to your docker compose files. Podman will automatically generate a systemd service unit for you if you drop the .container file in your user systemd unit directory ($HOME/.config/containers/systemd/) and run systemctl --user daemon-reload. Then starting the container on boot is as simple as systemctl --user enable --now containername.service.

    This will not solve your rootful vs. rootless issues, as others have pointed out, but Quadlet/systemd is nice replacement for the service/container management layer instead of docker-compose/podman-compose






  • starryoccultisttosdfpubnixSome posts not visible
    link
    fedilink
    arrow-up
    6
    ·
    2 years ago

    Your home instance will only start receiving posts from remote communities from the time that the first user subscribes to it onwards. So assuming you are the first person from the SDF.org Lemmy instance to sub to that community, the SDF.org instance will not backfill posts or comments from prior to the time that you subbed. If you know the URL of a specific post or comment, you can force the SDF.org instance to fetch it by plugging the post or comment’s direct URL into the search bar.

    See the Lemmy federation docs


  • It’s a really intriguing concept. One interesting point I saw someone make the other day is that you don’t necessarily need an explicitly immutable distro to achieve the affect. It’s more about your user habits and workflows. If I can’t find an alternative to Silverblue that I like, I’ll probably just go to Debian or Arch and make it “immutable” by not touching the base system at all and running apps with Flatpaks or distrobox containers.



  • I think Bloodborne + The Old Hunters are nearly perfect as their own self-contained thing, so my ideal would be a spiritual successor in a new setting but retaining some of the DNA of Bloodborne. It would be really difficult to replicate what they did with Bloodborne in any sequel or successor; the game was truly lightning in a bottle, like the first Star Wars movie.

    That being said, if there’s going to be a sequel set in the same world, exploring the old Pthumerian civ would be very cool and interesting.