psviderski

7 ms·

1. 61.▲
   by psviderski 1y ago

   What's your approach with getting users for your OSS product?
2. 62.▲
   by psviderski 1y ago

   Thanks! I'm more than happy to catch up to discuss the challenges. Feel free to reach out to me on twitter @psviderski or email 'me at psviderski.name'
3. 63.▲
   by psviderski 1y ago

   This is a great approach which resonates with me a lot. It's really frustrating that there is no simple way to run a multi-host Docker/Podman (Docker Swarm is abandonware since 2019 unfortunately). However, in my opinion K8s has t
4. 64.▲
   by psviderski 1y ago

   The only problem is Docker Swarm is essentially abandonware after Docker was acquired by Mirantis in 2019. Core features still work but there is a ton of open issues and PRs which are ignored. It's fine if it works but no one cares if
5. 65.▲
   by psviderski 1y ago

   Generally speaking, redundancy/availability could also be achieved through replication rather than automatic rescheduling, where you deploy multiple replicas of the service across multiple machines. If one of them dies, the other one s
6. 66.▲
   by psviderski 1y ago

   Working on Uncloud [1] — open source tool for self-hosting containerised apps across multiple machines. You can combine cloud VMs and on-premises to create hybrid compute environments, e.g. for cost optimisation or data privacy. While Kuber
7. 67.▲
   Uncloud: A Fresh Take on Workload Orchestration(cedwards.xyz)

   2 points by psviderski 2y ago|0 comments
8. 68.▲
   by psviderski 2y ago

   What’s your use case for custom certs? Why are the automatically issued Let’s Encrypt ones not enough?
9. 69.▲
   by psviderski 2y ago

   I'm continuing to develop Uncloud [1] — an open source tool for deploying and managing containerised applications across multiple Docker hosts. Includes WireGuard overlay network, ingress with automatic HTTPS, and simple Docker-like CL
10. 70.▲
    by psviderski 2y ago

    BTW, is there something specific that caught your attention?
11. 71.▲
    by psviderski 2y ago

    Thanks for the encouragement! I'm working on it steadily and feedback like yours helps keep me motivated
12. 72.▲
    by psviderski 2y ago

    Yep agreed, but on the other hand do you really need HA for them when you're perhaps a single user? I wonder, what motivated you to migrate to single-node K8s from Compose for your self-hosted setup?
13. 73.▲
    by psviderski 2y ago

    I agree there is no one-size-fits-all for data replication. Currently Uncloud doesn't handle volume replication. Moreover it doesn't support regular Docker volumes yet, only mounting a host path. The reason is I didn't have t
14. 74.▲
    Show HN: Uncloud – Uncomplicated container orchestration without control plane(github.com)

    30 points by psviderski 2y ago|8 comments
15. 75.▲
    by psviderski 2y ago

    Oh this is going to be a beast. It depends on what you're trying to achieve though. If you're doing this primarily to learn the kube landscape then it's a great way to play around with these tools in a homelab.
16. 76.▲
    by psviderski 2y ago

    As far as I know, Coolify is great for single-server PaaS or multi-servers that work independently. Uncloud focuses on distributed multi-server HA deployments (which is what is usually preferred for production). It allows you to spread work
17. 77.▲
    by psviderski 2y ago

    Honestly, I went with Docker simply because I'm much more familiar with it and its networking stack made integrating with WireGuard overlay straightforward. Podman support could come later but Docker's popularity and API stability
18. 78.▲
    by psviderski 2y ago

    Working on Uncloud[1][2] — think Fly.io but self-hosted. A lightweight Docker clustering tool for running web apps on your own servers (from cloud VMs to bare metal) with no control plane to maintain. Perfect for teams who want cloud-like d