• 6 Posts
  • 141 Comments
Joined 1 year ago
cake
Cake day: January 5th, 2024

help-circle




  • Create a systemd user unit that waits for the network-online.target.

    A script something like:

    [Unit]
    Description=Startup script
    Requires=network-online.target
    After=network-online.target
    
    [Service]
    Type=oneshot # either simple or oneshot, but sounds like oneshot
    ExecStart=/home/<user>/script.sh
    RemainAfterExit=yes #if oneshot, otherwise no
    
    [install]
    WantedBy=default.target
    

    Edit the template according to your needs and dump it into ~/.local/share/systemd/user/<unit>.service and enable it with systemctl --user enable --now <unit>





  • I had written about this in their Discord in a thread:

    using this shim script I made, do the following:

    1. Install Raft with Proton 9.0-# prefix
    2. Place the shim file into the game directory
    3. Mark the shim as executable
    4. Set Steam launch options to: WINEDLLOVERRIDES="winhttp.dll=n,b" ./shim %command%
    5. Launch Raft once
    6. Place RMLLauncher.exe into Raft game directory
    7. Look for a plaintext target file that should be created in the raft directory
    8. Copy the location of the RMLLauncher.exe (exact folder and filename) (right click > Copy Location in KDE / Steam Deck desktop mode)
    9. Paste this location into the target file and save
    10. Launch Raft
    11. Go through RMLLauncher first-time steps
    12. Press Play
    13. Stop the game and add mods into Raft mods folder
    14. Launch the game and load the mods in-game
    15. Play Raft modded through Proton

    (Instructions adapted from both mine and Discord user YumiChi’s)

    This method doesn’t require custom installations, messing with bottles, nor wine runtimes other than Proton.



  • If you’re running an email server for more than a handful of persistent users, I’d probably agree. However, there are self-host solutions that do a decent job of being ‘all-in-one’ (MailU, Mailcow, Docker-Mailserver) that can help perform a lot of input filtering.

    If your small org just needs automation emails (summaries, password resets), it’s definitely feasible to do actually, as long as you have port 25 available in addition to 465, 587 and you can assign PTR records on reverse DNS. Optionally you should use a common TLD for your domain as it will be less likely to be flagged via SpamAssassin. MXToolbox and Mail-Tester together offer free services to help test the reliability of your email functionality.


  • I’m currently going through a similar situation at the moment (OPNSense firewall, Traefik reverse proxy). For my solution, I’m going to be trial running the Crowdsec bouncer as a Traefik middleware, but that shouldn’t discourage you from using Fail2Ban.

    Fail2Ban: you set policies (or use presets) to tempban IPs that match certain heuristic or basic checks.

    Crowdsec Bouncer: does fail2ban checks if allowed. Sends anonymous bad behavior reports to their servers and will also ban/captcha check IPs that are found in the aggregate list of current bad actors. Claims to be able to perform more advanced behavior checks and blacklists locally.

    If you can help it, I don’t necessarily recommend having OPNSense apply the firewall rules via API access from your server. It is technically a vulnerability vector unless you can only allow for creating a certain subset of deny rules. The solution you choose probably shouldn’t be allowed to create allow rules on WAN for instance. In most cases, let the reverse proxy perform the traffic filtering if possible.




  • For desktop/workstation users: the simple answer is just use the flatpak from Flathub or from some other source if you need a user package that doesn’t align to the ethos of your chosen distro. In most cases desktop Linux users have gone beyond self-packaging for specific library versions and just use a separate set of common libraries to power application needs beyond the out of box experience of any given distro. It’s part of why immutable distros are starting to take off and make more sense for desktop/workstation use-cases.

    For servers, it’s in the nature to become part of the technical debt you are expected to maintain, and isn’t unique among RHEL, OpenSUSE Leap, Debian, Ubuntu, or any other flavor of distro being utilized.



  • Ocis/OpenCloud can integrate with Collabora, OnlyOffice but don’t currently have things like CalDAV, CardDAV, E2EE, Forms, Kanban boards, or other extensible features installable as plugins in Nextcloud.

    If you desire a snappy and responsive cloud storage experience and don’t particularly need those things integrated into your cloud storage service, then Ocis or OpenCloud might be something to look into.




  • Under what means? The target is public sector and the OS to replace (Windows 10, Windows 11) would be a relatively compatible release target. Fedora is a competent leading edge (Wayland, Pipewire, BTRFS) distro that runs as a 6 month point release. I wouldn’t see many reasons to not go with Fedora Workstation as a base unless going for an immutable base or a different core distro (OpenSUSE or Debian mainly).

    EDIT: Missed that this is going to be immutabe, so it is likely being based on Fedora Kinoite, meaning there really aren’t many alternatives besides OpenSUSE’s offerings.








OSZAR »