similar to: Problem with incorrect permissions with shared folders

My app is set up without database.yml in version control. I created a shared_path/config dir, and put database.yml in it. After I update the code, I want to link the app''s database.yml file to the shared config. So I added this task desc ''Copy the database config'' task :after_update_code, :roles => :app do run "ln -s #{shared_path}/config/database.yml

How does one configure capistrano for moving local file to your remote server? In the docs it says that one cannot use file:// so what''s the configuration step for resolving this issue? Thanks in advance, -Conrad -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060514/93bb7173/attachment-0001.html

Hi all, I want to love capistrano and I''m so close. My error is occuring while running the update_code task... (apologies for the shell spew) ************************************************************************* * executing "rm -rf /home/henster29/sites/glitter/releases/20060316143447/log /home/henster29/sites/glitter/releases/20060316143447/public/system &&\n ln

As I see in 2.0 there willn't be ability to control which flags should be shared, and which should be per-user. But may be there is some plans to implement settings to control that? It'll be great if you can write in dovecot-shared file which flags should be per-user. It's very usefull for group mailboxes, when each user should work with such mailbox like with their own. Now I

Between versions 1.0.4 and 1.0.5 there were some changes to the way dovecot-shared group ownership is propogated into new maildirs. Changing the group of new_dir/{tmp,new,cur} was added, but changing the group of new_dir itself was removed. As far as I can tell, this latter change may have been accidental. This patch puts the functionality back, in the 1.1 tree.

I have a few projects with large directories (say, user-uploaded files) that make using Capistrano a bit awkward. However, I suspect that I may have reached the "write a custom task" level. (I suppose I''m just thinking out loud, here...) It seems as though I''d want this directories symlinked in /shared... Maybe there''s a way to extend the

Quick question: I am going to use the file_column plugin to manage uploading thumbnails. By default the images are stored in the public/ dir of the rails project. The problem I see is that when capistrano redeploys a new build and symlinks it in none of the images will be in the new public/ dir... Does anyone have a solution for this? Thanks, Zack -------------- next part -------------- An

Hi, i''m using capistrano to deploy the application, but every time i deploy it change all the directory, so i lost also the ferret''s indexes. Is it possible to keep them in order to prevent the reindex on each deploy? -- Posted via http://www.ruby-forum.com/.

Hi! Using HEAD, and after the 7193:e5af14239137 changeset (Store physical message sizes also to dovecot-uidlist if needed.) I'm getting this: (gdb) bt full #0 0x0a0a80dd in kill () from /usr/lib/libc.so.41.0 No symbol table info available. #1 0x0a0e04a7 in abort () at /usr/src/lib/libc/stdlib/abort.c:65 p = (struct atexit *) 0x84992000 cleanup_called = 0 mask =

Hi all, I''m using Capistrano and SVN to version control and deploy, but I''m not sure what to do about my images directory. I use file_column and RMagick to save images to the disk under a model called "Image", and they''re saved in public/image/... etc. Each time I deploy a new version, my image folder doesn''t exist anymore. I don''t want

Some hardware (e.g. Dell Studio laptops) require special functions to be called on physical cpu 0 in order to avoid occasional hangs. When running as dom0 under Xen this could be achieved only via special boot parameters (vcpu pinning) limiting the hypervisor in it's scheduling decisions. This patch series is adding a generic function to be able to temporarily pin a (virtual) cpu to a

Some hardware (e.g. Dell Studio laptops) require special functions to be called on physical cpu 0 in order to avoid occasional hangs. When running as dom0 under Xen this could be achieved only via special boot parameters (vcpu pinning) limiting the hypervisor in it's scheduling decisions. This patch series is adding a generic function to be able to temporarily pin a (virtual) cpu to a

I am using nginx with unicorn as a reverse proxy. Has been fantastic, but needed to look through some code for first time. Using ruby 1.9.3p194 with rails 3.2.9, development mode with ssl enabled, I start unicorn with -d ...and it does not get served up by nginx. Any ideas, or more information needed? Thanks! Jet Below is my unicorn.rb for developent: # config/unicorn.rb env =

Hi, This is a recurring issue for me - the index directory on my production server and everything below it occasionally disappears and isn''t reconstructed. I tried manually creating the entire index path manually before starting the server, but it still happened while the server is running. I don''t know what''s causing the index to disappear and I''m also not

Some hardware (e.g. Dell Studio laptops) require special functions to be called on physical cpu 0 in order to avoid occasional hangs. When running as dom0 under Xen this could be achieved only via special boot parameters (vcpu pinning) limiting the hypervisor in it's scheduling decisions. This patch series is adding a generic function to be able to temporarily pin a (virtual) cpu to a

Some hardware (e.g. Dell Studio laptops) require special functions to be called on physical cpu 0 in order to avoid occasional hangs. When running as dom0 under Xen this could be achieved only via special boot parameters (vcpu pinning) limiting the hypervisor in it's scheduling decisions. This patch series is adding a generic function to be able to temporarily pin a (virtual) cpu to a

Some hardware (e.g. Dell Studio laptops) require special functions to be called on physical cpu 0 in order to avoid occasional hangs. When running as dom0 under Xen this could be achieved only via special boot parameters (vcpu pinning) limiting the hypervisor in it's scheduling decisions. This patch series is adding a generic function to be able to temporarily pin a (virtual) cpu to a

Some hardware (e.g. Dell Studio laptops) require special functions to be called on physical cpu 0 in order to avoid occasional hangs. When running as dom0 under Xen this could be achieved only via special boot parameters (vcpu pinning) limiting the hypervisor in it's scheduling decisions. This patch series is adding a generic function to be able to temporarily pin a (virtual) cpu to a

Some hardware (e.g. Dell Studio laptops) require special functions to be called on physical cpu 0 in order to avoid occasional hangs. When running as dom0 under Xen this could be achieved only via special boot parameters (vcpu pinning) limiting the hypervisor in it's scheduling decisions. This patch series is adding a generic function to be able to temporarily pin a (virtual) cpu to a

Some hardware (e.g. Dell Studio laptops) require special functions to be called on physical cpu 0 in order to avoid occasional hangs. When running as dom0 under Xen this could be achieved only via special boot parameters (vcpu pinning) limiting the hypervisor in it's scheduling decisions. This patch series is adding a generic function to be able to temporarily pin a (virtual) cpu to a