6 ms·

I mean... I'm happy he's happy, but for instance, I sign up with a budget webhost, run rsync and my blog is deployed. Super low mental burden. There's no arguin

• taeric 6y ago
  It is mind bending to see how much more complicated than "rsync" deploying a simple static site often gets.
  • kyawzazaw 6y ago
    I just want to write these days so I have been using HEY world. Simple as sending an email!
    • saimiam 6y ago
      Can you tell me a bit more about this? How does it work? Do you have to subscribe to hey.com? What did you like about this approach? Is it a free service? I’m asking because I too made an email->blog post service for myself and I want to see if this is productizable.
      • raihansaputra 6y ago
        Yeah if you have a HEY.com account (paid), you can send an email to world@hey.com and it's published.
        • saimiam 6y ago
          Thanks for the answer. Do you also use this feature to blog?
          • kyawzazaw 6y ago
            Yes, here's mine at https://world.hey.com/daedalus https://world.hey.com/daedalus Very simple. Although I still haven't found out how to embed links into text.
  • Macha 6y ago
    I have ansible so I can install nginx, acme.sh and copy files. Then if my host explodes, it's the same single command to deploy to a fresh host as my existing host.
    • turtlebits 6y ago
      It's just as trivial to spin up a new cluster, and do a kubectl apply -f .
      • Macha 6y ago
        With a managed service sure. If you have an unmanaged host? I'm not sure stuff like microk8s or k3s claim to be production ready.
        • turtlebits 6y ago
          If you have an unmanaged host you just need to install docker and k3s (with a curl command). Two lines in a userdata/init script and you're ready to go. K3s claims to be production ready.
        • nonameiguess 6y ago
          k3s is absolutely production ready. It's intended for IOT and edge devices, but if you want to use it in a data center, it'll work. What you lose is the failover of Kubernetes itself that you get from a proper HA etcd setup where the control plane for your cluster is itself also clustered, but you really don't need that if your entire application is a single node anyway.
          • merb 6y ago
            k3s supports that. in fact rke2 is basically driven by k3s
    • taeric 6y ago
      For a static site, why not just use s3?
  • lawn 6y ago
    And I thought my script wrapping s3cmd was overcomplicating things.
• cyrialize 6y ago
  True. My personal blog is also just super easy to run. I use Jekyll for the blog and Neocities as a host, so all I need to do is: - `jekyll build` to build `_site` - `neocities push _site` to recursively upload modified files in _site
  • kube-system 6y ago
    And on kubernetes you can `docker build [...]` the image and then `kubectl set image [...]` to update the image that kubernetes is using Or, even better, you can just set up CI to do everything on commit/push. For the last static site I deployed, I just tossed Caddy on k8s and set up the git module. I commit, push, hit f5, and my site is already there. There's a ton of ways you can use kubernetes, which is probably part of the adoption problem.
    • joshmanders 6y ago
      Along with this a lot of people fail to also take into consideration flow that is NOT the happy path. With k8s and a proper build system, you can roll back easily if you introduce a bug or something doesn't work. More importantly if your site doesn't start up in any specific way you deploy it, k8s won't even start a new pod. Everything sounds all fine and dandy if all you think about is the happy path.
• dexterchief 6y ago
  I'm happy you're happy, but do you really need all that fancy file syncing/diff/resolution stuff? Wouldn't FTP have been enough? Vim over SSH? Seems like overkill. :P