I'm a big fan of Wireguard. I wrote wg-access-server [1] as an all-in-one wireguard VPN solution. I recently added some docs [2] and support for deploying with Helm. I'd love some feedback on here or on github. Give it a try.
This is awesome news. I’ve been using my self written access server deployed as a docker container at my home for ages now with no problems at all. Wg is a pleasure to use and their apps for iOS and desktop are great. The QR code feature in the mobile app is really good.
I can’t wait for better adoption amongst businesses for corporate VPNs.
Is it though? Hosted k8s clusters make deploying a single app just as simple as heroku or elasticbeanstalk, but you still have the flexibility to deploy more. For a small team it's just as easy to setup a managed k8s cluster as it is any other PaaS - you go though a wizard on GKE or some other provider. And if you apps are simple then you don't need to use the complicated features of k8s itself. 1 deployment and 1 LoadBalanced service is simple enough for most Ruby, Python, C#, Java monolith apps to be off to the races.
I'm not trying to argue that it's a silver bullet but there's a bit of circle jerk over k8s complexity when it's not that hard.
Yes, I quite liked this about Rust's `Result` and `Option` type and using monads in general but I don't think Golang could achieve this pragmatically without generics.
How does this scale once you have multiple developers/teams and an automated CI/CD process in place? Could you elaborate on how to manage this manual step (potentially for multiple environments) when an automated deployment depends on them being done?
Is this a Enterprise edition only feature? From reading it seems this is the case which is a shame because it feels like a pretty basic feature but also really useful to small CE users.
Type errors might not be the biggest issue up-front when writing new frontend code, but refactoring JS becomes really hard as the LOCs grow. Typescript (static typeing in general) really helps with this as you can get instance feedback about how you're changing interfaces between parts of the system.
Another reason i've enjoyed TS is the editor intellisense support. It's really helpful when using a library to get type info in your editor instead of having to google when you forget what a function returns, for example. This is also helpful when you're coming back to code you wrote a long time ago, or a colleague wrote it, and you don't know what particular variables/function arguments/object properties are at a given spot in the code.
I often try to ask 'why' and 'what if' questions. Maybe I just suck at talking to people but they often become defensive and think i'm trying to question their solutions when i'm really trying to understand how their solution works (i'm young).
i opensourced it so that others could see it and perhaps use it for inspiration which this fork seems to be doing :)