denibertovic

I've been using this (different snippet though) for about 6 years now. It's great. "Poor man's CLI" is what I call my makefiles. :D Example: https://github.com/denibertovic/makefiles/blob/master/bare.m...

Thanks. I'm pretty sure it's a little bit of all 3 of those. And possibly other things you didn't list.

Thanks. I can't help myself and still feel like there's something there... but I don't know how to work it. I mean if there was nothing there I wouldn't be hearing about new projects doing something similar. The difference is that they seem super complex and do a lot more. The idea behind my project was to be simple and perhaps be able to serve a subset of the market. But perhaps that was a mistake.

I suppose. Given that it checks the AWS/GCP api on a schedule not sure how effective that would be.

Then again, it's not like the hosting is costing that much. Actually I currently run it on a machine with lost of resources that is used for other things as well...so technically I could keep running it forever. That is to say the cost isn't the main driver for shutting it down. It's more a psychological burden at this point where I'm thinking "ok I tried, it didn't work time to move on".

I don't have any users. A few tried it out but did no continue using it.

Honestly I can keep it running forever since it's running on a dedicated machine that has lots of resources and that I use for other projects as well. So it's not like it's costing me to keep it up. The burden is purely mentally (I just don't want to keep thinking about it anymore...I tried...I failed...right?)

I experimented with pricing a lot. The one you see now is the latest iteration. The idea was you pay 1$ per EC2 instance per month. So kind of like insurance right? The trick is that if you have say 60 instances you're paying 100$ still because the tier allows 100 instances to be monitored. I wanted the expense to be fixed every month because I've gotten feedback from folks that companies don't like variable cost per month for infrastructure...and it's already an issue that AWS is costing them a different amount each month....so it would be a hard sell to get to them to pay me a variable amount as well (small fish and all that).

Initially I didn't have a free tier at all. I only added it later as a desperate attempt to attract users. That's why historically I never gotten around to setting up a register flow without an invite link. :/ I don't know if 50 is the right number for the free tier but it definitely needs to be a larger number since companies/individuals that I target have a larger amount of servers. The ones that only have a handful don't really need this tool at all since they already mostly know all of their servers by name (so to speak). It's the whole "cattle vs pets" discussion. Anyway, that's where the limit to 50 comes from.

Thanks for the link btw. I read a bunch of patio11's posts but I don't think I've read this one.

Apparently the links are clickable only in comments:

[1] https://ledger.initeq.net/

[2] https://twitter.com/denibertovic/status/1466408868276314114

Also how can I verify that intermediate certificate? Is that a base64 encoded string?

Where does it say specifically on that page you linked that only Mozilla can use these apis?

How do I verify that this is signed by Mozilla?

Interesting app. I'm currently using todo.txt [1] and am quite happy with it. It's not really a note taking app (although I could use it that way) but rather a todo app and it uses a pure text file and syncs with dropbox nicely. I use an Android app as well [2].

There's a bunch of plugins for it but I haven't used any of them yet.

[1] http://todotxt.org/ [2]: https://play.google.com/store/apps/details?id=nl.mpcjanssen....

When you say hiring is never a problem? Does that mean you're hiring remote as well?

Are you hiring remote folks?

And they conveniently don't mention Linux support.... Sigh..

Also interesting thing to note is how everybody came down on keybase FS because the sync is on-demand. Most people citing dropbox and things like "if it was a viable option dropbox would do it and not have full sync". Well now... :D

I suspect the 700MB dependency is Haskell Platform. Which you don't need and is not considered a good way to install Haskell. Just GHC and Cabal (package manager, sort of ) are nowhere near there. Or even better, use Stack. See how large the binaries are.

I've learned Haskell at university too. That doesn't prove anything though does it? At the time I've found it useless and plain wrong ... it is much later that I learned to appreciate it and value what it brings to the table...much much later.

How does FP, most notably Haskell, not encourage polymorphism? This statement is just plain wrong.

Type classes are the definition of polymorphism. And you can write very generic, abstract, polymorphic code using these constructs. It's not any languages fault if you write your code expecting only concrete types. By this standard it's Javas fault if the developer isn't using generics. No it's not it's the developers fault. The mechanisms are there. Use them.

Not sure what you mean. scrolling works just fine for me. I use mosh and screen together though.

Is there an open source version of either something like Cinema or what MSR did? I'd really like to be able to post-process some of my gopro footage.

I like the new homepage. One little nit-pick, I actually find the quicksort example a better candidate (instead of the sieve one). I think it highlights the expressiveness of the language a lot, and everybody implemented quicksort in some other language at one point, so they can compare.

I don't think it's possible. At least with celery. The only way I've was able to do this is with more Queues (and workers).

Fair point. I agree with this.

It is true that each worker will use up a connection. Not sure how heavy weight it is, depends on your setup and use-case I guess.

Tnx for the link. nice read. There is a difference though, in using something as "a Queue" and using something as an AMQP implementation when it's clearly not that.

"Tornado only blocks if you do something silly. It's event based, and can keep hundreds of connections open and waiting for it's async response event before actioning/responding the open connection." - Yes pure tornado based apps are probably fine if you know what you are doing.

"Wow, overkill much? Polling is bad, and is exactly the kind of bad solution that a lot of these libraries are in place to prevent developers from needing to do." - Polling is not bad if you have a good use case. You just cannot do non-blocking stuff with Django for instance, or it's very very hard and tricky. Websockets also limit you with the number of connections you can have open at once.

A background task is just something that's computed outside of the standard http request/response process. So it's asynchronous in the sense that the result will be computed sometime in the future, but you don't care when.

Distributed just means that you can have your task processing spread out across multiple machines.

A specific example would be, let's say, after your user registers on your website for the first time you wan't to get a list of all his facebook/twitter friends. This action will take a long time and is not vital to the whole registration/login process so you set a task to do that later, and let the user proceed to the site and not make him look at the spinner the whole time, and when the friend list becomes available it will show up on the website (on his profile or whatever). Makes sense?

Oh absolutely values before objects. I said "serializing" more in the sense that pickle is always used for storing the arguments into the queue (or whatever the default serializer).

It always depends on your use-case but generally you want your application to behave correctly, which means it has to have correct/fresh data...you can't sacrifice correctness because of an inability to scale your database.

Feel free to ping me if you have any questions. I will do my best and try and answer them if I can.

Awesome, tnx for the tip! :)

Indeed. I use Ansible myself.

At the point where all the other "normal" mechanisms monitoring storing the job on the queue have failed I would suppose I have a far more greater problem on that system. Personally I would not use flags for jobs types, I would monitor them with flower. Also, we need to keep in mind that it's one thing retrying sending a job to the queue and a whole other thing retrying a job already on the queue that failed for some reason. In my experience so far there a mechanisms that deal with both of these issues effectively and none involved using the webapps database for this.