[Demi-devel] Screen shots

[John Morrissey]

On Tue, Mar 08, 2005 at 08:12:29AM +1100, Andrew Pollock wrote:
> so we'd have a "demi" account, which the central server uses to SSH in and
> retrieve the status file, as well as upload new .debs to. A cron job could
> then check for the presence of a command file telling it what to do.

Interesting... I'll start working in that direction, since I like that idea
better. Could I get access to the Alioth svn repo for Demi so I have an
externally-accessible place to put this once it's in a more releasable
state?

> > The only major difference is placing the package (plus dependencies) in
> > /var/cache/apt/archives/ so it's already downloaded on the client. I
> > admit I'm biased on this, since our machines have access to a local
> > mirror.
> 
> Well that's not a lot different to using cron-apt on the client, with a
> pretty web interface showing central version levels (which isn't a bad thing
> I might add).

The thing we're looking for immediately is a centralized place to check
patch levels and apply patches to groups of machines (or perhaps execute
commands) at once without having to log in to them individually. I see your
point about a pretty GUI on cron-apt, but cron-apt is really a big
sledgehammer when it comes to installing new packages. A central interface
like Demi is more like a scalpel.

john
-- 
John Morrissey          _o            /\         ----  __o
jwm@horde.net        _-< \_          /  \       ----  <  \,
www.horde.net/    __(_)/_(_)________/    \_______(_) /_(_)__