Peter Bex wrote: > On Mon, Aug 27, 2007 at 01:39:35PM +0200, Bart Duchesne wrote: > >> Well I added an option to the engines plugin to symlink the public files >> instead of copy them. So I added Engines.symlink_asset_files boolean to >> the module and used it in the >> Engines.mirror_files_from. >> In development mode I want to symlink (because some of the plugins I'm >> developing contain assets that get modified during the development >> process of the main application), in production mode I want to copy >> that's why I wanted to change the setting in config/environment. >> Maybe there is another way of achieving what I want; basically I want to >> have full flexibility in development mode with as least restarting as >> possible. Is it possible to execute mirror_plugin_assets before every >> request get's handled in development mode ? >> > > This sounds rather overcomplicated to me. I use symlinks too, and this works > fine even without making any configuration changes. Maybe I'm > misunderstanding > what you're trying to do, but I'll explain how I do it: > > If I have a project called 'myproject', in my plugin_assets directory I > create a symlink by that name to the assets directory in the plugin: > $ cd public/plugin_assets > $ ln ../../vendor/plugins/myproject/assets myproject > > There's no need to do anything more than this, afaik. > :-[ You're right; shame on me; things can really be simple sometimes ...
thx Bart _______________________________________________ Engine-Users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
