public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Glenn Strauss <gs-cygwin.com@gluelogic.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Questions on how to upgrade Apache
Date: Thu, 8 Apr 2021 14:33:25 -0400	[thread overview]
Message-ID: <YG9MdTOpcu6Rr+tA@xps13> (raw)
In-Reply-To: <38c22f36-f199-d9f5-e39e-8c5d5b7e48b1@gmail.com>

On Thu, Apr 08, 2021 at 11:37:13AM -0500, René Berber via Cygwin wrote:
> On 4/8/2021 10:49 AM, Andy Romens via Cygwin wrote:
> 
> > Is there something else Cygwin provides that I should use instead of
> > Apache? Sorry for the elementary questions, I’m still quite new to
> > this :)
> 
> 
> nginx is an alternative (NGINX Open Source. The open source web server).
> 
> Cygwin is at version 1.14.2, current version is 1.19.9 (there's a Windows
> binary at nginx.org).

lighttpd is also an alternative and is kept up-to-date in Cygwin by the
upstream lighttpd maintainer (me)

https://www.cygwin.com/packages/summary/lighttpd-src.html

Latest lighttpd release is lighttpd 1.4.59.
Latest lighttpd available in Cygwin is lighttpd 1.4.59.

Cheers, Glenn

  reply	other threads:[~2021-04-08 18:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 20:34 Andy Romens
2021-04-06 20:37 ` Andy Romens
2021-04-08  5:30 ` Andrey Repin
2021-04-09  0:26   ` Brian S. Wilson
2021-04-08 13:22 ` Andy Romens
2021-04-08 14:33   ` Stephen John Smoogen
2021-04-08 15:49     ` Andy Romens
2021-04-08 15:57       ` Eliot Moss
2021-04-08 16:37       ` René Berber
2021-04-08 18:33         ` Glenn Strauss [this message]
2021-04-08 19:53   ` bzs
2021-04-09  6:23     ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-04-09  9:08 ` Csaba Raduly
2021-04-09 11:59   ` Brian S. Wilson
2021-04-09 14:46     ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YG9MdTOpcu6Rr+tA@xps13 \
    --to=gs-cygwin.com@gluelogic.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).