On Sep 6, 2006, at 2:50 PM, Peter Michaux wrote: > On 9/6/06, John Clayton <[EMAIL PROTECTED]> wrote: > >> We certainly could do that, and if we decide to use the engines >> approach, may have to. > > But you won't be able to stay up-to-date very easily. For example, > when the recent Rails core security issue came up the engines plugin > had to be modified. So you would be driving home to email your self a > copy of the updated version. Seems like a pain.
Very true and a concern. > > >> Anyway, just from a practical standpoint, I'd still like to find a >> non-subversion way to capture official releases. Might be as simple >> as requesting they be posted as tarballs ... > > I think it is practical to have SVN installed on your computer if you > are in the Rails world. That way you can do this stuff without > spending any time worrying about it. Just "svn export" and you are > finished. Is there some sort of security problem you are worried about > by having and SVN client on your computer? I guess we could keep a plugin repository using subversion and keep that up to date, but we'd then have to suck changes into our working SCM, darcs. Which might not be too too bad. > > >> Thanks for the suggestion though, seriously. > > It's a way to get started anyway. Engines are very cool. They are. The only thing that bothers me is that we are looking for a way to host multiple sites on one physical app, which we are thinking of deploying as an engine to a bunch of application stubs. I'm not sure we're using Engines in the right way here, but it would probably beat dynamically switching the database connection, etc. Although, since we'll probably use mongrel or some other container mechanism, we'd only have to do that once ... so maybe engines are the wrong choice for us. Still trying to figure that out. > > Peter > _______________________________________________ > engine-users mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-users-rails- > engines.org _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
