kamrani

Fair enough

Appreciate your feedback.

I think in a few years the demand will move from cloud operator role towards cloud/solution architect role.

No one really enjoys from dealing with the infrastructure that should just work. The main added value will be in orchestrating these tools which are easy to set up and building great solutions from them rather than dealing with unnecessary details.

Great question. While some people might actually want to use Dokku for real project, there are fundamental flaws in it.

Firstly, you start with setting up Dokku and maintaining it while the whole idea was that you didn't want to deal with that sort of headache.

The other point is that the UI is very primitive and the UX goals are different from the ones I've followed.

Finally, what's the point to run Dokku when I charge you around the cost of the server you want to run your Dokku on? (That's the starter plan and it costs more for the plans with more advanced - mainly security and compliance related features)

Interesting, never thought about it. Doesn't SES work for you in case I provide that?

Thanks! Absolutely, that's exactly the idea.

AWS offers a lot of flexibility, it's a lot cheaper than PaaS providers like Heroku and even Render and it provides massive discounts specially to startups or if you pay upfront.

However, it's complicated and time consuming and I want to help teams to just focus on building the product rather than dealing with all the headaches of infrastructure set up.

Hi, sure will DM you in a few days.

I'm glad you're interested. I agree that C# has its own templates and CLI, however I'm building on top of the existing tools wherever available.

It means, in some cases my CLI supports things as basic as creating a folder structure (e.g. for GO REST APIs), and in other cases it adds a few missing pieces to the existing tools.

In the next phase, the CLI will simplifies common use-cases such as Database, message queue, sending emails, AWS/Azure related functionalities, etc.

And most importantly, this CLI will be integrated to a platform that simplifies moving your code to cloud, so with a single command you'll host it on AWS/Azure/GCP/DO.

Great questions. Q)"How is this different from the current boilerplate tools" A) This tool will do more than creating the boilerplate. For example, in case of UI frameworks, it'll give you different components based on different design-systems which will be available on Figma.

Also, this tool will act as a superset of all those tools. I'm using the most popular CLI for each language/framework, if there is one available, to keep it as close as possible to developers who're perhaps already using those CLIs. I don't want to change anyones habit, just making people's lives easier.

Q) "Additionally, "deploy to AWS" is somewhat vague. Deploy as a lambda function? Static site? Ec2 instance? With(out) a DB?" A) You'll have different options. As I can detect what options are viable for your project I can give you those options in an interactive session and deploy it based on the scenario you choose.

Yup, that's it

The idea is to have the bare minimum every developer in that particular category have on their system and just help them boost their productivity with a good jump start and hopefully with the upcoming features during the development.

Love the analogy, really love it.

It's just the very beginning of it. I'm adding different languages/frameworks as soon as I can.

Never thought about something like Lisp, but definitely if that's something the community really use, we can definitely support it (at least the community should be able to contribute); it's just a matter of priority.

Hi, appreciate your support.

The goal is to make it really easy to go from idea to URL. So the CLI boosts your speed in kick starting the project and you should be able to deploy it on cloud with a single command.

There will be a platform, that gives you PaaS experience on AWS/Azure/GCP so it speeds up the end to end process.

Thanks.

Definitely. I've taken an iterative approach to supporting languages/frameworks and adding features. Python will be the next language to support.

I start with a minimal/basic support and in later iterations I keep adding features.

Thanks for your support

I just want to make sure people can use it for free if they want but I don't want to give the right to sell.

Then I think it's not what I want.

Fair points. It's not a library and it's actually going to be provided as a SaaS product and as you mentioned I think it's best not to share the critical parts of code. At least that's what I'm doing.

Not always really. Code commit/build/deploy still are some of the worst products in AWS and they're far behind Gitlab which is OSS.

Btw, I'm not really concerned about Amazon particularly, it's a general question about someone taking advantage of few years of work without putting in any effort.

I think I have to use something exactly like the license Sentry is using then. It's just one license and it should be fine I guess if it had protected them.

Also, I'm not concerned about Amazon exactly but it can be any other entity with enough resources to offer my product to their existing user base and definitely with massive marketing budget, etc.

Thanks, sounds like what I need. Not sure if with AGPL still I have to use a dual license approach.

Also it's very true about what happened to elastic search or was about to happen to Sentry.

Thanks it's a good read.

That's exactly what I'm trying to do.

My concern is that a large enterprise like Amazon jumps in and in a few months I see exactly the scenario you describe.

I'll add a contributor agreement right away and it seems a dual license is the way.

I think the last one then.

I want to be able to sell it (exclusively), and anyone should be able to use the open-source version for free if they want (there is a SaaS offering for whoever wants it).

Well, maybe for early adopters? I think I've got something wrong...

And do you think if approach users they'd think we're not ready?

We have built a tool that helps small to medium size companies to run their static websites, functions, dockerized applications and even non-dockerized on cloud in a few minutes. We provide two options:

- to run your applications on our cloud platform like Heroku (but way cheaper)

- or to run your applications on your own cloud platform (we support aws now, and soon we'll support azure, gcp and digitalocean)

You get monitoring, notifications, incident management, and many more integrations out of the box.

We have hobby plans and flat fee subscriptions (extremely low price for early customers).

Are you interested in trying our product? It has a generous free plan (no credit cards required), we can also give you a demo of all the features (no obligations).

Yup, it's just an MVP, will be ready soon. It's built in less than a day as the guys in YC recommend

Nah, not really even close to Heroku's experience