HN user

keikubo

12 karma
Posts1
Comments13
View on HN

We are based on Amazon Web Services (ELB + EC2 + nginx + powerdns + apache + FastCGI). I admit the current response time is very slow, but our team members make a lot of effort to improve it.

It may be the different issue, but some node hackers may disagree to use Node.js with Apache + FastCGI. However, it is our challenge to make the node technology available not only to geeks but also to light users who will take advantage of server side javascript.

We'll improve the performance and I welcome any advices!

Hi Andrian. We bring the power of social coding (GitHub) into a cloud hosting platform (fluxflex), and I believe the multi-language support is critical point to achive it. Taking advantage of social knowledge and cllaboratoin with other developers will reduce initial learning curves for trying new technologies, and will amplify the joyful energy instead. Our goal is to let the web application development faster, easier and more amusing.

Now you can install various popular applications with one-click. These applicatoins include Rails, Node.js, Coffee script, Django, Catalyst, Mojolicious, Lokka, Haskell and so on. Because we use GitHub on its backend, you can access to the source code easily, and fork it to start developing your original applications.

On ther other hand, if you have an existing repository on GitHub, you can automate the deployment process by specifying the reposity in a form on fluxflex.

As the result of these collaborations, I believe web applications development will become more pleasant.

You can write a configuration file named .flx and we will run commands according to the description in it. "Lokka on fluxflex" is a greate example for understanding how the configuration and the deployment work on fluxflex. You can read the source code at https://github.com/sowawa/lokka.

Various one-click install applications are hosted on GitHub, and you can fork, merge and push on GitHub as well as just install the application on fluxflex.

Thnaks for your comment.

At first, we are in the process of refine the phrases on the Web with some native English speakers, and will clarify the description soon.

Second, we just use GB instead of MB because we will increase the free quota in future. Current quota is for temporal use to avoid paying too much unexpected infrastructure cost.

Thanks for your advice.