Boot.lisp -- where is the bootstrap code in the repo?

[A.J. Rossini]

Sean -

Does the repo have the pieces to create the WWW system? (i.e. I can't
tell right now how to create boot.lisp or if there is a support system
for the repo)?

I've been walking through the code, and have a bit more understanding
-- would you prefer that I fork the github code (on github), or could
you just add blindglobe to the list for the mudballs related repos?

Also, are you wedded to the idea of mudballs.com, or making a more
portable framework that could be deployed on common-lisp.net or
similar?

best,
-tony

blind...@gmail.com
Muttenz, Switzerland.
"Commit early,commit often, and commit in a repository from which we
can easily roll-back your mistakes" (AJR, 4Jan05).

Drink Coffee: Do stupid things faster with more energy!

[Sean Ross]

On 29 Jul 2009, at 06:42, A.J. Rossini wrote:

>
> Sean -
>
> Does the repo have the pieces to create the WWW system? (i.e. I can't
> tell right now how to create boot.lisp or if there is a support system
> for the repo)?
>

Hi A.J.

boot.lisp is pretty static file and is meant to remain relatively
unchanged over time, the other
parts of the WWW system are the html files, the various tarballs of
systems and the system definition
files. The tarballs of systems sit in a git repository in my home
directory which is symlinked into the apache
path and are provided to the mudballs download code through an apache
rewrite rule.

I use release-action to create tarballs of systems to be released and
then mudballs-presenter to add the tarball and definition
to the cloned github repository on my machine which I then push to
mudballs.com.
Mudballs presenter then has a release-sydef-file function which
generates the sysdef file, which I test on my machine and
then push out.

> I've been walking through the code, and have a bit more understanding
> -- would you prefer that I fork the github code (on github), or could
> you just add blindglobe to the list for the mudballs related repos?
>

I'm fine either way, although a fork might make it more clear that I
am no longer
contributing.

> Also, are you wedded to the idea of mudballs.com, or making a more
> portable framework that could be deployed on common-lisp.net or
> similar?
>

No, I'm not wedded to mudballs.com at all (IIRC the domain actually
expires in a couple of months)
and a more portable system would make a lot of sense.

- Sean