• 0 Posts
  • 185 Comments
Joined 1 year ago
cake
Cake day: June 28th, 2023

help-circle

  • Yeha, but you can ask for help without taking a shit on the effort of thousands of engineers.

    I doubt OP thought, ‘I’m going to take a shit on thousands of engineers.’ It’s okay to not know what to do, including asking for help. If they don’t know what to do with “error 2,” they’re obviously lost. This unwelcoming attitude to newcomers is a big problem, and in my opinion, it’s probably best not to contribute to it.

    You can rephrase what you’re saying and provide better help to someone who’s completely lost in a much more polite and informative way. It’s better for everyone.





  • Synthead@lemmy.worldtoNo Stupid Questions@lemmy.worldcan chromeos be hacked??
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    10 months ago

    Exactly. Just be responsible and don’t do anything dumb with your security. Do the typical stuff right like using a password manager and updating your software often. With your programming, don’t skip ssl validation, don’t have unauthenticated connections that matter, don’t shell out, etc. On your local system, use permissions correctly, keep a local firewall, and all that good stuff. You should be fine, but it’s never 100%.










  • I think Docker is a tool, and it depends on how you implement said tool. You can use Docker in ways that make your infra more complicated, less efficient, and more bloated with little benefit, if not a loss of benefits. You can also use it in a way that promotes high uptime, fail-overs, responsible upgrades, etc. Just “Docker” as-is does not solve problems or introduce problems. It’s how you use it.

    Lots of people see Docker as the “just buy a Mac” of infra. It doesn’t make all your issues magically go away. Me, personally, I have a good understanding of what my OS is doing, and what software generally needs to run well. So for personal stuff where downtime for upgrades means that I, myself, can’t use a service while it’s upgrading, I don’t see much benefit for Docker. I’m happy to solve problems if I run into them, also.

    However, in high-uptime environments, I would probably set up a k8s environment with heavy use of Docker. I’d implement integration tests with new images and ensure that regressions aren’t being introduced as things go out with a CI/CD pipeline. I’d leverage k8s to do A-B upgrades for zero downtime deploys, and depending on my needs, I might use an elastic stack.

    So personally, my use of Docker would be for responsible shipping and deploys. Docker or not, I still have an underlying Linux OS to solve problems for; they’re just housed inside a container. It could be argued that you could use a first-party upstream Docker image for less friction, but in my experience, I eventually want to tweak things, and I would rather roll my own images.

    For SoC boards, resources are already at a premium, so I prefer to run on metal for most of my personal services. I understand that we have very large SoC boards that we can use now, but I still like to take a simpler, minimalist approach with little bloat. Plus, it’s easier to keep track of things with systemd services and logs anyway, since it uniformly works the way it should.

    Just my $0.02. I know plenty of folks would think differently, and I encourage that. Just do what gives you the most success in the end 👍