Yep. Our 128 GB hypervisor wasn't enough. We redirected traffic to a static HTML prototype, so - at least - you guys have a chance to see the design and planned features. https://demo.virtkick.io/

another thing: all the add-on links redirect to the same DNS add-on

Oh, forgot to actually add something there. To give you a better understanding, it'll work the same way as on Heroku.

thanks, I'll be checking the project out for sure

Not at this point. We're focusing on features now. However, installing an alpha is a matter of 4 commands, give it a try: https://github.com/virtkick/virtkick-starter#virtkick-take-c...

Not at this point (we mount an ISO as CD), but we've got it planned: https://github.com/virtkick/virtkick/issues/6

Perfect! I wanted to host my own DO type thing for personal projects and I tried "webvirtmgr" which has a nice control panel for libvirt, but the creator insists that ssh key injection is out of the scope of his project. I'm glad to see this happening!

You may be surprised that VirtKick wraps WebVirtMgr and uses it as a JSON API for libvirt. :-) This is a temporary solution but does the job - it allowed us to start real quick with features that users care about, instead of harnessing libvirt. (Of course, SSH key injection is in a scope of our project! https://github.com/virtkick/virtkick/issues/6)

Ah, I didn't see that before. So without SSH key injection, what's the current primary method of gaining access to VMS created from cloud images that have no password & ssh key? I'm eager to start using it to host a throwaway jenkins server locally. Do you manually edit in ssh key/password or is there some tool to use?

Thanks for your comment. UI comes first as every user will hit it. API comes next. We planned DigitalOcean-compatible API altogether with a CLI. Looks like we removed this from our website by mistake (will get it back real quick), but it's listed in our IGG campaign: https://www.indiegogo.com/projects/virtkick-take-cloud-back

That sounds like a good approach; reimplementing an existing API like EC2 or DO makes it easier to integrate your software with tools like Vagrant and Terraform.

Exactly right, we value existing tools - that's what makes DO so strong. :)

We don't intend to sell modified proprietary versions. In fact, we planned to re-release it under MIT. Just see on the bottom: "Get excited: (...), MIT..." http://goo.gl/w64Ic5 from https://www.indiegogo.com/projects/virtkick-take-cloud-back We'd just want to get funded, so we can work on it without worrying about other things.

Flynn, Deis, Heroku are PaaS - they are focused on applications.

VirtKick is like DigitalOcean or Linode - they are focused on machines (and containers, that you think of as machines). You install it on your Linux desktop (for localhost hacking), or home or dedicated server (for something more).

Will try to express it a little bit better. Thanks for your feedback.

Our intention is that you share code back to the project if you modified it and added some new great features. :) If I'm not wrong, it only applies to the modified source code, and not the data/machines that you work with. http://stackoverflow.com/a/18406382/504845

AGPL means that if you modify VirtKick itself, you have to contribute these modifications back to the project. GPL does not enforce this for software run on a back end.

likely because it could be a hosted application. If he were to choose the GPL then someone could make modifications and host them as a competitive advantage without sharing the modifications to their users.

Excactly right - plus on remote hypervisors too.

External monitoring integration, and off-site status page, will be actual features of VirtKick. Think of VirtKick is a 1-click installable panel that you can use both on your desktop and as a VPS provider. Instead of paid features, we want it to be forever free - instead, we aim to be crowdfunded. https://www.indiegogo.com/projects/virtkick-take-cloud-back

> Excactly right - plus on remote hypervisors too.

Things get crazy here (in a good way). You could create federation where you allow remote hypervisor management from a central authority (your app). #ArchiveTeam needs their VM running for the latest web property shutdown? Here, have access to my overpowered home router to run a few tiny VMs to help the cause.

Knocked it out of the park here guys (and/or gals)! Awesome job.

(co-founder here) we try to not get ahead of ourselves, working on the basics first but it's sometimes nice to think big as well and you have some interesting ideas sir, thanks!

It just sounded too good to be true. I'll definitely contribute.

I didn't spot your question. The best way would be to contribute. :) We currently have virtkick-starter, a bunch of scripts that set everything up. You could try it out on Guix and improve if needed. https://github.com/virtkick/virtkick-starter

>The best way would be to contribute. :)

Of course, I was just wondering where a ticket could be created so that it's on the record as a feature request.

>We currently have virtkick-starter, a bunch of scripts that set everything up.

Perfect. I'll have a look. Thanks!

Edit: I think we have a misunderstanding. I would like to use VirtKick to provision Guix VMs, not just install VirtKick on Guix.

Oh, that's relatively easy at the moment. Put your distro in these two files. ISO will be autodownloaded by `virtkick-starter` script, and the distro will appear on VM create screen. It'll be configurable in the settings in a month, of course. http://goo.gl/u1LKwi http://goo.gl/j1j80f

Sorry for that. The hypervisor died, which results in errors like this. We use Bugsnag so we've got all the stacktraces - we'll handle distasters. :)