• 0 Posts
  • 1.38K Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle
  • I don’t think there’s anything inherently wrong with the idea of using a GUI, especially for a non-professional who mostly just wants to get into self-hosting. Not everyone has to learn all the ins and outs of every piece of software they run. My sister is one of the least technical people in the world, and she has her own Jellyfin server. It’s not a bad thing that this stuff has become more accessible, and we should encourage that accessibility.

    If, however, you intend to use these tools in a professional environment, then you definitely need to understand what’s happening under the hood and at least be comfortable working in the command line when necessary. I work with Docker professionally, and Dockge is my go to interface, but I can happily maintain any of my systems with nothing but an SSH connection when required. What I love about Dockge is that it makes this parallel approach possible. The reason I moved my organization away from Portainer is precisely because a lot of more advanced command line interactions would outright break the Portainer setup if attempted, whereas Dockge had no such problems.


  • The thing is, those poor design decisions have nothing to do with those features, i claim that every feature could be implemented without “holding the compose files hostage”.

    Yes, this is exactly my point. I think I’ve laid out very clearly how Portainer’s shortcomings are far more than just “It’s not for your use case.”

    Portainer is designed, from the ground up to trap you in an ecosystem. The choices they made aren’t because it’s necessary to do those things that way in order to be a usable Docker GUI. It’s solely because they do not want you to be able to easily move away from their platform once you’re on it.



  • Not the point. If you want to interact with the compose files directly through the command line they’re all squirelled away in a deep nest of folders, and Portainer throws a hissy fit when you touch them. Dockge has no such issues, it’s quite happy for you to switch back and forth between command line and GUI interaction as you see fit.

    It’s both intensely frustrating whenever it comes up as an issue directly, and speaks to a problem with Portainer’s underlying philosophy.

    Dockge was built as a tool to help you; it understands that it’s role is to be useful, and to get the fuck out of the way when its not being useful.

    Portainer was built as a product. It wants to take over your entire environment and make you completely dependent on it. It never wants you to interact with your stacks through any other means and it gets very upset if you do.

    I used Portainer for years, both in my homelab and in production environments. Trust me, I’ve tried to work around its shortcomings, but there’s no good solution to a program like Portainer other than not using it.


  • Please don’t use Portainer.

    • It kidnaps your compose files and stores them all in its own grubby little lair
    • It makes it basically impossible to interact with docker from the command line once it has its claws into your setup
    • It treats console output - like error messages - as an annoyance, showing a brief snippet on the screen for 0.3 seconds before throwing the whole message in the shredder.

    If you want a GUI, Dockge is fantastic. It plays nice with your existing setup, it does a much better job of actually helping out when you’ve screwed up your compose file, it converts run commands to compose files for you, and it gets the fuck out of the way when you decide to ignore it and use the command line anyway, because it respects your choices and understands that it’s here to help your workflow, not to direct your workflow.

    Edit to add: A great partner for Dockge is Dozzle, which gives you a nice unified view for logs and performance data for your stacks.

    I also want to note that both Dockge and Dozzle are primarily designed for homelab environments and home users. If we’re talking professional, large scale usage, especially docker swarms and the like, you really need to get comfortable with the CLI. If you absolutely must have a GUI in an environment like that, Portainer is your only option, but it’s still not one I can recommend.


  • I think you’re seriously underestimating the strength, size and funding of the Israeli military, combined with the significant presence the US has in the area. They’re likely to be quite capable of holding off a full scale assault by an Iranian lead coalition until more forces can be deployed.

    Isreal is a very paranoid, highly militarized state. There is no attack that will be “faster than they can react.” They’re basically on a war footing all the time, and especially now with the recent ratcheting up of tensions.

    Iran has very few strategic or tactical advantages in this situation.






  • Which is ironic given that the previous commenter was extolling how scientific and precise baking is, and how you never have to deal with vague measurements.

    Baking - especially bread - is in fact incredibly fussy. It’s hugely dependent on factors like humidity and temperature, and just what mood the yeast is in that day.

    But if you are struggling with bread recipes that include vague measurements for salt, generally 5g of salt for every 250g of flour should be alright.

    Also avoid bread recipes that measure flour by volume (cups). Look for ones that measure by weight instead. Much more reliable.


  • The answer to “a pinch of salt” is that you “season to taste”. Literally, taste it, then add more if it needs more. Your pinch and my pinch will be different, because you and I will like different amounts of salt.

    And it’s actually nearly impossible to find “a pinch of salt” in a recipe these days. Most recipes will give you exact measures for herbs and spices.


  • Honestly OP, about ten years ago I sucked at cooking too. Then one day I just got excited about being a better cook, and that was enough to make me keep on trying until I did. Since then I’ve managed to help two other people who knew literally nothing about cooking get to the point where they can absolutely wow people with some of their dishes.

    It all comes down to this; learn one meal. That’s it. Just one thing that you can do well. Mac and cheese. Spaghetti bollognaise. Fried chicken. A grilled pork chop with green beans. Garlic bread. Just pick that one thing, and get good at it. Then you pick another thing. And another. And before you know it, you’ll not only have a catalogue of dishes that you can confidently cook, but also dish will have taught you techniques that you’ll find yourself reusing when you learn the next, and so the learning process itself becomes faster and easier. Eventually, you’ll look at a recipe and just immediately think “Oh, right, I know how to do all that. Easy.”

    But how do you get there? I find that recipes are a terrible way to learn to cook. Video content is much more helpful, because a video can break down technique for you. Binging With Babish is so popular because he’s exceptional at this; every video he tries to introduce at least one new technique to his audience. Ethan Chleblowski is also really good at getting into the how and why of cooking, as well as just the what. If you’re vegan or vegetarian Derek Sarno makes excellent content. For baking Ann Reardon’s How To Cook That is wonderful. Joshua Weissman is really fun. Kenji Lopez Alt is an absolute master of breaking down the science of cooking (and also just doling out fun and easy late night recipes). And despite the name and humorous tone, You Suck At Cooking really does offer good cooking ideas.

    Watch a whole lot of this content. Just bounce through videos until you land on a recipe that makes you go “Yeah, I want to try that.” Then, after you’ve had a few cracks at it, start looking up that meal on n YouTube and finding other videos about the same thing. Compare and try out different techniques. Look for where people agree and disagree an try everything until you find something that really works for you. If, try as you might, you just can’t seem to make a dish work, move on to a different one (but only after really giving it a few goes). Sometimes you have to come back to something later, once you have more of your basic technique down.

    Eventually, you will get good at one thing. And then another thing. And another. And as you do that, your confidence will grow exponentially. Soon enough, you’ll feel at home in the kitchen.


  • Also baking is heavily dependent on factors beyond many peoples control, such as the humidity and temperature in your home, or the quality of your oven. Cookies are fine, everyone should take a crack at them, but anything with yeast is a fussy little bitch that will fuck you over just for fun.