On Tue, Jul 23, 2013 at 09:29:29PM +0200, Arno Töll wrote:
Hm, how do you deal with the conf.d vs. conf-available change and the
completely different maintainer script actions?
there are several possibilities, but I suggest something like [1] which
I wrote for that purpose.
Hi Arno, I
On Mon, Jul 22, 2013 at 10:38:00PM +0200, Arno Töll wrote:
Unfortunately there is no discussion on how to reload the apache
configuration?
I guess the right thing here is to use `invoke-rc.d apache2 reload` as per
the usual for init stuff.
Please refrain to interface with the web
Hi,
On 23.07.2013 10:16, Sebastian Tramp wrote:
Hi Arno, thank you for clarifying this.
Is there a similar document for apache 2.2 ?
you can stop worrying about Apache2 2.2 right now. Any new package you
are going to upload will go through Sid into Debian which will have
Apache 2.4 only.
That
Arno Töll schrieb am Tuesday, den 23. July 2013:
Hi,
On 23.07.2013 10:16, Sebastian Tramp wrote:
Hi Arno, thank you for clarifying this.
Is there a similar document for apache 2.2 ?
you can stop worrying about Apache2 2.2 right now. Any new package you
are going to upload will go
Alexander Wirt formo...@formorer.de writes:
Arno Töll schrieb am Tuesday, den 23. July 2013:
you can stop worrying about Apache2 2.2 right now. Any new package you
are going to upload will go through Sid into Debian which will have
Apache 2.4 only.
To be honest: I don't think thats true. As
On Tue, 23 Jul 2013, Russ Allbery wrote:
Alexander Wirt formo...@formorer.de writes:
Arno Töll schrieb am Tuesday, den 23. July 2013:
you can stop worrying about Apache2 2.2 right now. Any new package you
are going to upload will go through Sid into Debian which will have
Apache 2.4
Alexander Wirt formo...@formorer.de writes:
On Tue, 23 Jul 2013, Russ Allbery wrote:
You pretty much have to branch to support both. The packaging is
substantially different.
I have several packages working well for 2.2 and 2.4. At least for
webapps, it is possible.
Hm, how do you deal
Hi,
On 23.07.2013 20:08, Russ Allbery wrote:
Hm, how do you deal with the conf.d vs. conf-available change and the
completely different maintainer script actions?
there are several possibilities, but I suggest something like [1] which
I wrote for that purpose.
[1]
Arno Töll a...@debian.org writes:
On 23.07.2013 20:08, Russ Allbery wrote:
Hm, how do you deal with the conf.d vs. conf-available change and the
completely different maintainer script actions?
there are several possibilities, but I suggest something like [1] which
I wrote for that purpose.
Hi Debian Mentors,
can you give me some good example packages which demonstrate how to package web
applications. Esp. I am interested in how / and when to restart the Apache
after installation.
Currently I am doing something like
if [ $1 = configure ] ; then
invoke-rc.d apache2 restart
fi
This is what I would do: add a script (or use the existing one for
your framework) to the package that the sysadmin can run that sets up
an instance of the app under a sysadmin-chosen URL with
sysadmin-chosen filesystem/database storage.
Some more links about this topic:
On Mon, Jul 22, 2013 at 11:47:13AM +0200, Paul Wise wrote:
Paul, thank you for the links.
Unfortunately, webapps-common looks very unmaintained.
In 5.1.2 Registering and unregistering an application with web servers of the
webapps-common documentation [1] there is the hint to create apache
http://wiki.debian.org/Apache/PackagingFor24
On Mon, Jul 22, 2013 at 6:49 AM, Sebastian Tramp
tr...@informatik.uni-leipzig.de wrote:
On Mon, Jul 22, 2013 at 11:47:13AM +0200, Paul Wise wrote:
Paul, thank you for the links.
Unfortunately, webapps-common looks very unmaintained.
In 5.1.2
On Mon, Jul 22, 2013 at 1:49 PM, Sebastian Tramp wrote:
Unfortunately, webapps-common looks very unmaintained.
Sadly that is true, you might want to help out with it.
Unfortunately there is no discussion on how to reload the apache
configuration?
I guess the right thing here is to use
Sebastian Tramp tr...@informatik.uni-leipzig.de writes:
In 5.1.2 Registering and unregistering an application with web servers
of the webapps-common documentation [1] there is the hint to create
apache config files in /etc/PACKAGE/xxx.conf and symlink it to the
conf.d directory of the apache.
Hi,
On 22.07.2013 22:02, Paul Wise wrote:
Unfortunately there is no discussion on how to reload the apache
configuration?
I guess the right thing here is to use `invoke-rc.d apache2 reload` as
per the usual for init stuff.
Please refrain to interface with the web server directly when
16 matches
Mail list logo
