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

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

help-circle










  • I’m fairly certain I annoy the people at my bank because I always insist on calling them back at their official number if they ask for any personal information. I don’t fuck around with my bank security. I did however get got a couple of more years ago back when the chrome browser window phishing attack first started and had my Steam account stolen for a solid minute.

    That’s the attack where they simulate a browser window so what you think is a oauth popup is actually just inpage javascript and CSS.






  • 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
    ·
    4 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’m not sure what you mean by “open source compatible”. Do you mean the camera itself can have open source firmware installed, or that it’s compatible with open source NVR software such as Shinobi or ZoneMinder?

    If the former, I know some of the Wyze cameras have that option. Like OpenMiko. There’s all OpenIPC, which does have a list of supported devices.

    If the latter, any camera with RTSP and some sort of API to expose PTZ controls would do. My personal recommendation would be Axis, which makes solid cameras.