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

help-circle

  • Lodra@programming.devtoSelfhosted@lemmy.worldBest way to dockerize a static website?
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    4 months ago

    The simplest way is certainly to use a hosted service like GitHub Pages. These make it so easy to create static websites.

    If you’re not flexible on that detail, then I next recommend Go actually. You could write a tiny web server and embed the static files into the app at build time. In the end, you’d have a single binary that acts as a web server and has your content. Super easy to dockerize.

    Things like authentication will complicate the app over time. If you need extra features like this, then I recommend using common tools like nginx as suggested by others.




  • This really depends on the services you’re interested in. If you want something like aws, then no 🙂

    There are plenty of other service providers that do things more ethically. Bitwarden is good, random example in my opinion. The software is e2ee and their service just syncs data between your devices. It’s not really possible for the bitwarden, the company, to read or mishandle your data in a way that matters. Note that this doesn’t apply to the credit card info for paid accounts. Still, this is what I consider “the good guy”.

    So what services are you looking for?


  • Lodra@programming.devtoSelfhosted@lemmy.worldAny love for Kubernetes here?
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    10 months ago

    While you’re probably right overall, there are many good reasons to use k8s. The api provides all sorts of benefits. Kubectl, k9s, and other operational UIs . Good deployment models and tools like argo. Loads of helm charts that are (theoretically) ready to use.

    No, those things aren’t free. There’s a lot of overhead to running k8s.



  • Well I’m also not entirely sure what you’re looking for. But here’s my guess 😅

    None of this stuff should run under the account of a human user. Without docker/compose, I would suggest that you create one account for each service, deploy them to different directories with different permissions. With docker compose, just deploy them all together and run it all under a single service account. Probably name it “docker”. When an admin needs to access, you sudo su - docker and then do stuff.