Yeah, I guess we could do this better.  This was just a little one-off.  I
say we go with this since it's easy.


On Mon, Feb 4, 2013 at 8:25 AM, Joe Blaylock <notifications@github.com>wrote:

> In chef/cookbooks/class2go-dbdump/templates/default/proddump-daily.sh.erb:
>
> > +if [ -e $zipfile ]; then rm $zipfile; fi
> > +zip $zipfile $dumpfile
> > +
> > +cd ~
> > +
> > +dumplink=proddump-latest.sql
> > +if [ -e $dumplink ]; then rm $dumplink; fi
> > +ln -s /mnt/$dumpfile $dumplink
> > +
> > +ziplink=proddump-latest.sql.zip
> > +if [ -e $ziplink ]; then rm $ziplink; fi
> > +ln -s /mnt/$zipfile $ziplink
> > +
> > +cd /mnt
> > +
> > +AGE=2
>
> I guess it makes sense to do this here since you're doing a fair bit of
> other custom stuff, but my sysadmin training wants me to say we should use
> logrotate to handle log file aging and archival (after all, a DB dump is
> just a really, really, detailed log...) That would let us encode all the
> information about what we're doing with all our logs in one place, without
> having to write a lot of custom recipes for chef.
>
> Unless you think that the log situation needs addressing, though, I don't
> think that should hold this up.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/Stanford-Online/class2go/pull/2116/files#r2878405>.
>
>