How to compile assets from within exploded war?

kevin · January 25, 2013, 5:00pm

We are trying to move asset compilation step to deployment, after the
war
is exploded on deployment, but before the application starts. Our
project
is a Rails 3.2.10 app on JRuby 1.7.1, includes turbo-sprockets-rails3
gem,
packaged as war under Jetty.

I have a vendor bundle directory with all my gems in the war. I figured
I
could invoke the assets using java, passing the jruby-complete jar as an
argument. The process finds gem dependencies and rails will start, but
the
rake task fails because rake/file_utils.rb tries to invoke my args as a
shell argument. I think the issue is that it interpets the path to jruby
with the “file:/” prefix. And if one was to try to invoke a binary with
that prefix, it will simply fail.

Has anyone tried to compile assets while in a war structure using jruby
via
java?

Input:

#invoked from a bash script during the deploy process but before Jetty
starts up.
#APP_ROOT_DIR is the root of the war file
export GEM_HOME=$APP_ROOT_DIR/WEB-INF/vendor/bundle/jruby/1.9
export BUNDLE_WITHOUT=“development:test”
export BUNDLE_GEMFILE=$APP_ROOT_DIR/WEB-INF/Gemfile
export RAILS_ENV=production

java -jar lib/jruby-complete-1.7.1.jar -S
$APP_ROOT_DIR/WEB-INF/vendor/bundle/jruby/1.9/bin/rake --trace
assets:precompile

Output:

starting asset compilation…
Booted rails in 3.153
Included bundled gems in 5.32
** Invoke assets:precompile (first_time)
** Execute assets:precompile
file:/Users/khutson/myapp/target/myapp-1.7.6-SNAPSHOT/WEB-INF/lib/jruby-complete-1.7.1.jar!/META-INF/jruby.home/bin/jruby
/Users/khutson/myapp/target/myapp-1.7.6-SNAPSHOT/WEB-INF/vendor/bundle/jruby/1.9/bin/rake
assets:precompile:all RAILS_ENV=production RAILS_GROUPS=assets --trace
rake aborted!
Command failed with status (127):
[file:/Users/khutson/ruby_apps/secondporch/…]
/Users/khutson/myapp/target/myapp-1.7.6-SNAPSHOT/WEB-INF/vendor/bundle/jruby/1.9/gems/rake-10.0.3/lib/rake/file_utils.rb:53:in
`create_shell_runner’

Thanks for any info you can provide. We have no issue compiling assets
during our build.
NOTE: I don’t have rvm on the server (wish I did).

thanks,
Kevin

kevin · January 25, 2013, 6:01pm

That doesn’t work very well if you don’t know which env the war is going
to be deployed to eg: stage or prod. The different envs will often have
a
different asset host.

kevin · January 25, 2013, 5:17pm

Why not precompile the assets before packaging up the war file? That
would be much safer and standard.

However, if you really need to do it at deploy time then you should
check out this pull request to warbler and see if it works for you:

github.com/jruby/warbler

java -jar rails.war -S rake db:migrate (and some cleanup)

jruby:master ← kares:runnable

opened 02:45PM - 28 Dec 12 UTC

kares

+398 -229

I was working on it almost a year ago and got it to a place where `rake` seems t…o work : ``` kares@theborg:~/workspace/github/jruby-rack/examples/rails32$ java -jar rails32.war -S rake -T rake about # List versions of all Rails frameworks and the env... rake assets:clean # Remove compiled assets rake assets:precompile # Compile all the assets named in config.assets.pre... rake db:create # Create the database from DATABASE_URL or config/d... rake db:drop # Drops the database using DATABASE_URL or the curr... rake db:fixtures:load # Load fixtures into the current environment's data... rake db:migrate # Migrate the database (options: VERSION=x, VERBOSE... rake db:migrate:status # Display status of migrations rake db:rollback # Rolls the schema back to the previous version (sp... rake db:schema:dump # Create a db/schema.rb file that can be portably u... rake db:schema:load # Load a schema.rb file into the database rake db:seed # Load the seed data from db/seeds.rb rake db:setup # Create the database, load the schema, and initial... rake db:structure:dump # Dump the database structure to db/structure.sql. ... rake db:version # Retrieves the current schema version number rake doc:app # Generate docs for the app -- also available doc:r... rake log:clear # Truncates all *.log files in log/ to zero bytes rake middleware # Prints out your Rack middleware stack rake notes # Enumerate all annotations (use notes:optimize, :f... rake notes:custom # Enumerate a custom annotation, specify with ANNOT... rake rails:template # Applies the template supplied by LOCATION=(/path/... rake rails:update # Update configs and some other initially generated... rake routes # Print out all defined routes in match order, with... rake secret # Generate a cryptographically secure secret key (t... rake stats # Report code statistics (KLOCs, etc) from the appl... rake test # Runs test:units, test:functionals, test:integrati... rake test:recent # Run tests for {:recent=>"test:prepare"} / Test re... rake test:single # Run tests for {:single=>"test:prepare"} rake test:uncommitted # Run tests for {:uncommitted=>"test:prepare"} / Te... rake time:zones:all # Displays all time zones, also available: time:zon... rake tmp:clear # Clear session, cache, and socket files from tmp/ ... rake tmp:create # Creates tmp directories for sessions, cache, sock... kares@theborg:~/workspace/github/jruby-rack/examples/rails32$ java -jar rails32.war -S rake db:migrate == DeviseCreateUsers: migrating ============================================== -- create_table(:users) -> 0.0200s -> 0 rows -- add_index(:users, :email, {:unique=>true}) -> 0.0050s -> 0 rows -- add_index(:users, :reset_password_token, {:unique=>true}) -> 0.0050s -> 0 rows == DeviseCreateUsers: migrated (0.0360s) ===================================== ``` there seems to be more work required for `rails c` to work : ``` kares@theborg:~/workspace/github/jruby-rack/examples/rails32$ java -jar rails32.war -S rails console Usage: rails new APP_PATH [options] Options: -r, [--ruby=PATH] # Path to the Ruby binary of your choice # Default: file:/tmp/jruby7112847635427892118extract/lib/jruby-stdlib-1.7.1.jar!/META-INF/jruby.home/bin/jruby ... ``` I promised this on #128 thus here it is, hopefully others will find this useful even as is ...

