• 0 Posts
  • 9 Comments
Joined 4 years ago
cake
Cake day: February 26th, 2021

help-circle


  • I like the Kobo options a lot, I have a device from them that was the Kobo Aura HD from Ebay that was $50 dollars in great condition. Kobo has better support for loading whatever you want on it without any annoying issues and it is running linux under the hood and has a lot of expand-ability because of it. These days I use a kindle paperwhite 4 and honestly, it just isn’t as well thought out. It is waterproof & has a higher resolution display but I found the Kobo OS was faster & the device with buttons had a much better design overall. So, I wish I had gone for an up to date Kobo alternative when I upgraded. So, go Kobo, don’t look back, & get second hand if you want to save some $$$.


  • BioMyth@lemmy.mltoLinux@lemmy.mlThe Terminal Question
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 month ago

    I have determined that foot is best for me personally, like alacritty and a couple others, it is very barebones. No tabs or anything like that without tmux. But it doesn’t rely on GPU acceleration and is just as fast (or faster) than my experience using GPU accelerated terminals. Easy to configure and since it doesn’t have the GPU requirements it works on old hardware like a dream. Only possible issue is that it is wayland only but since that is all I like to use it is perfect.

    I find a lot like ghostty and wezterm try to include too many features. All I need a terminal emulator to be is a terminal emulator. But then a lot of these then add tabs, build in multiplexers & more and it is more bloated than I like a simple utility to be. Additionally, I don’t need native tabs as a lot I do in the terminal uses SSH so it is easier just to use tmux/zilji and not have to manage it as much.





  • Yes Yes I did, sorry! Collabora CODE server configuration in Caddy.

    office.DOMAIN {
            @collabora {
                    path /browser
                    path /browser/*
                    path /hosting/discovery
                    path /hosting/capabilities
                    path /loleaflet/*
                    path /lool/*
                    path /cool/*
            }
            @local-ip {
                    remote_ip private_ranges
            }
            reverse_proxy @collabora https://nextcloud-office:9980/ {
                    transport http {
                            tls_insecure_skip_verify
                    }
            }
            reverse_proxy @local-ip nextcloud-office:9980 {
                    transport http {
                            tls_insecure_skip_verify
                    }
            }
    }
    

    Nextcloud section, may look different from yours I use the FPM image but it should be similar, enough. There are also some limitations on the urls based on local vs public access but that is an attempt at hardening rather than necessary configurations.

    nextcloud.DOMAIN {
            root * /var/www/html
    
            file_server
    
            php_fastcgi nextcloud:9000
    
            header {
                    Strict-Transport-Security max-age=31536000;
            }
    
            @phpFiles {
                    path_regexp phpfile ^/(remote|public|cron|core/ajax/update|status|ocs/v1|ocs/v2)\.php
            }
    
            rewrite @phpFiles {http.regexp.phpfile.0}
    
            redir /.well-known/carddav /remote.php/dav 301
            redir /.well-known/caldav /remote.php/dav 301
    
            @local-ip {
                    not remote_ip private_ranges
                    path /settings/admin
                    path /settings/admin/*
                    path /settings/users
                    path /settings/users/*
                    path /settings/apps
                    path /settings/apps/*
            }
            #respond @local-ip 404
    
            @forbidden {
                    path /.htaccess
                    path /data/*
                    path /config/*
                    path /db_structure
                    path /.xml
                    path /README
                    path /3rdparty/*
                    path /lib/*
                    path /templates/*
                    path /occ
                    path /console.php
            }
            respond @forbidden 404
    }
    

    Then in nextcloud you just point it to the CODE server domain above & you even have tls securing the communication layer.