thomasbacklund

8 ms·

1. 1.▲
   by thomasbacklund 5y ago

   I am still curious. As a FB software engineer you can probably work at any company you want to, so one must assume you want to work at Meta. And why is this? Serious question here, please respond.
2. 2.▲
   by thomasbacklund 5y ago

   https://en.wikipedia.org/wiki/Criticism_of_Facebook
3. 3.▲
   Show HN: pocket-sockets is a small TCP/WebSockets lib written in TypeScript(github.com)

   3 points by thomasbacklund 5y ago|1 comments
4. 4.▲
   by thomasbacklund 5y ago

   I made this nice little client/server socket lib which has the same interface both for TCP sockets and WebSockets. Free to use, MIT licensed. You all know that browsers require WebSockets but when doing server to server communication r
5. 5.▲
   by thomasbacklund 5y ago

   Sure :) follow me as @bashlund on twitter but also star the repo on github https://github.com/simplenetes-io/simplenetes
6. 6.▲
   by thomasbacklund 5y ago

   Thanks for asking :) Writing this much Bash is quite straining because there is a lot of typing, but it is also liberating in the sense of coding very close to the OS (utils). Also, most of it is not written in Bash, it's written in Po
7. 7.▲
   by thomasbacklund 5y ago

   Indeed, the goal has to keep the number of moving parts down as much as possible so it can be easy to understand the full cluster and how to troubleshoot it. But of course, it still requires knowledge about the architecture to do so.
8. 8.▲
   by thomasbacklund 5y ago

   Thanks, We use haproxy pods for inbound traffic, they perform TLS termination and simply pass the traffic over to a local proxy pod. The haproxy pod (and all other pods) communicate with each other over this local proxy service which is run
9. 9.▲
   by thomasbacklund 5y ago

   I have really enjoyed using Podman and will keep using it. I have found it be to stable (running on CentOS) for our production stuff. Shameless plug: We built Simplenetes[1] around Podman (a simpler alternative to Kubernetes, but written in
10. 10.▲
    by thomasbacklund 5y ago

    I like the detailed questions :) The line count is a rough (overestimate) summoning the source of the three projects involved, simplenetes, simplenetesd and podc, and it also includes comments and blank lines. The compiled output pulls in s
11. 11.▲
    by thomasbacklund 5y ago

    You are looking at the `./release/sns` file, which is the "compiled" release, it's like looking at the .exe (404 kb isn't that bad for an ".exe") The source files involved are smaller [1]. [1] https:
12. 12.▲
    by thomasbacklund 5y ago

    Thanks for taking the time l0b0! A lot of good points. Coding in shell sure is a challenge, I try to avoid bashims where I can, that's why most scripts are .sh not .bash, since they run also with dash/ash (that's why preferri
13. 13.▲
    by thomasbacklund 5y ago

    Thanks for sharing, I'll have a peek :) Heroku is ACE
14. 14.▲
    by thomasbacklund 5y ago

    Thank you :)
15. 15.▲
    by thomasbacklund 5y ago

    Thank you aabhay for a nice comment. Seems like my click-baity title brought out some strong feelings :) I do actually like Kubernetes. I recommend it to clients, I assess candidates who are to work with it, but I do really think it is a Be
16. 16.▲
    by thomasbacklund 5y ago

    If you want something simpler and use podman you can try `podc` [1] which compiles a pod yaml spec into a single executable shell script with a nice managagement CLI api to it. [1] https://github.com/simplenetes-io/podc
17. 17.▲
    by thomasbacklund 5y ago

    Thanks!! We do use it in production, it is however fresh from the keyb so giving it some time before putting sensitive stuff in there. About the state, it's perfectly doable, but requires some more Ops than k8s and isn't as flexib
18. 18.▲
    by thomasbacklund 5y ago

    No, don't build the next Netflix on Simplenetes. However, if you are just dealing with a three node cluster (Yes I know many of you are running tri-cycles with k8s stickers on it) then maybe it can be fine for many applications to not
19. 19.▲
    by thomasbacklund 5y ago

    Oh geez.. Hehe, thank you for pointing that out facepalm
20. 20.▲
    by thomasbacklund 5y ago

    Haha :) Well, the learning has been great I can confirm that. My script-fu is on a whole new level now, it was already quite up there after creating Space.sh [1] Waste of time... Well... Let's not think too much about that. I'm at
21. 21.▲
    by thomasbacklund 5y ago

    Thanks :) The real use case is super simple clusters, which could be just 1 node, no etcd, no API (SSH managed), no iptables. Simplenetes is not a living breathing thing which auto heals it self, it's a deterministic approach where you
22. 22.▲
    by thomasbacklund 5y ago

    Simplenetes does support state, no sweat. But it can't pull a disk out of the cloud for you, there is some traditional Ops involved.
23. 23.▲
    by thomasbacklund 5y ago

    Thanks! We just moved Space.sh from GitLab to GitHub (hurts in my heart, but yeah community is on GitHub). Also we are lousy at promoting our stuff, maybe April 1st is not the best day to do this either...
24. 24.▲
    by thomasbacklund 5y ago

    Thank you for noticing! :) Yeah, this represent a few months of full time work.
25. 25.▲
    by thomasbacklund 5y ago

    This is why Simplenetes is built with Space.sh [1], a tool to build shell script applications. About the tests, can't disagree with you, they will come. [1] https://github.com/space-sh/space
26. 26.▲
    by thomasbacklund 5y ago

    As long as you have multiple replicas of the pods they keep serving traffic.
27. 27.▲
    Show HN: Simplenetes – I replaced Kubernetes with 17k lines of shell script(github.com)

    296 points by thomasbacklund 5y ago|148 comments
28. 28.▲
    by thomasbacklund 6y ago

    Ok, I though it was to catch CTRL-c :) trap EXIT, does work for me in ash/dash/bash, though, when just letting the code flow exit with and without errors. Not sure your use case, but I can for sure concur that traps are very painf
29. 29.▲
    by thomasbacklund 6y ago

    Indeed, it's such a messy job coding for shell.. Comes with a lot trial and error. The above will work as (tested in ash/dash/bash): #!/usr/bin/env sh trap "echo exiting" INT sleep 1h But t
30. 30.▲
    by thomasbacklund 6y ago

    Yeah, I agree.. I was listening to the Command Line Heroes podcast the other day, about Bash. First version was stored on tape . So it has some legacy, hehe. Already then the requirement was to be backwards compatible with sh, so yeah, c