| 1 |
On Monday 13 of June 2011 11:35:08 Patrick Lauer wrote: |
| 2 |
> On 06/13/11 01:44, Maciej Mrozowski wrote: |
| 3 |
> > On Friday 10 of June 2011 20:08:00 Ciaran McCreesh wrote: |
| 4 |
> >> On Thu, 9 Jun 2011 16:37:46 -0500 |
| 5 |
> >> |
| 6 |
> >> Matthew Summers <quantumsummers@g.o> wrote: |
| 7 |
> >>> After consultation and discussion at length with several developers, I |
| 8 |
> >>> am writing to announce the impending revival of the tool known as |
| 9 |
> >>> app-admin/webapp-config effective immediately. |
| 10 |
> >> |
| 11 |
> >> You might want to chuck it out and start from scratch... |
| 12 |
> >> |
| 13 |
> >> Much of the difficulty with the original webapp-config was that it was |
| 14 |
> >> designed to work on Windows. Stuart's plan was to create a distribution |
| 15 |
> >> and operating system independent way of dealing with web apps, sort of |
| 16 |
> >> like CPAN; Gentoo was merely the testbed. If your goals don't match |
| 17 |
> >> that, you're probably better rethinking everything than trying to revive |
| 18 |
> >> something that was designed for a completely different purpose. |
| 19 |
> > |
| 20 |
> > Also, for pure Gentoo needs it may be better to replace webapp-config |
| 21 |
> > with package manager and eclasses. |
| 22 |
> |
| 23 |
> How does that handle multiple installs etc.? |
| 24 |
|
| 25 |
Multiple version installs? Package slotting could be utilized. |
| 26 |
If multiple instances of the same version - of course it doesn't but nothing |
| 27 |
prevents you (or eclass - pkg_config() phase) from creating apache config for |
| 28 |
each virtualhost (for instance) you want particular webapp served. It's not |
| 29 |
like one really needs to bluntly copy webapp code to deploy it multiple times, |
| 30 |
usually it's sufficient to fiddle with <DocumentRoot/> and <Directory/>. |
| 31 |
Sometimes patches are needed of course. |
| 32 |
|
| 33 |
> > So to install web apps to /usr/share or sth and provide apache config |
| 34 |
> > files to set up those webapps like Debian does for instance |
| 35 |
> |
| 36 |
> ZOMG NOES. |
| 37 |
> That stuff is horrible, it randomly patches the webserver config |
| 38 |
> wrongly, then restarts the webserver - so installing nagios knocks out |
| 39 |
> your apache. Which then makes for some funny debugging ... |
| 40 |
> |
| 41 |
> Let's aim higher than that, please, I don't want random misbehaviour :) |
| 42 |
|
| 43 |
I forgot the word 'Debian' triggers some unhandled exceptions within your |
| 44 |
processing queue ;) |
| 45 |
Seriously, Debian-way of handling web apps isn't bad at all from my experience |
| 46 |
(I'm not sysadmin however, I just happened to maintain a few web/dev servers), |
| 47 |
certainly better out-of-the-box experience and better organized than what we |
| 48 |
have IMHO (save webapp-config). |
| 49 |
|
| 50 |
As for httpd service auto restarts - I believe that was never suggested for |
| 51 |
Gentoo anyway, just "a bit Debian-like" apache config layout - bug 296271. |
| 52 |
|
| 53 |
> - so dispatch-conf would be |
| 54 |
> |
| 55 |
> > utilized for tracking config file modifications and uninstall via unmerge |
| 56 |
> > |
| 57 |
> > One major obstacle is that we have quite a number of web servers to |
| 58 |
> > support if we're to provide out of the box experience for those web |
| 59 |
> > apps. |
| 60 |
> |
| 61 |
> So provide a default config for, say, apache, and then figure out if |
| 62 |
> that can be transcribed to others easily. Maybe it can be turned into |
| 63 |
> simple templates to generate all configs from? |
| 64 |
|
| 65 |
-- |
| 66 |
regards |
| 67 |
MM |
Archives