• 0 Posts
  • 32 Comments
Joined 2 years ago
cake
Cake day: September 29th, 2023

help-circle







  • I declare war on this hill!

    • Peak windows was Windows 7 in both design and Function. It was pinnacle User Experience of a traditional OS before Microsoft started chasing fads, (Touchscreens in Windows 8, Cloud integration in Windows 10, and now AI bullshit in Windows 11)
    • No opinion on macOS. My only complaint is that its not linux.
    • Instead of Flatpak I would replace that with AppImages. At least with Flatpak I get some semblance of the SW Integrating with my DE and a semblance of a package manager. AppImages I feel like are like rolling the dice on how much effort the dev put into it.

  • Disclaimer: If you want to explore window managers then go ham! Linux is all about exploration.

    Now, If you think the grass might be greener on a different desktop manager then stick with gnome. By no means am I saying Gnome is the best, but its more of a situation where it will devolve into the quirks you know vs the quirks you don’t know situation.

    Personal Antidote, I started with Gnome and used Gnome for years. Got curious and started jumping around I tried KDE, I3W, XFCE, Pure X, Etc. There were things I liked about each one of them but the quirks of each deviating from my expectations coming from gnome was too much and I ended up sticking with gnome.

    That being said, out of necessity due to system constraints I run XFCE when I need a light weight DE. A close second in that realm is LXDE But I don’t like its default aesthetic nor do I feel like customizing it since I do most of my computing in a terminal.






  • Are you talking about an ERP system like SAP? If so it’s all about data collection of business operations. Sure you make some no brainer decisions to do things that are practical but it always devolves into “how much did this improve the bottom line?” You start to get data on what business has the highest margins in sales and what products are proving to be a PITA to the bottom line due to customer support eating through labor.

    spreadsheets are good but you start hitting walls when the company expands. Suddenly Purchasing managers are making entries to a file, but simultaneously works in production are changing the same file to reflect what they consumed in production. You then start auditing things and don’t know what the QTY row numbers mean. Is that actual inventory? Is that a mix of inventory on order? does this reflect what the production consumed today? if so when?

    It gets messy without the right tools when the company scales.


  • Trimatrix@lemmy.worldtoLinux@lemmy.mlDistro for a new user
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    2 months ago

    The embedded IoT crowd would like to refute your claim that there are no operating systems that you can install and forget.

    The collective would like to stress that any operating system can be installed and forgotten. Please note, that usefulness and security may be impacted.

    /s

    Also, to be technical there is CollapseOS which is an install once and forget sort of thing.





  • Use tailscale for host nodes, use tailscale docker container in a compose stack with an app that you sidecar to. That way that app is on your tailnet as if it is its own computer. Use tailscale serve for reverse proxying support of the apps. Then, setup a vps node (I use linodes $5 node) with tailscale and configure that to be your DMZ into your tailnet.

    For DMZ, use Caddy, UFW, and fail2ban. Also take advantage of ACLs in the Tailscale admin console to only have the VPS able to route traffic to specific apps you want to expose. My current project is to work in Authelia into this setup so a user logs into one exposed app and is able to traverse to other exposed apps through header / token authentication.

    Oh also, segment the tailnet using different authentication keys. Each host node should have its own key, all the apps on a host node should have a shared key, and all public facing clients should have a common shared key. That way in case of compromise you can revoke the affected keys without bringing down your network.