purvis's comments

Your story sounds so familiar, someone could read what you wrote above and think it's me.. though I like to think of myself as a generalist rather than "fullstack". I tend to believe "fullstack" is a marketing term for acquiring slave labor. You're right though, it's required at this point for smaller startups.

> I wonder if I could ever possibly get into that fight

I wonder this too. I've been using AWS for 4+ years at my day job(s). The main pain point for almost all users, including myself is the cost. I think a product/tool that helps companies save on cloud costs would be invaluable. The difficulty is convincing crusty old ops people that the product is something worth trying.

Anyway, after my current employer runs out of money, I'm going to do a startup of some sort. While one of my many idea was like the one we outlined above, I'm actually starting to shy away from the infra/op verticals lately.

My email's in my profile, if you ever want to bounce ideas.

It's parallel because AWS Lambda is inherently parallel? Or are you referring to within JavaScript?

> Terraform is basically this tool, but I want an even easier interface, terraform still feels somewhat too specific to me -- I don't want to even have to write config or specify some "aws" adapter that will make my config work on some provider. I want instant, multi-cloud (possibly) heroku, using only the network, hard-drive-space, ram, and lxc "primitives".

This sounds very similar to some ideas I've been stewing on over the past few months. One of them being a multi-cloud terraform-like tool which abstracts away the low level details of which provider an instance is provisioned onto (whichever is currently cheapest). It could also automatically determine how firewall/security groups/networking should be configured.

If you happen to create two instances in two different providers that need to communicate privately over say port 443, the security groups would be updated automatically to account for this, bridging the two providers.

One major thing to consider in doing this is the bandwidth. If you look at the fine print in these providers, the outgoing bandwidth is where they really get you. So if your backup server is in a different provider than your database, you might see some hefty data transfer fees while performing a daily backup.

Just curious, what's your background? Are you an infrastructure type, or are you a general developer who just wants a tool like you've described? Sometimes I can't tell if this is something people really want or if I've just drank too much of the infrastructure automation koolaid.

I've recently installed Enpass and I'm currently in the process of evaluating it. I really like the idea so far. My main concern is that they're not charging enough and wonder if the business model is sustainable.

I've been doing something similar to your everydaycheck app, but manually using google sheets for about a year now. Works great for me too. Your app looks pretty neat!

Does it get much interest from others, or are you the main user?

The main thing is how you are able to offer unlimited disk, when anyone can start uploading data? Some users might upload very large amounts of innocent data, others might simply abuse it as a sort of data backup system. More nefarious users might even try to distribute malware.

Do you plan to curate the free plans? If not, how will you prevent abuse? (thinking in terms of both the service and its users)

How do you keep track? Individual wallets or do you keep them on exchanges?

My initial concern was an aggressive server timeout on nginx/haproxy. I think the defaults should be long enough, but it's entirely possible to have something lower than 20 seconds. (and the app developer might not even be aware of this)

I have no reason to think it's unacceptable, was just curious. Interesting project!

I'm not too familiar with ruby/rails, but does this mean the HTTP request just sits open for up to 20 seconds? Is this common/acceptable practice?

    # user is given 20 seconds to approve the request
    20.times{
      sleep 1
      sltoken = REDIS.get("sl:#{state}")
      break if sltoken
    }

https://github.com/homakov/cobased/blob/master/app/controlle...

> I think I'd recommend it highly over Terraform for production provisioning.

I'm curious why you recommend this? I'd argue the opposite. With the declarative nature of Terraform, you can know exactly which part of your infrastructure is going to change before you actually apply it. With Ansible, this information is a bit more opaque. You basically just run the playbook and pray it goes as planned and things haven't drifted too much.