Forum: Rails France Capistrano : cached_externals.

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Jean-François Trân (Guest)
on 2008-11-02 14:47
(Received via mailing list)
Jamis B. vient de publier une extension Capistrano pour gérer
les dépendances externes de son appli.

Bon il explique ça mieux que moi dans le README, extrait :


"This Capistrano extension provides yet another way to manage
your application's external dependencies.

External dependencies are a necessary evil. If you're doing
Rails development, you'll automatically be dependent on the
Rails framework itself, at the very least, and you probably
have a handful or two of plugins that you're using as well.
Traditionally, the solution to these has been to either install
those dependencies globally (which breaks down when you
have multiple apps that need different versions of Rails or
the plugins), or to bundle them into your application directly
via freeze:gems or the like (which tends to bloat your repository).

Now, bloating a repository is, in itself, not a big deal. However,
when it comes time to deploy your application, more data in the
repository means more data to check out, resulting in longer
deploy times. Some deployment strategies (like remote_cache)
can help, but you're still going to be copying all of that data
every time you deploy your application.

One solution is to use a deployment strategy like FastRemoteCache
(http://github.com/37signals/fast_remote_cache), which employs
hard-links instead of copying files. But your deploys will go _even
faster_ if you didn't have to worry about moving or linking all the
files in your external dependencies.

That's where this Cached Externals plugin comes in. It capitalizes
on one key concept: your external dependencies are unlikely to
change frequently. Because they don't change frequently, it makes
more sense to just check them out once, and simply refer to that
checkout via symlinks.

This means your deploys only have to add a single symbolic link
for each external dependency, which can mean orders of magnitude
less work for a deploy to do."

http://github.com/37signals/cached_externals/tree/master

(via Technoweenie)

    -- Jean-François.


--
Les 50 ans de Jeanie Longo : http://www.longo50.org
http://twitter.com/underflow_
This topic is locked and can not be replied to.