Nice. Software developer, gamer, occasionally 3d printing, coffee lover.

  • 0 Posts
  • 47 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle



  • So far I’ve helped my team of 5 get on them. Some other teams are starting as well. We’ve got Windows, Linux, and Mac OSX that developers are running on their work machine (for now), and the only container specific issue we ever encounter is port conflicts, which are well documented with easy to change environment variables to control.

    The only real caveat right now is we have a bunch of micro services, and so their supporting services (redis, mariadb, etc.) end up running multiple times, so their is some performance loss from that. But they’re all designed to be independent, only talking to each other via their API, so the approach works.


  • Zikeji@programming.devtoProgrammer Humor@programming.devWorks on my machine
    link
    fedilink
    English
    arrow-up
    52
    arrow-down
    4
    ·
    3 months ago

    If this is your take your exposure has been pretty limited. While I agree some devs take it to the extreme, Docker is not a cop out. It (and similar containerization platforms) are invaluable tools.

    Using devcontainers (Docker containers in the IDE, basically) I’m able to get my team developing in a consistent environment in mere minutes, without needing to bother IT.

    Using Docker orchestration I’m able to do a lot in prod, such as automatic scaling, continuous deployment with automated testing, and in worst case near instantaneous reverts to a previously good state.

    And that’s just how I use it as a dev.

    As self hosting enthusiast I can deploy new OSS projects without stepping through a lengthy install guide listing various obscure requirements, and if I did want to skip the container (which I’ve only done a few things) I can simply read the Dockerfile to figure out what I need to do instead of hoping the install guide covers all the bases.

    And if I need to migrate to a new host? A few DNS updates and SCP/rsync later and I’m done.







  • I really like the way my current company handles things. Aside from annual raises that take effect July 1st (currently waiting for approval, but if that happens after July 1st the raises are retroactive to the first), we have open bars (free drinks) every other month, company wide lunch events a few times a month, other general events (had a Juneteenth and Pride event this month). Oh, and all these events are paid time (you still have to hit your KPIs though).

    A fairly well stocked kitchen (you could make your own lunch if you wanted to), coffee and espresso machines, sparkling water / flavored water one as well, snacks, the whole deal. Yes it’s not perfect but I’ve been happy so far.


  • I’ve also had no negative experience with VPNs and Discord. This being said, I see two potential factors.

    Accessing an account from a different IP and then changing the email on that account from that different IP can look like the account got hacked.

    And the specific VPN being used could play a role (I’m not asking you to reveal that) - if the VPN is being used by bad actors, their IP ranges might be flagged as well.

    Considering the problem with stolen accounts being used to send spam to their friends and the servers they’re in, I can see why there would be automated logic to rate limit actions. The only real issue I see here is the appeal / support process just not being there, going by your other message about a lack of success appealing.









  • The Dockerfile is essentially the instructions for deploying from scratch. Sure, they most likely only exist for one distro but adapting isn’t a huge chore.

    You can also clone the repo and build the container yourself. If you want to update say, log4j, and then attempt to build it, that’s still entirely possible and easier than from scratch considering the build environment is consistent.