Oops, I didn't know about this one. Thanks for the heads up.
It's very difficult to find a CLI name that not already taken these days...
4,626 karma · joined April 13, 2013
Email: jje.levy@gmail.com
Twitter: https://twitter.com/jeremy_levy
Github: https://github.com/jeremylevy
It's very difficult to find a CLI name that not already taken these days...
Yes, port forwarding works as usual.
At the time of writing, the ressources are directly created on your cloud account when you run the start command.
Each cloud provider has an extensive documentation that describe the ressources created. (As an example, you could see the documentation for the AWS provider here: https://github.com/recode-sh/aws-cloud-provider).
Given that this project is 100% community-driven, you could open an issue with this feature proposal. All features are implemented once they receive a significant amount of upvotes (>= 10 currently).
It's free, open-source, you could generate a complete infrastructure in seconds, you could manage multiple environments and sandboxes for team work.
Maybe the landing page is not very clear?
[1] https://raw.githubusercontent.com/stackplanet/sourcestack/ma...
What do you think of: "Like Terraform but with the user-friendliness of Heroku" ?
Pricing is something that we've thinking about for a while.
What's your opinion? How much are you willing to pay?
Pricing is something that we've thinking about for a while.
What's your opinion? How much are you willing to pay?
We have started on Medium for the audience but we'll move on your own domain.
The "friend" links:
https://medium.com/revolv2/creating-and-deploying-a-symfony-...
https://medium.com/revolv2/deploying-a-symfony-4-5-applicati...
https://medium.com/revolv2/deploying-a-laravel-7-application...
https://medium.com/revolv2/deploying-a-laravel-7-application...
It's a first alpha release. We're listening to feedback. Billing is not implemented yet.
Pricing is something that we've thinking about for a while.
We also have written a blog post about that: https://medium.com/revolv2/im-building-revolv-to-automate-cl...
What's your opinion? How much are you willing to pay?
Honestly, I've created Revolv for my own needs, as a "full-stack" developer.
I've often found myself wanting something like this: "A Terraform with Heroku-like features".
We've planned to target users that have low to medium cloud experience, so we need to show clearly how cloud architecture creation is easier by using Revolv.
The pricing is something we've been thinking about for a while. Currently, I don't have enough data to make a decision.
It's very difficult because it's not something that have been done yet.
Your GitHub repo looks super useful! Thanks! Thanks! Thanks!
At the time of writing, when you "eject" an architecture, we remove all the "user-friendly" features that we've added.
So you have a fully-working architecture in your own cloud provider account. Like the one you could have been created using Terraform.
We've thought of adding an "export" feature to export all the Terraform/Ansible/Packer... files.
We've created an application that you could use to test the architecture: https://github.com/getrevolv/revolv-docker-architecture-test
We also have written many blog posts that explain how to deploy the most famous frameworks:
We'll add more details.
The price part is something we’ve been thinking about for a while.
There are many possibilities:
- Taking a fee as a percentage of your cloud provider bill for each architecture
- A free plan for the architectures created without the user-friendly features and a premium one?
- A monthly subscription? Per developer? Per architecture?
What do you think?
In the meantime, you could read our introductory blog post:
https://medium.com/revolv2/im-building-revolv-to-automate-cl...
Hope that helps!
I'm so sorry that you need to authorize access to your email to check it out, you could read our blog post instead:
https://medium.com/revolv2/im-building-revolv-to-automate-cl...
It's a first alpha release. I will make sure that we will do better in the future.
--
"How to price?" is something we’ve been thinking about for a while.
There are many possibilities:
- Taking a fee as a percentage of your cloud provider bill for each architecture
- A free plan for the architectures created without the user-friendly features and a premium one?
- A monthly subscription? Per developer? Per architecture?
What do you think?
https://medium.com/revolv2/im-building-revolv-to-automate-cl...
Hope that helps!
It's a first release, so some features are missing.
I've written a blog post that explain in details what Revolv is and why we've build that:
https://medium.com/revolv2/im-building-revolv-to-automate-cl...
Hope that helps!
It's exactly what we've started to do: targeting startups in incubators.
DevOps people in early-stage startups are not very common, so it's seems safe to say that a Devops-as-a-service may be useful for them.
When you say "'a la carte' consultancy", do you mean with a one-shot payment?
Do you think that the "user-friendly" features (deployment monitoring/rollback, CI on all branches, health monitoring...), that you can't have with Terraform only, are useful enough to ask for a recurring one?
We've released an alpha version, with only one architecture, some days ago.
If you want to learn more, I've written a blog post: https://medium.com/revolv2/im-building-revolv-to-automate-cl...
A "catalog" of architectures that you could use to create a complete cloud architecture on your AWS, GCP or Azure account in less than one minute.
For example, you could create a docker-based architecture with CI/CD, auto-scaling, zero downtime deployment, SSL, load-balancing, high availability and MongoDB in less than one minute in your own AWS account.
Like Terraform with the user-friendliness of Heroku.
[0] Previous discussion: https://news.ycombinator.com/item?id=23742097
[1] Direct link: https://getrevolv.com
Yes! I used Terraform because it was the tool I know best but Pulumi seems very elegant.
I didn't know Juju, I'll try it out!
> people who have been working on infrastructure long enough know that there's really only a handful of useful architectures that solve 90% of problems
I totally agree with you on that point.
Also, given that architectures are created on your own cloud provider account you could easily add the missing parts.