Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8966857
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 15, 20262026-06-15T17:06:47+00:00 2026-06-15T17:06:47+00:00

I have a problem on my production server where assetic:dump is timing out on

  • 0

I have a problem on my production server where assetic:dump is timing out on a Capifony deploy (but not always).

Running assetic:dump locally is fine. Also deploying to a different staging (much less powerful) server is fine.

To fix this (and speed up deploy), I was wondering whether it’s possible to run assetic:dump before a deployment and just send those complied assets along with the rest of the deployment?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-15T17:06:49+00:00Added an answer on June 15, 2026 at 5:06 pm

    That’s a bit tricky, I’m also trying to do this (java is not working properly on my server, so deployment fails).

    The problem is that Capifony deploys from a source control repository, and usually dumped assets are not on the repository (and they shouldn’t).

    So I guess the only way to do this is to create a Capistrano task (Capifony is based on Capistrano) that will dump the assets and rsync them on the server.

    Edit : Here’s my attempt
    Edit : It does work, I’ve been using it since I answered the question.

    I’m sure there are plenty of possible improvements, I’m not a ruby guy, I’m not a shell script guy either.

    In your deploy.rb you can add two tasks :

    before "deploy:update_code", "deploy:dump_assetic_locally"
    after "deploy:update_code", "deploy:rsync_local_assets_to_server"
    

    And the code associated to those tasks (in the same file) :

    namespace :deploy do
      task :dump_assetic_locally, :roles => :web do
        run_locally "php app/console assetic:dump --env=prod"
      end
    
      task :rsync_local_assets_to_server, :roles => :web do
        finder_options = {:except => { :no_release => true }}
        find_servers(finder_options).each {|s| run_locally "rsync -az --delete --rsh='ssh -p #{ssh_port(s)}' #{local_web_path}/js/ #{rsync_host(s)}:#{release_path}/web/js/" }
        find_servers(finder_options).each {|s| run_locally "rsync -az --delete --rsh='ssh -p #{ssh_port(s)}' #{local_web_path}/css/ #{rsync_host(s)}:#{release_path}/web/css/" }
      end
    
      def local_web_path
        File.expand_path("web")
      end
    
      def rsync_host(server)
        :user ? "#{user}@#{server.host}" : server.host
      end
    
      def ssh_port(server)
        server.port || ssh_options[:port] || 22
      end
    
    end
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We have problem with our Qt based production server for our business application. When
I have a WordPress site running on a production server that I recently copied
I recently installed APC on my production server but It's not working as expected.
We have found a problem with our deployment to a production server that runs
I have a production server running an app that uses CouchDB as its main
Problem I have an Xpage working properly on the test Domino server. On production
I have a Rails app that is running on a production server with Apache
I have some problem while configuring symfony project on the production server. When I
I have a problem in our BTS production environment which we cannot reproduce in
I have a problem that occurs only in a production environment, deployed at heroku.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.