4 ms·
seems interesting but I started clicking around, specifically in the Python section and this website seems to have been released too early, the text I am not su
by duiker101 11y ago
seems interesting but I started clicking around, specifically in the Python section and this website seems to have been released too early, the text I am not sure is right(it says I need to use a ruby engine settings for python?) and some links don't work or give 404.
- grhmc 11y agoLater it says you can specify which JS runtime to use with python: build: runtime: python27 js_runtime: nodejs-0.12 app_module: ''
- zeckalpha 11y agoThat one's not unreasonable.
- grhmc 11y agoIt seems I can't also specify a ruby runtime, though. What makes one reasonable and another not?
- sanderson1 11y agoThe mention of ruby in the description is a typo. There isn't a ruby runtime available in the generic python engine, but you're free to fork the engine and add the ruby runtime. All engines are open-source.
- sanderson1 11y agoThe js_runtime is included because of the ubiquity of using tools like bower and gulp to compile assets, which require node.
- stinky613 11y agoYeah, if anyone from nanobox is reading, I found a broken link on the Node.js Engine page: On page https://engines.nanobox.io/languages/nodejs https://engines.nanobox.io/languages/nodejs the link for Create Custom Engine leads to a 404 on https://nanobox.io/engine-dev https://nanobox.io/engine-dev
- lyondhill 11y agoWe will get that fixed asap. Thanks for letting us know
- tylerflint 11y agoThanks for the heads up! Please keep in mind this is an open-source project in the pre-beta phase. Any contributions are welcomed!