File System Related · How To · Linux · Solution to Error

How To Compress a Directory with the tar Command and Exclude Certain Files, tarball exclude files

When creating a tar-ball (compressing a directory of files), you may exclude certain files by using the –exclude flag.

The –exclude flag will also work with a wild card “*”. Here is an example of how to tar-ball a directory from the parent directory and exclude certain files:

IMPORTANT: Be sure to use the –exclude just after the tar command, NOT at the end of the command.

Grunt · How To · Solution to Error

FIXED: Grunt Dploy Not Pushing Files

Getting-started-with-GruntI was trying to set up Grunt to deploy to my development server.

According to the output in the terminal all went well. However no files were being uploaded.

When setting up the info in my grunt.js file, I had used the full path as output by the “pwd” command like this:

According to the feedback in the terminal (shown above) it “appears” to have worked just fine. However, this is WRONG.

Actually the grunt.js file needs to have the stage: path: local: value to be the path as seen from the project root. As in, the same place as where the grunt.js file resides.


I hope that will save you a few hours of scratching your head. : )

Grunt · How To · node · Solution to Error

How To Fix: “Errno::ENOENT: No such file or directory @ rb_sysopen – undefined” Grunt Error

While setting up a grunt.js file, I ran into the following stubborn error.

After having Googled several solutions to the problem. I ended up updating my Ruby and uninstalling and re-installing nodejs among other things.

It turns out I had a misspelling in the directory of the key-data pair inside the grunt.js file.

I missed it because it was on a line that was off the screen.

This error can at times appear to be a more serious issue than it really is.

So remember to check your grunt.js file proper syntax first. You just might save yourself some trouble.

Apache · Backend · How To · Linux · Solution to Error · ZendFramework

How To Fix 403 Forbidden Error from htaccess File

As a web developer, you will likely need to make rewrites for clean URLs and produce an htaccess file so you can create ModRewrite rules.

If you encounter a 403 Forbidden Error after creating the htaccess file. This happens because even though the htaccess file itself may have the right permissions, it is possible the web server is not explicitly allowing the rewrites for that directory.

To check for this you should take a look at the webserver error log. The webserver error log may be in different locations depending on your operating system. On Mac OS X it’s in /var/log/apache2/error_log, on most Linux boxes it’s in /var/log/httpd/error_log

for example, you can view the last few errors in the error log by using the tail follow command in the linux command line like this:

If you see an error like this:

Then you can fix the issue by adding the following line to the top of the .htaccess file:

So that it may look something like this ( the other code should be code specific to your own set up). The important thing to know is that by adding Options +FollowSymLinks you explicitly allowing the rewrites.

If you are comfortable editing your Apache httpd.conf file, you can add the Options +FollowSymLinks to the directory directive like this: