I take my shitposts very seriously.

  • 3 Posts
  • 506 Comments
Joined 2 years ago
cake
Cake day: June 24th, 2023

help-circle




  • are rolling release distros stable enough

    I’ve been using Arch (or some flavor of it) for several years, and I’ve never had any serious issues that I didn’t cause myself. The thing that might catch you with your pants down is if a dependency introduces a change that breaks another application, but catastrophic failures are fairly rare, as long as you’re willing to learn how to maintain your system.

    is it possible/easy to roll back to a previous version

    Yes. The application is called Timeshift, and it’s specifically designed to back up the system files to a separate partition. If your root filesystem is btrfs, it can also manage filesystem-level snapshots that you can roll back if you bugger the system.


  • I was there with KSP from the early days. Squad was not in the video game business, they were a billboard advertisement company. The lead dev HarvesteR started it as a passion project. It found success with the alpha and full release in 2015.

    Then in 2017 Take-Two bought the rights to the game. Squad kept working on the original, but development of the sequel was handed off to Star Theory with Private Division publishing. The game was delayed, then development was moved to a new studio, Intercept Games, which was owned by Take-Two. They also poached a third of Star Theory’s personnel, which resulted in the studio’s death. They fucked around for a few years, released the early access version, then sold Private Division, closed Intercept Games, and abandoned the game.

    In short: corporate interests. KSP2’s failure had nothing to do with KSP or its developers.



  • I’ve never used the AIO image. I’ve heard it’s weird. This is my compose file for the community image:

    compose.yaml
    volumes:
      db:
    
    services:
      db:
        image: mariadb:10.6
        restart: always
        command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
        volumes:
          - db:/var/lib/mysql
        secrets:
          - mysql_root_password
          - mysql_nextcloud_password
        environment:
          - MYSQL_ROOT_PASSWORD_FILE=/run/secrets/mysql_root_password
          - MYSQL_PASSWORD_FILE=/run/secrets/mysql_nextcloud_password
          - MYSQL_DATABASE=nextcloud
          - MYSQL_USER=nextcloud
    
      nextcloud:
        image: nextcloud
        restart: always
        ports:
          - 8080:80
        depends_on:
          - db
        links:
          - db
        volumes:
          - /var/www/html:/var/www/html
          - /srv/data:/srv/data
        secrets:
          - mysql_nextcloud_password
        environment:
          - MYSQL_PASSWORD_FILE=/run/secrets/mysql_nextcloud_password
          - MYSQL_DATABASE=nextcloud
          - MYSQL_USER=nextcloud
          - MYSQL_HOST=db
    
    secrets:
      mysql_root_password:
        file: ./secrets/mysql_root_password.txt
      mysql_nextcloud_password:
        file: ./secrets/mysql_nextcloud_password.txt
    

    You can access it on port 8080 and perform the initial setup manually. For the database server address, use the db hostname. You’ll have to use a reverse proxy for HTTPS.

    You could also try OpenCloud, which is a Go rewrite of ownCloud.












  • No. I’m so bloody fed up with AI “search” solutions that return everything on the fucking planet except what I want. Text search has been a solved problem for a decade. All I want out of a search engine is to be deterministic, stable, and reliable, and to look in titles, descriptions, and keywords. Vibe processing is completely unnecessary and will only create issues.

    If you really want to iNnoVAte, then consider creating an index with transcripts and summaries that users can search by keywords.