- Based on the Nginx article at ArchWiki.
- Some commands in the script are specific to the 64 bit architecture.
If you have a Box account and you want to access it from your linux system directly, follow these steps:
Install the WebDAV file system driver. On Arch Linux, this is done by running
$ sudo pacman -S davfs2
Set the username(email) and password for your Box account in the davfs2 secrets file. On Arch, add the following line to
/mnt/box email@example.com secret_password_is_secret
Create the mount point where you want the Box files to be shown:
$ sudo mkdir /mnt/box
Add a line to your
/etc/fstabto mount it automatically, with write access to a normal user:
https://www.box.com/dav /mnt/box davfs defaults,uid=1000,gid=100 0 0
gidvalues must be the valid user id and primary group id of the regular user whose account needs access to the Box files. To find out the uid and gid for the currently logged in user, just run
Note: If you change the mount point in
/etc/fstabfrom what is shown above, remember to change it in
Mount the folder by running:
$ sudo mount -a
This should automatically pick up the username and password from the davfs2 secrets file and mount the folder for you. If for some reason this doesn’t work, try:
$ sudo mount.davfs https://www.box.com/dav /mnt/box
Once you have successfully mounted the folder using the
mount -a command (which picks up mount options from
/etc/fstab), try creating/modifying some files as the normal user (set above in step 4) to ensure everything is in order.
One of my initial excursions into Sails.js territory:
I had posted a while back about a web-based front-end to aria2c that I started building, primarily as an exercise in learning Node.js. While it has been functional and available on GitHub for some time, I now have the pleasure to announce that it is now available directly through the NPM Registry.
Needless to say, my JS knowledge base required a few upgrades before I could put together anything smarter than a ‘Hello World’ responder. Said upgrades, among other excellent sources, I have found here, here, here along with the JS object graph learning trail (part 1, part 2 and part 3). In fact, most of How to Node is a must-read if you’re planning on serious Node programming.
But this post is not just about my experience learning server-side JS. In the process of upgrading my overall web development repertoire, I’ve had to undergo quite a steep ramp-up on client-side JS technologies as well…
The biggest problem still, was the lack of flexibility, in spite of all the automation and scaffolding (or perhaps because of it), in building a custom UI to one’s exact liking (esp. with dynamic scaffolding, where you lose significant control over the finally generated DOM). Including client-side styling libraries like Bootstrap would require jumping through increasingly tight hoops in order to make the auto-generated templates adhere to the specific DOM and CSS requirements dictated by such libraries.
As of today, I’m still delving deeper into the fascinating world of server-side JS runtimes, the accompanying middleware (Connect and Express being among the biggest names here), while also being repeatedly amazed by the power of modern client-side frameworks. The JS landscape is already incredibly expansive, and continues to grow at a frightful rate, as each day heralds the launch of several new libraries, frameworks and tools that make JS programming all the more exciting and enlightening.
My journey of exploration has already started bearing fruit, and has empowered me to give back to the wonderful open source community (JS or otherwise) that I have received so much from. My current efforts are focused on building a JS-based e-commerce platform, and I am confident I have selected the right platform for the necessary pace of development and superior performance that I demand of the product-to-be.