oranki

  • 4 Posts
  • 93 Comments
Joined 2 years ago
cake
Cake day: June 5th, 2023

help-circle
  • If something like Ansible is too much, you could list the packages as a bash array in a file

    pkgs=(
    vim
    bash-completion
    ...
    )
    

    Source the file

    source pkgs.txt
    

    Then install them

    dnf install ${pkgs[@]}
    

    This expands to dnf install vim bash-completion ...

    As for listing the installed packages,

    dnf repoquery --userinstalled --queryformat '%{name}\n'
    

    The list includes all packages not installed as dependencies, so it’s not quite perfect but might be close enough to what you need.

    The array expansion workaround should work for other package managers too, as long as they take the list of packages as whitespace-separated arguments.







  • orankitoLinux@lemmy.mlDistro for a new user
    link
    fedilink
    arrow-up
    9
    ·
    1 month ago

    Another vote for Aurora.

    Universal Blue in general has been really solid, I remember one time in the last year or two when there’s been any need for manual intervention. And that came with a notification after boot, with a link to instructions that were all copy-pastable as-is to the terminal.


  • My biased opinion is that most people run Nextcloud on an underpowered platform, and/or they install and enable every possible addon. Many also skip some important configurations.

    If you run NC on a bit more powerful machine, like a used USFF PC, with a good link to it, the experience is better than e.g. OneDrive.

    Another thing is, people say “Nextcloud does too much”, but a default installation really doesn’t do much more than files. If you add every imaginable app, sure it slows down and gets buggy. Disable everything you don’t need, and the experience gets much better. You can disable even the built-in Photos app if you don’t need it.

    Not saying NC is a speed daemon, but it really is OK. The desktop and mobile clients don’t get enough love, that’s true.

    I’m talking about the “bare metal” installation or the community Apache/FPM container images. AIO seems to be a hot mess, and does just about everything a container shouldn’t be doing, but that’s just my opinion.




  • orankiOPtoSuomiSuomalainen Nextcloud-palvelu
    link
    fedilink
    suomi
    arrow-up
    5
    ·
    2 months ago

    Hyvä pointti! Maksuvaihtoehtoja on tarkoitus kyllä lisätä, kun/jos käyttäjämäärä kasvaa, mutta korttimaksunvälittäjät on pikkusummilla aika kalliita. Toistaiseksi perinteinen lasku on kyllä vaikuttanut enemmänkin toivotulta, ei tarvitse miettiä mihin korttitietoja syöttää.

    Sen verran korjaan väärinkäsitystä, että ensimmäisessä laskussa on 30pv maksuaikaa, joka on samalla ilmainen kokeilujakso. Seuraavissa sitten normaali 14pv.





  • Keep at it! The learning curve is not a straight line, just like with any skill. You’ll see fast progress, just to be followed by a long plateau of no progress or even feel you’re getting worse. And then you notice possibly big improvement again. And again.

    Don’t worry about following sheets/chords initially. If chords are not in your muscle memory, you’re basically doing three complex tasks simultaneously, reading, figuring out chords and fingering chords. I’d try to memorize one or two simple pieces first, to get the chords under your belt. Start simple and stay patient, it’ll take time.

    Don’t forget the rhythm. Play on top of recordings. You can be pretty liberal with the harmonics, but if you keep a steady beat it’ll probably still sound good.


  • orankitoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    12
    ·
    6 months ago

    There’s occasionally something buggy, but the last time I ran Windows there were a lot of bugs too. They’re just abstracted away, which Linux DEs don’t do at all.

    For me, it’s about choosing the bugs that bug me less. If Windows is working better for you, just run Windows. Internet points are not worth much.



  • orankitoSelfhosted@lemmy.worldWhy docker
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 year ago

    Portability is the key for me, because I tend to switch things around a lot. Containers generally isolate the persistent data from the runtime really well.

    Docker is not the only, or even the best way IMO to run containers. If I was providing services for customers, I would definetly build most container images daily in some automated way. Well, I do it already for quite a few.

    The mess is only a mess if you don’t really understand what you’re doing, same goes for traditional services.



  • There was a good blog post about the real cost of storage, but I can’t find it now.

    The gist was that to store 1TB of data somewhat reliably, you probably need at least:

    • mirrored main storage 2TB
    • frequent/local backup space, also at least mirrored disks 2TB + more if using a versioned backup system
    • remote / cold storage backup space about the same as the frequent backups

    Which amounts to something like 6TB of disk for 1TB of actual data. In real life you’d probably use some other level of RAID, at least for larger amounts so it’s perhaps not as harsh, and compression can reduce the required backup space too.

    I have around 130G of data in Nextcloud, and the off-site borg repo for it is about 180G. Then there’s local backups on a mirrored HDD, with the ZFS snapshots that are not yet pruned that’s maybe 200G of raw disk space. So 130G becomes 510G in my setup.