Live data from Hacker News

Nanobox: Local development done right

desktop.nanobox.io

11–20 of 84 posts

Re: Nanobox: Local development done right

#11
post #7

Earlier quoted context omitted.

Later it says you can specify which JS runtime to use with python: build: runtime: python27 js_runtime: nodejs-0.12 app_module: ''

That one's not unreasonable.

It seems I can't also specify a ruby runtime, though. What makes one reasonable and another not?

Re: Nanobox: Local development done right

#15
post #4

Earlier quoted context omitted.

Agreed. This sentence especially makes me think this is too much magic: >Nanobox detects your app type and automatically configures the environment and installs everything your app needs to run and >Each Engine sniffs the code looking for a positive match to determine which language / framework your app is written in and lastly: >The matched Engine generates a Boxfile defining the services your app needs to run and h…

>> Nanobox detects your app type and automatically configures the environment and installs everything your app needs to run Yeah, that's gonna be a bit hard for it to do with our Clojure web app. Well, maybe. If it knows to install openjdk-7 and nginx because it sees a project.clj, then perhaps it really is as smart as it thinks it is.

.. or immutant or jetty or .... Buildinng a simulated production environment on the dev machine is hard because in production, there are (in most cases) special settings, special servers, special configurations, special files on special places, ... It is rarely out of the box configured service stacks.

Re: Nanobox: Local development done right

#16
I have a Dockerfile that I use to run my production. This is already built.

Is there anything I can use to build a local dev environment quickly using the Dockerfile. Obviously I can use docker, but quite often new developers have trouble with docker.

Re: Nanobox: Local development done right

#17

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.

Yeah, 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 the link for Create Custom Engine leads to a 404 on https://nanobox.io/engine-dev

Re: Nanobox: Local development done right

#19

I have a Dockerfile that I use to run my production. This is already built. Is there anything I can use to build a local dev environment quickly using the Dockerfile . Obviously I can use docker, but quite often new developers have trouble with docker.

You can use Lattice for that: http://lattice.cf/docs/

Re: Nanobox: Local development done right

#20
I am skeptical about this tool because I feel like the learning surface underneath will actually be massive, but massive in the wrong direction toward someone's idiosyncratic product.

In order to give me confidence that I won't have to look underneath the surface too much, I'd want to know that the abstraction is very airtight, but all appearances say otherwise. Like another commentator said, I'd rather have an app with well-defined boundaries.

Post reply on HN