But alas, I’m short on time and Ruby knowledge. Seems to me the nicest, most reusable thing to do would be to write a separate task (in lib/tasks) that runs after files are linked, and re-creates them to be relative. The issue doesn’t exist, for some reason, when linking to files (.env). The thing that tipped me off (besides the above linked recipes for Cap 2 that talk about relative symlinks) was that I manually created links via SSH as an experiment: ln -s releases/RELEASENUM current, and I could suddenly access linked directories just fine. (FWIW, I also had issues navigating through to the symlinked directories in my FTP client, but that could just have been an issue with my FileZilla.) But when trying to access symlinked files via HTTP, the browser would return a 403 or a 500.

In SSH, I could even cd into the symlinks. Doing a readlink on /current (and /current/app/.env, and /current/app/uploads) showed the paths were all correct. The really odd thing is that Capistrano was creating and verifying links just fine. MT uses an /html like other hosts use /htdocs, so I also tried deploying to that directory. I was deploying to the root of the domain–so the path looked like /home/ACCOUNTNUM/users/.home/domains/. I don’t know Ruby, so any direction at all would be really helpful. (They also don’t account for the shared assets/environment-specific links, the symlinks to which are also absolute by default.) So, my question is this: can I force Capistrano to use relative paths in symlinks? I’ve found a couple of recipes that do just that, but they appear to be built on previous versions of Capistrano, and I get errors every time I use their methods. The problem is this: as a (weird, random, undocumented) limitation to using their GridServer shared hosting service, symlinks must point to relative paths, but Capistrano creates symlinks with absolute paths.Īs an experiment, after a deploy, I SSHed into the server, did a rm current, and manually did ln -s current releases/$releasenumber$. However, the symlinks remain inaccessible to the outside world (403 and 500 errors when attempting to access the site or any linked content). So I’ve spent two days jerking my MediaTemple (gs) account around so that I can deploy with Capistrano, and I’ve hit a bit of a wall.Ĭapistrano writes to my server perfectly.

Mediatemple ftp filezilla