kevin · January 25, 2013, 6:15pm

The wabler-exec gem might be of help:
warbler-exec | RubyGems.org | your community gem host, depending on where you want the
compiled assets to be deployed. You might have to hack it a little since
in the current state it just takes the war and unpacks it to a different
path, but in general, there’s no reason why it shouldn’t be possible to
feed it the path to an unpacked war as an option.

Regards
Felix

On Jan 25, 2013, at 5:57 PM, Patrick R. wrote:

out this pull request to warbler and see if it works for you:

java -jar lib/jruby-complete-1.7.1.jar -S
** Execute assets:precompile
/Users/khutson/myapp/target/myapp-1.7.6-SNAPSHOT/WEB-INF/vendor/bundle/jr

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

–
Felix Gilcher
Geschftsfhrer

m. +49 172 840 88 28

asquera GmbH
Ohlauer Strae 43
D-10999 Berlin

AG Charlottenburg, HRB 140808 B
Geschftsfhrung: Felix Gilcher, Florian G.

kevin · January 25, 2013, 7:56pm

That doesn’t address the issue where you have different asset hosts on
each env.

Eg:

cdn-stage.example.com/assets/…
cdn-prod.example.com/assets/…

kevin · January 25, 2013, 6:55pm

You can make the precompiled assets relative which will allow them to
work in any environment by doing something like this:

gist.github.com

https://gist.github.com/atambo/4636450

gistfile1.rb

namespace :assets do
  desc "Make all embedded assets in stylesheets relative paths"
  task :relativize => :environment do
    Dir[Rails.root + "public/assets/*.css"].each do |asset|
      contents = File.read(asset)
      File.open(asset, "w") do |file|
        file.puts contents.gsub("url(/assets/", "url(../")
      end
    end
  end

This file has been truncated. show original

I run rake assets:precompile and then I run assets:relativize and then
when I package my war file it will work for whatever path you put it
under.

kevin · January 25, 2013, 11:05pm

I think the way I would do that would be to just build the war for
staging and build the war for production separately.

kevin · January 25, 2013, 11:12pm

You should make the asset host configurable using an environment
variable or a system property or use another mode of deployment that
doesn’t use wars.

Wars are not really meant to be changed or partially deployed.

Regards,
Florian

kevin · January 26, 2013, 1:11am

That could work, but asset pre-compilation is expensive. Our build
servers
currently generate the war on every commit to master, compiling the
assets
twice (once for test and once for stage) would add significant time to
the
build process.

What we are trying to do is disconnect asset compilation from the war
and
move it elsewhere in our deploy process.