Re: New stable release coming up.

On Sat, 1 Feb 2003, Wari Wahab wrote:
> 
> will wrote:
> > 
> >Um...  I don't know if I would run my blog off of my CVS directory.  I 
> >would think you'd want a step between you and CVS in case someone drops 
> >something in that causes things to break.
> >  
> I'm with running things from CVS, infact I would know if something is 
> wrong from the CVS copy immediately :)

I think you guys are crazy.  I've done development for a long time and it
just seems silly to me not to have that additional buffer between your
"production" code and your "development" code.  Though I guess these are
just weblogs, so it probably doesn't matter so much.

I wrote a script to backup files on my web-site and then copy things from
my pyblosxom CVS directory over to my web-site.  I run it only after I've
had time to read the checkin comments and diff.


> >Then you can have changes in your blog system and not have to worry about 
> >accidentally commiting those to the repository.
>
> There are always some precaution to check with, like doing a diff, see 
> if there are your changes. Also always make sure you do a cvs update -d 
> before doing a commit, which my colleague paid for his mistake doing so 
> (loosing a couple of weeks work).

Exactly.  Though like I said, these are just weblogs, so maybe it doesn't
matter so much to you all.

I use my weblog walks through the status on the projects I'm working on
and I know people check it frequently enough that if my weblog were to
become non-operational for a few hours, it'd be a pain.

(shrug)

I'd be up for Ted's idea for using defaults and then an example-config.py.  
Though I should note that if you add a:

   sys.insert(0, "/path/to/dir/with/config/")

to the top of your pyblosxom.cgi script, then you can put your config.py 
wherever you like as well.

/will


-- 
whatever it is, you can find it at http://www.bluesock.org/~willg/
except Will--you can only see him in real life.