• 11 Posts
  • 607 Comments
Joined 4 years ago
cake
Cake day: May 31st, 2020

help-circle



  • Ah, yeah, I don’t think there was anything in the app. I guess, they could’ve mentioned it in the changelog, which gets shown in the app by default after an update.

    But yeah, I think we’ll have to excuse a bit of a bumpy ride here. I know, it says “Mozilla” on there now, but to my knowledge, it’s still just the one core dev…






  • Hmm, it’s been a few years since I’ve run Fedora, but that’s an experience also still stuck in my head from that time.

    I always figured, Linux had just gotten better at that, because I switched to a more up-to-date distro afterwards, but in retrospect, it’s not like Fedora is terribly out of date, so maybe that is just a weird configuration on Fedora…








  • I’d say, I’m primarily a very low volume gamer, so I don’t play a lot of games, and if I do, I don’t play them for long. And that certainly makes it easy to look at the news of a game releasing and to think, yeah, that’s probably neat, but if I’m buying another game then it’d be Undertale or Baba Is You or such, and it definitely doesn’t look as neat as those…


  • “Infrastructure as code” is what the strategy is typically called. You use one of the many tools for orchestrating configuration of hosts (Ansible, OpenTofu, Puppet, Saltstack, Chef, etc.). These allow you to provide configuration files and code for setting up your hosts in a central place. This place is typically a Git repo, allowing you to keep track of when which change was made.

    Depending on the tool you use, you trigger applying the configuration on your dev PC, or there’s a hosted CI/CD server which automatically rolls out the changes when a new commit is pushed.


  • For a project called “Potato Peeler”, I’ll put it into a structure like this:

    ~/Projects/Tools/Potato-Peeler/potato-peeler/
    

    Tools/ is just a rough category. Other categories are, for example, Games/ and Music/, because I also do gamedev and composing occasionally.

    Then the capitalized Potato-Peeler/ folder, that’s for me to drop in all kinds of project-related files, which I don’t want to check into the repo.

    And the lower-case potato-peeler/ folder is the repo then. Seeing other people’s structures, maybe I’ll rename that folder to repo/, and if I have multiple relevant repos for the Project, then make it repo-something.

    I also have a folder like ~/Projects/Tools/zzz/ where I’ll move dormant projects. The “zzz” sorts nicely to the bottom of the list.