5 ms·
To save everybody some time, here is a list of the runtimes and frameworks actually supported by nanobox: - ruby 1.9, 2.0, 2.1, 2.2 / jruby 1.6, 1.7, 9.0 -
by gmisra 11y ago
To save everybody some time, here is a list of the runtimes and frameworks actually supported by nanobox:
- ruby 1.9, 2.0, 2.1, 2.2 / jruby 1.6, 1.7, 9.0
- node 0.8, 0.10, 0.12 / iojs 2.3
- python 2.7, 3.4
- php 5.3, 5.4, 5.5, 5.6
- wordpress (version unknown)
- java openjdk 7, 8 / sunjdk 6, 7, 8 (no minor version information available)
The actual content on the "Engines" page is aspirational, to say the least. One of the first question I ask of a tech product is "is it usable today for any current projects?" - why make this question challenging for site visitors?
If they're targeting novice web developers who should follow best practices, no rails support and out-of-date node support seems like a bad place to start.
- sanderson1 11y agoPosted this answer to a similar question/comment: --- 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. --- The library of engines is in its infancy and we're working to expand it. You're absolutely right in saying that the list of engines is "aspirational". Anybody can build and publish new engines. Any help you can provide would be greatly appreciated.
- gmisra 11y agoAspirational is great, but I would suggest you update that page to clearly identify what is currently supported versus what is aspirational. There is probably limited overlap between your target user audience and your target collaborator audience.
- tylerflint 11y agoI think you're right. Thanks for the advice!