• 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • gornius@lemmy.worldtoSelfhosted@lemmy.worldShould I move to Docker?
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    1
    ·
    11 months ago

    Learn it first.

    I almost exclusively use it with my own Dockerfiles, which gives me the same flexibility I would have by just using VM, with all the benefits of being containerized and reproducible. The exceptions are images of utility stuff, like databases, reverse proxy (I use caddy btw) etc.

    Without docker, hosting everything was a mess. After a month I would forget about important things I did, and if I had to do that again, I would need to basically relearn what I found out then.

    If you write a Dockerfile, every configuration you did is either reflected by the bash command or adding files from the project directory to the image. You can just look at the Dockerfile and see all the configurations made to base Debian image.

    Additionally with docker-compose you can use multiple containers per project with proper networking and DNS resolution between containers by their service names. Quite useful if your project sets up a few different services that communicate with each other.

    Thanks to that it’s trivial to host multiple projects using for example different PHP versions for each of them.

    And I haven’t even mentioned yet the best thing about docker - if you’re a developer, you can be sure that the app will run exactly the same on your machine and on the server. You can have development versions of images that extend the production image by using Dockerfile stages. You can develop a dev version with full debug/tooling support and then use a clean prod image on the server.



  • gornius@lemmy.worldtoPrivacy@lemmy.mlPlease, do not use Brave.
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    1 year ago
    1. Chromium has tons of eyes on it, because it’s codebase for many other projects, such as Electron and any chromium based browser.

    2. Web integrity wasn’t discovered through chromium source code, but it was openly proposed by Google on separate Github repo, dedicated solely for that proposal.

    3. There are many shortcuts in your thinking that just the code being open makes it trustworthy. Every PowerShell malware technically has its code open, because it’s a script. But you wouldn’t open a random script from the internet, without checking what it does, yet you don’t apply the same logic to Brave. If you don’t check the source code yourself, you either need to trust an author, or third parties that “checked” the code.

    4. In addition to that, you’re probably using compiled binary, which means at this point you can throw that source code out from window, because at this point you can’t be sure compiled binary == source code.

    5. Due to the enormous amount of code, it’s really easy to obfuscate malicious behavior. At the scale of the browser it’s more efficient tracking outbound packets that program sends than examine source code.


  • gornius@lemmy.worldtoPrivacy@lemmy.mlPlease, do not use Brave.
    link
    fedilink
    arrow-up
    50
    arrow-down
    5
    ·
    1 year ago

    Brave behaving like Win XP era browser with gazillion toolbars installed, with a pinch of crypto and crypto promoting ads should be a giant red flag.

    FOSS =/= trusted by default. Why are there so many FOSS evangelists, but such a damn tiny part of them are programmers, let alone programmers able to examine a source code behind such a giant codebase as web browser?

    I use Vivaldi, at least their business model is clear, and developer is kind of trusted, and not crypto scammer and homophobe.