6 ms·

Are there really that many people that want to code a Node.js app but can't set up an quick ubuntu image using virtualbox? EC2 as a dev environment seems a bit

Are there really that many people that want to code a Node.js app but can't set up an quick ubuntu image using virtualbox? EC2 as a dev environment seems a bit backwards.

sthatipamala 16y ago
The great thing with EC2 is that you can let all your friends try your Node.js app by giving them a simple link. It's all about reducing the barrier to entry.
ericz 16y ago
For me the reason is two fold. Sharing the hacks I build is easier when I don't have to deal with NAT. Secondly, for some environments, like the default Amazon Linux AMI the default packages and PATH makes it a huge hassle to compile/install Node. This AMI was born out of our own frustration with that process which I'm sure affects Linux distros other than just the Amazon Linux one. EDIT: Removed lingo abuse.
- jrockway 16y ago
  NAT? Who doesn't have IPv6 these days? If I want to share my node app with someone, I just tell them to visit http://snowball2.jrock.us:4545/ http://snowball2.jrock.us:4545/ and there we are. (Really? -2? I am actually surprised that this is a problem. I have to share web apps with my friends, in both directions, regularly. It's never been a problem. Everyone has a publicly-routeable address these days.)
  - robflynn 16y ago
    Sadly, not all ISPs allow this. I run into this frustration whenever I visit my parents. They use a wireless ISP which does not provide each customer with a public facing IP. They all share the same public IP address and therefore can not receive incoming connections. It's quite frustrating.
    - jrockway 16y ago
      Ah, but it's easy to get a publicly-routed IPv6 tunnel.
- sausagefeet 16y ago
  "real-time web apps"? C'mon, don't abuse the lingo man.
jhuckestein 16y ago
I use EC2 for development (I commute via bike so I don't usually work offline) and it's the best environment I've ever coded in. In fact, I can even code and fix things from my iPad, your iPad, anyones computer, my phone, a library kiosk or an airplane cockpit. If I want to try something experimental (aka dist upgrade etc), I just clone the AMI, make my modifications, and if I like it, I keep it. My emacs looks exactly the same, where ever I am. If I need to get to a different computer, I still log in through my EC2 instance, where all servers I need are accessible via convenient shortcuts and the appropriate port forwarding is configured already. And, again, I can do this from wherever I am. How is that backwards?
- cosbynator 16y ago
  You make a good point, on second thought EC2 is a pretty good development environment as long as you aren't GUI dependent. I still don't think it is a good development environment for someone that finds a node.js install too complicated. This seems to be what the article suggests.
- drivebyacct2 16y ago
  How is that superior to having a nice desktop that you can shell/nx into?
  - jhuckestein 16y ago
    OTTOMH: create different configurations that you only need for one project, experiment with cutting edge software, increase CPU, memory and disk on the fly ...
    - drivebyacct2 16y ago
      For a development environment? What? Especially with node.js that simply doesn't make sense. If you're running it with users on it which would actually need CPU, memory or disk, duh I would run it on EC2.
  - AlexC04 16y ago
mwdev 16y ago
Yes. They are called Windows users. And I am one of them. I set up an ec2 instance last week using a similar process. I also got a cywin up locally, but I use the ec2 instance mostly. Now that you mention it, Virtual Box would be a great solution and it would be great to have a guide walking through this. I used google to figure everything out and 'node.js ec2' is a query you get to pretty quickly when you have no starting reference point.

Are there really that many people that want to code a Node.js app but can't set up an quick ubuntu image using virtualbox? EC2 as a dev environment seems a bit backwards.

sthatipamala 16y ago

The great thing with EC2 is that you can let all your friends try your Node.js app by giving them a simple link. It's all about reducing the barrier to entry.

ericz 16y ago

For me the reason is two fold. Sharing the hacks I build is easier when I don't have to deal with NAT. Secondly, for some environments, like the default Amazon Linux AMI the default packages and PATH makes it a huge hassle to compile/install Node. This AMI was born out of our own frustration with that process which I'm sure affects Linux distros other than just the Amazon Linux one. EDIT: Removed lingo abuse.

jrockway 16y ago
NAT? Who doesn't have IPv6 these days? If I want to share my node app with someone, I just tell them to visit http://snowball2.jrock.us:4545/ http://snowball2.jrock.us:4545/ and there we are. (Really? -2? I am actually surprised that this is a problem. I have to share web apps with my friends, in both directions, regularly. It's never been a problem. Everyone has a publicly-routeable address these days.)
- robflynn 16y ago
  Sadly, not all ISPs allow this. I run into this frustration whenever I visit my parents. They use a wireless ISP which does not provide each customer with a public facing IP. They all share the same public IP address and therefore can not receive incoming connections. It's quite frustrating.
  - jrockway 16y ago
    Ah, but it's easy to get a publicly-routed IPv6 tunnel.
sausagefeet 16y ago
"real-time web apps"? C'mon, don't abuse the lingo man.

jhuckestein 16y ago

I use EC2 for development (I commute via bike so I don't usually work offline) and it's the best environment I've ever coded in. In fact, I can even code and fix things from my iPad, your iPad, anyones computer, my phone, a library kiosk or an airplane cockpit. If I want to try something experimental (aka dist upgrade etc), I just clone the AMI, make my modifications, and if I like it, I keep it. My emacs looks exactly the same, where ever I am. If I need to get to a different computer, I still log in through my EC2 instance, where all servers I need are accessible via convenient shortcuts and the appropriate port forwarding is configured already. And, again, I can do this from wherever I am. How is that backwards?

cosbynator 16y ago
You make a good point, on second thought EC2 is a pretty good development environment as long as you aren't GUI dependent. I still don't think it is a good development environment for someone that finds a node.js install too complicated. This seems to be what the article suggests.
drivebyacct2 16y ago
How is that superior to having a nice desktop that you can shell/nx into?
- jhuckestein 16y ago
  OTTOMH: create different configurations that you only need for one project, experiment with cutting edge software, increase CPU, memory and disk on the fly ...
  - drivebyacct2 16y ago
    For a development environment? What? Especially with node.js that simply doesn't make sense. If you're running it with users on it which would actually need CPU, memory or disk, duh I would run it on EC2.
- AlexC04 16y ago

mwdev 16y ago

Yes. They are called Windows users. And I am one of them. I set up an ec2 instance last week using a similar process. I also got a cywin up locally, but I use the ec2 instance mostly. Now that you mention it, Virtual Box would be a great solution and it would be great to have a guide walking through this. I used google to figure everything out and 'node.js ec2' is a query you get to pretty quickly when you have no starting reference point.