symlink

I am using capistrano to deploy my Ruby on Rails project. I am on a Dreamhost VPS and since a few weeks ago, with no change in capistrano or passenger, I began to experience a strange problem with the deployment: Every time capistrano is deploying my application, everything goes right except deploy:symlink (which is called by default) that should point the "current" directory to the newest release. Although the new release is deployed properly to the "releases" directory, the problem is the "current" symlink is always set to previous release instead of the new one. So I can deploy apps but I

Windows native alternative for ln -s is mklink . Is there any native alternative for readlink ? Or how to natively identify if the file is symlink? I don't believe there's any tool directly equivalent to readlink . But you can see in the output of dir whether an item is a symlink or not, so you can still determine this from the command line or in a script. Test whether it's a symlink or not You can pretty easily test whether a given file is a symlink using syntax like: dir mysymlink | find "<SYMLINK>" >NUL if not errorlevel 1 echo. It's a symlink! Errorlevel will be 0 in the case that "

I wrote a simple script to automate creating a symbolic link. #!/pseudo today = "/tmp/" + date("Y-m-d") exec("ln -sf " + today + " /tmp/today") Simple enough; get today's date and make a symlink. Ideally run after midnight with -f so it just updates it in-place. This works just fine! ...for my user. xkeeper /tmp$ ls -ltr drwxrwxrwx xkeeper xkeeper 2014-10-21 lrwxrwxrwx xkeeper xkeeper today -> /tmp/2014-10-21/ xkeeper /tmp$ cd today xkeeper /tmp/today$ cd .. Notice that it works fine, all the permissions are world-readable, everything looks good. But if someone else wants to use this link (we

When working with apache on a unix system, If your file system has icons in /home/me/web/icons and you want the browser be able to display them when calling the url http://www.me.com/icons/myicon.jpg for example, then you have at least 2 solutions : alias ( Alias /icons/ /home/web/icons/ ) symbolic links ( ln -s /home/web/icons /home/me/web/www/icons ) It seems to me that using apache aliases is the best choice since we know exactly that aliases would normally be in the /etc/apache2 directory ( so that is just one place to look at in case the application grows ), but I would be pleased to know