• 12 Posts
  • 2.21K Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle


    1. No, you can’t “remove” your local networking interfaces from a container and expect it to use networking, anymore than you can remove the engine from a car, and expect it to drive. Set the default route of that container to some VPN tunnel interface, and you should be fine.
    2. I’m not seeing a link to any config
    3. 1000:1000 is usually the default user that is created for you when you setup a Linux system, so yes it’s reasonable for them to run as your user. It is NOT reasonable to run them as root, which is 0:0. Don’t do that.







  • I get that you’re aiming this at a user base of new folks and all, but I’m super confused to see Nix on there.

    This is kind of…Nix’s entire identity, no?

    One could also make the argument that this supercedes bootstrap tools that each distro has. Kickstart for example.

    I would maybe focus on making helper scripts that do specific things for groups of users, like installing all the steam-* packages for Steam installs and not just steam itself since this is pretty opinionated on how you’re choosing to install things re: native package manager vs Flatpak and such.







  • I think you’re asking the wrong question here. You should be asking “Is my tech stack doing what I need and working for me?”.

    If yes, then just keep doing what you’re doing.

    If not, then figure out what’s wrong, and take steps to fix it.

    Trying to “compete” - as it sounds like you may be trying to do - IS futile. But what are you competing over? Why would you feel the need to compete with the things you hate? That’s not where your battle is, it sounds like.


  • Sorry, ma dude. This is 100% incorrect. Been doing this a long time, and have managed massive numbers of desktop sessions for enterprise end users.

    Lookup dconf. It’s the tool that manages the underlying configuration engine for Gnome specifically.

    Outside of the granularity there, you could also just lock everything to a group and exclude logged in users from that group. That’s a very simplistic way of explaining it, but achieves the exact same thing. You build a base image with only the apps the user needs, set execution to an inclusive group that user belongs to, and everything else to some other groups, and there you go. Dead simple.

    Of course that’s not how you’d do it for an org with thousands of users, but you get the point.



  • For starters: Rails, PHP, and passthrough routing stacks like message handlers and anything that expects socket handling. It’s just not built for that, OR session management for such things if whatever it’s talking to isn’t doing so.

    It seems like you think I’m talking smack about HAProxy, but you don’t understand it’s real origin or strengths and assume it can do anything.

    It can’t. Neither can any of the other services I mentioned.

    Chill out, kid.