[jcwilde]

It's a bit disingenuous to list a bunch of languages (along with custom logo icons) that are _presumably_ supported by nanobox, only to force visitors to drill-down one-by-one to discover that only one out of three have any support at all, and the others are just placeholders saying "please contribute".

On the positive side, I guess it is better odds than a state lottery.

[sanderson1]

We (I work for Nanobox) listed all the languages we hope to support mainly as an invitation to collaborate. We admittedly do not specialize in all programming languages. Engines are open-source and those who do specialize are invited to create engines for each language. We'll even create the engine for you. We just need to know what the engine should look for and how the environment needs to be configured.

[thawkins]

The php part has almost no content. Im also concerned that the custom builds are not documented, its easy to build a dev env with half a dozen rpm files thrown in, but when it comes to getting all your custom extensions etc added thats a bit harder and we cannot judge that as of right now.

[sanderson1]

There's currently only one php engine, other than the generic php engine, listed on https://engines.nanobox.io/languages/php. However if you look at the generic php engine docs, there's a lot of content: https://engines.nanobox.io/releases/3b30f069-bb16-4f1a-9c36-.... And even more in the Advance config options included in the nanobox-engine-php repo: https://github.com/nanobox-io/nanobox-engine-php/blob/master...

[carapace]

Hey, I typically browse with javascript turned off. Your site is a blank page for me.

[eljimmy]

Perhaps if they dropped the opacity on the yet-to-be supported language icons? With that said, though I'm not a huge fan of the tool itself, I do really like the site design. Great job, it definitely kept me looking around and interested in reading further.