Responsabilidade

What if you try another interface, like shutdown -P now or poweroff -p?

Well, it is. Is so stable that many of Arch users install Arch once and don’t have to format the computer again in years.

Of course you can’t say that Arch is as stable as Debian, cause it’s not. But it’s totally unfair compare these distros, cause the use cases are completely different.

Don’t use a ruler to measure how loud a sound is.

I called it “stable enough”. For a home user, it’s stable enough. It’s a myth that Arch will break every update or it is unstable. Arch is as unstable or stable as you make it be.

You also can’t setup automatic updates safely

That’s partially true. If you’re trying to run a server, yeah, don’t set any automatic update. If you’re home user, you may do it and you’ll be fine, but be aware of your system.

Arch is easy to maintain and is stable enough. Of course you can make Arch unstable if you do greedy stuff, but if you use like a normal person, it will be fine

It’s using Arch for 5 years now and I never broke my system, for example

I don’t know if I correctly understood but I think that KDE plasma has this functions you need from DisplayFusion. You need to use Virtual Desktops + Activities, both inhetit to KDE

Maybe I didnt undertand correctly, but I think this may do the job for you

deleted by creator

Why are you using that?

    location ~ /\.ht {
        deny all;
    }

You’re denying the access to your root, which is the public/ folder and has the file .htaccess that has

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews -Indexes
    </IfModule>

    RewriteEngine On

    # Handle Authorization Header
    RewriteCond %{HTTP:Authorization} .
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect Trailing Slashes If Not A Folder...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} (.+)/$
    RewriteRule ^ %1 [L,R=301]

    # Send Requests To Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]
</IfModule>

This file handles the income requests and send to the front controller.

I’m not sure, but looks like you’re denying all .htaccess files. Laravel depends on .htaccess to make things work properly

Take a look on Laravel docs - Deployment to make sure your configs are right

And it’s not. SELinux is much more secure, however much more complex. Although AppArmor also do the job, despite being easier to workaround it. But I don’t think this is a good argument against Debian.