The Schedule
It's on! We start on the morrow.
Where: Downtown LA
When: Monday-Thursday, 8-11 PM (12 hrs/wk)
Shout out to Jen Diamond (member of Team Bundler and organizer of the Los Angeles Women's Ruby on Rails Group) for 1) continuing to run the LA Ruby Eastside study group despite her new stint on the Westside, and 2) agreeing to move its location from Glendale to Downtown LA.
Popping my IRC Freenode Cherry
Shout out to UForgotten of the IRC #vagrant channel, who helped me debug a problem on Freenode for the first time!
Earlier today, I tried to run vagrant up again in my new Linux environment as per Discourse as Your First Rails App, and luckily it didn't hang at the VM boot anymore. However, I kept getting this error:
[Default] Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
I scrounged the Discourse docs for NFS errors and found the following in the Discourse Vagrant Developer Guide:
Nope, not my errors. Google wasn't any real help either; Vagrant issues #1659, #1694, and #1702 mentioned similar errors but the solutions didn't work for me. Vyki and Kurtis weren't online to help out. I was so totally (de)buggin'.
Frustrated after running vagrant up and vagrant halt over and over again with no success, I turned to the next best thing: irc.freenode.net.
I posted my problem on the #vagrant channel, and bam, UForgotten immediately responded. (The badass was actually troubleshooting for multiple IRC users at the same time.) He asked me some questions, and had me run some commands to get to the bottom of things. He thought at first it had to do with IP issues that he himself had run into recently with Vagrant, but that wasn't it.
UForgotten eventually told me to send him my Vagrantfile and debugging log after running this:
$ VAGRANT_LOG=debug vagrant up
I did so, and after some time, he informed me that the problem lay in this line of the log:
exportfs: /home/jzeta/Projects/rgsoc/discourse does not support NFS export
Wait a second.....I'd seen that before.......!
"The root Discourse directory cannot be on an ecryptfs mount or you will receive an error." When I installed Ubuntu, I had opted to encrypt my home folder, which is where I had put Discourse. All I have to do is remove the encryption, and the Discourse environment should be able to run.
The answer had been right in front of me! Guess I just had to learn the hard way to always read the error log.
UForgotten was pretty patient with my noobiness, and said the reason why I couldn't use an encrypted folder was that NFS simply can't handle the decoding. Another IRC user, smerrill, also put in his 2 cents about how NFS can't export symlinks either.
I thanked UForgotten for his help, and he replied, "De nada mang. Welcome to IRC. It's good karma, I need help once in a while so when I can I try to pay it forward." Cool.
Really glad my first foray into IRC Freenode went well! On to fixing the encryption thing tomorrow.
1st time getting help on irc freenode ---> problem solved! thanks #vagrant channel @RailsGirlsSoC
— jz (@jzeta) July 2, 2013
I am an Installing Machine
Welp, my dream of a VM within a VM will alas remain unfulfilled. I really couldn't get Vagrant to boot the Discourse VM without hanging.
I've been hesitant about installing Ubuntu on my laptop, but I finally gave in and decided to dual-boot Ubuntu and Windows at Kurtis's suggestion. Learned a bit about HD partitioning and boot loading. Bye, Linux VM and LinuxLive USB!
I've set up my Linux dev environment yet again (probably 10th time in the last month? here's to repetition), and will try to get Discourse running by tomorrow.
