Re: [gentoo-soc] Online image builder

[Eitan Mosenkis]

Perhaps PHP for frontend and PHP + Bash for backend?  That way the project
all gets done essentially in one language and any person qualified to do one
piece knows the language used for the other - PHP has had a lot of changes
in the last year or so to make it usable as a non-web-based scripting
language.
As for IPC, I think I'd store the user's choices in a database, which allows
user preferences to be reused and shared, etc., and then the frontend would
really just need to be able to ping the backend when it wanted it to get to
work (the backend can optionally either send notifications itself or ping
the frontend to do it).  Since all of the data should really be stored for
future use (and purged after enough time passes), I see no point in sending
much besides simple signals through IPC.  Might as well just use the
database for all the data.

Make sense?

On Mon, Mar 16, 2009 at 2:29 PM, Luca Barbato <lu_zero@g.o> wrote:

> On 16-03-2009 10:33, Eitan Mosenkis wrote:
>
>> Hi.
>> I already emailed a bit about the idea with the potential mentor (solar),
>> but I thought I'd say hi here on the mailing list too, since I don't
>> expect
>> to have too much time before applications start going in to hang around
>> the
>> IRC channel.
>>
>> The way it looks to me, I'd like to implement the frontend in PHP.  The
>> first stage would be getting a functional frontend and backend (I might do
>> that in PHP for code reusability between the two parts, but the backend
>> language doesn't seem to really matter because it will really just be
>> deciding which helper programs to invoke) that is usable to generate an
>> image for the requested arch and with a few choices about packages
>> installed, etc.
>>
>
> Please make the backend use a language among those used by the tools you
> are already supposed to install (say bash, python and C).
>
> You may consider using a json or xml rpc (check libxr).
>
> lu
>
>