RE: Use cases question

> > I've used markive but it's been a while since I played with
> > moto. I'm looking into a bit more and have a few uses case=20
> questions.
> >=20
> > 1)If I remember right after you install it you can have a
> > .moto file that is plaiin text and it gets interpreted each=20
> > time it's run correct?
> >=20
> > If I want to compile one or more .moto files I can folow the
> > instructions at http://projectmoto.org/usecases.moto
> >=20
> > My questions are:
> > On number 1 it says:
> > Take the compiled website (mod_sitename.so) and install it in
> > the libexec directory of your apache installation. Restart apache...
> >=20
> > 2) So if I move the .so file to the proper directory it will
> > just work, withotu modifying httpd.conf ??
>=20
> 2.1) And how would you make a url to that mod_*****.so=20
> website, simply the http://domain.com/ ?

2.2)=20
I wonder if there is a way to set up apache so that if the user put a =
directory called moto-bin/ in the public_html directory and put their =
mod_****.so in it that it would work the same way. That way users can =
use jail shell to create moto.so and use them. If possible we'd need a =
way that wouldn't break apache if they did something wrong.

>=20
> >=20
> > On number 2 it says:
> > Take the compiled application and distribute it online or
> > burned on a cd without giving away the source code. Users,=20
> > customers, clients will not even need moto or any other third=20
> > party 'runtime' environment to run it.
> >=20
> > 3) So how would I execute it as a program?
> >=20
> > 4) The mmc comands looked identical pretty much, so how does
> > it know if I want a mod_*****.so for apache or just a plain=20
> > standalone prog? (***** instead of mod_*****.so)
> >=20
> > TIA
> >=20
> > Dan
> >=20
>=20