Same experience with VirtualBox but I figured it out. Samba is not easy and googling for how somebody else solved it years ago didn't work for me. I have it mostly scripted but it's not standalone. I'll extract the scripts and blog about it.
On Monday, October 22, 2012 12:03:11 PM UTC-7, Valery Carpentier wrote: > > For a while I tried to run node in a VM (Virtual Box with Ubuntu > server), with the code shared in my Dropbox, so I could easily move > between my two machines (one OSX, one Windows 7) and edit in > OSX/Windows. It nearly worked until I ran into some Virtual Box bugs > (No matter how I configured them, the shared Dropbox folders never > showed up correctly in Ubuntu). I didn't insist as it wasn't an > absolute necessity for me, but hopefully these bugs have been fixed > now and that could be a viable (simple) setup. > > On 22 October 2012 01:22, John Scott <[email protected] <javascript:>> > wrote: > > I was running Node on my Windows 7 64bit laptop until I installed a > module > > that wouldn't compile. > > > > So since I am deploying to a linux production server, I decided to setup > a > > linux development server with VirtualBox. I run these tools on Windows : > > > > * WebStorm from JetBrains http://www.jetbrains.com/webstorm/ which has > > awesome support for Node and JavaScript development in general. I love > the > > GitHub support and its `always sync` remote deployment feature means > that > > file changes are instantly pushed to your local VM instance of linux > running > > Node. > > > > * Git for Windows http://msysgit.github.com/ includes msysGit which > doubles > > as a great command-line Git client as well as a great Bash shell. You > can > > right-click on a folder to `Git Bash here` which starts a bash sell at > that > > directory. You can also connect to your VM instance via ssh like this : > > > > > > $ ssh user@<localip> > > > > > > This setup which has the following pros / cons : > > > > Local development on the same platform as production is sensible and > > pragmatic - but you get to keep running your development tools on > Windows > > (which I really like). Issues you will encounter in production are > likely > > encountered first in development. > > > > VirtualBox's `snapshots` feature let you try things on your development > > server at little risk because you can revert to a previous snapshot if > you > > screw things up. I often pre-flight major changes to my production > server > > this way too. > > > > You need at least 1GB of RAM to dedicate to a linux VM i found. > > > > > > On 22 October 2012 06:46, mgutz <[email protected] <javascript:>> > wrote: > >> > >> You're best bet is Xubuntu if you want GUI or plain Ubuntu/Debian > server > >> on VirtualBox (or even better VMware for its simple networking). That > way > >> you don't have any gotchas when deploying your node app to production. > >> > >> On Windows I use Chrome + SecureShell add-on to to connect to my > virtual > >> machines. I use tmux and vim from terminal. My colleagues map a samba > share > >> from the virtual machine and they edit the files in Windows using > Sublime. > >> That works surprisingly well. An Ubuntu server with node, redis and > mongodb > >> run just fine in 512MB. > >> > >> On Friday, October 19, 2012 7:23:05 AM UTC-7, jerome wrote: > >>> > >>> Hi All, > >>> > >>> For various reasons, I may be switching to a Windows PC at home, but > >>> would like to continue playing with Node. > >>> > >>> I've been on a Mac for years. Am I likely to encounter any pitfalls or > >>> gotchas doing node dev on Windows? > >>> > >>> A buddy of mine reminded me that some of the add ons require a C > >>> compiler. What are my options? > >>> > >>> -- > >>> Regards, > >>> Jerome > >>> Music || Web Dev > >>> > >>> > >> -- > >> Job Board: http://jobs.nodejs.org/ > >> Posting guidelines: > >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > >> You received this message because you are subscribed to the Google > >> Groups "nodejs" group. > >> To post to this group, send email to [email protected]<javascript:> > >> To unsubscribe from this group, send email to > >> [email protected] <javascript:> > >> For more options, visit this group at > >> http://groups.google.com/group/nodejs?hl=en?hl=en > > > > > > > > > > -- > > Regards, > > > > John Scott > > > > -- > > Job Board: http://jobs.nodejs.org/ > > Posting guidelines: > > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > > You received this message because you are subscribed to the Google > > Groups "nodejs" group. > > To post to this group, send email to [email protected]<javascript:> > > To unsubscribe from this group, send email to > > [email protected] <javascript:> > > For more options, visit this group at > > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
