Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nanobox: Local development done right

desktop.nanobox.io

Post reply on HN
Print view View original

31–40 of 84 posts

Re: Nanobox: Local development done right

#31

Post by sdegutis »

creshal wrote: post #21
sdegutis wrote: post #8

Earlier quoted context omitted.

That said, the colors really are beautiful. At least, what I can see of them. Excellent color palette! I'm a sucker for softened tones like these.

Seems to be the solarized colour palette (or was inspired by it, at least): http://ethanschoonover.com/solarized Looks fancy, but boy is it bad on the eyes. I've since switched away from it to harlequin ( https://github.com/nielsmadan/harlequin ).

I used to use Solarized but switched to Zenburn since then in my editor. That said, whatever color scheme they're using on that website looks really nice on the website, even if I wouldn't use it in my editor (I might though!)

Re: Nanobox: Local development done right

#34

Post by odiroot »

aeze wrote: post #33
odiroot wrote: post #29

And again dependency on Vagrant and Virtualbox. What can you do. On every modern Ubuntu (even previous/old LTS) Docker works out of the box, without any issue. Why add another virtualization layer on top?

To work with other operating systems?

Then why not have it optional?

Re: Nanobox: Local development done right

#35

Post by lyondhill »

stinky613 wrote: post #17
duiker101 wrote: post #3

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

We will get that fixed asap. Thanks for letting us know

Re: Nanobox: Local development done right

#36

Post by sanderson1 »

sdegutis wrote: post #10
thecopy wrote: 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.

Auto-detections is based on the existing library of engines, which is only in its infancy right now. Engines have what's called a "sniff" script. This is a bash script written by the engine developer that searches the codebase for uniquely identifying files or content within files. Auto-detection won't work for every app, but it should help to get the majority of apps up and running quickly. For very custom apps, anybody can develop and publish their own engine. Information about engines is in the nanobox docs: https://docs.nanobox.io/engines/

Re: Nanobox: Local development done right

#37

Post by 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.

Re: Nanobox: Local development done right

#38

Post by sanderson1 »

arsalanb wrote: post #22

Assuming this works perfectly well, all the time — this is awesome. A possible pain-point this is addressing is that apps behave differently locally and then when you move them to the cloud (aka deploy them) they behave differently.

Full disclosure: I work for Nanobox. We're prepping Nanobox Cloud for release likely in 2016 https://nanobox.io/cloud/. With Nanobox Cloud, you'll be able to take the exact same environment configuration you have locally and deploy it to a cloud provider (starting with Digital Ocean but others will soon follow). The same engine used to run your app locally will be used in the production app. The whole workflow has been designed to provide parity between development and production environments.

Re: Nanobox: Local development done right

#40

Post by sanderson1 »

grhmc wrote: post #7
duiker101 wrote: post #3

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.

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

The js_runtime is included because of the ubiquity of using tools like bower and gulp to compile assets, which require node.
Post reply on HN