[Slackbuilds-users] nginx maintainer

[Doogster]

Where to put the included error pages is a matter of taste. I choose
/var/www/ngdocs; another blogger chose /var/html
(http://zhu-qy.blogspot.ca/2012/11/slackware-14-nginx-fastcgi-php-php-fpm.html).

What's definitely not acceptable is just removing them, which the
current SlackBuild does.

On Sun, Apr 13, 2014 at 12:15 AM, Doogster <thedoogster at gmail.com> wrote:
> The error pages are installed, by default, into /usr/html. The default
> nginx.conf expects to find them there. The current SlackBuild just
> removes this directory. I consider that a problem.
>
> IIRC,if you have an unmodified nginx.conf, then /usr/html is also your
> document root.
>
> On Sat, Apr 12, 2014 at 9:08 PM, Miguel De Anda <miguel at thedeanda.com> wrote:
>> i haven't check the 40x and 50x pages but are you saying the default pages
>> w/o changing the included nginx.conf file? i would agree that this is a
>> somewhat trivial change that doesn't affect the binary or the original
>> source. another option is to correct the shipped nginx.conf to not reference
>> the nonexistent files.
>>
>> it would make sense that a clean build/install of the package should be
>> fully functional. for example, chown'ing log files so the pre-configured
>> runas user can actually write to them instead of leaving it as an
>> undocumented step.
>>
>> -m
>>
>>
>> On Sat, Apr 12, 2014 at 3:40 PM, Doogster <thedoogster at gmail.com> wrote:
>>>
>>> Removing the 40x and 50x error pages is a problem with the SlackBuild,
>>> and it should be fixed.
>>>
>>> The rest of what my patch does is a matter of taste.
>>>
>>> On Sat, Apr 12, 2014 at 2:53 PM, Klaatu <klaatu at straightedgelinux.com>
>>> wrote:
>>> > I hear what you're saying, Doogster, but is that really an issue with
>>> > the Slackbuild? It looks like that is the way Nginx distributes itself,
>>> > and Slack{ware,Builds.org} policy, I believe, is to not change the
>>> > upstream package unless not doing so will result in the thing literally
>>> > not launching or being functional on Slackware.
>>> >
>>> > I realise that you may be making the argument that it is not functional
>>> > without being changed, and I can see what you mean. However, I use Nginx
>>> > on a few different servers, and on one I do change it to match the
>>> > htdocs webroot, but on others I change it to something else entirely.
>>> >
>>> > Bottom line is, if the SBo maintainer patches the config file for me,
>>> > I'm just going to have to unpatch it later to suit however I have it set
>>> > up on any given box.
>>> >
>>> > This is one of the things that drives me nuts about Debian and Red Hat;
>>> > they change the defaults from something I'm going to have to change, to
>>> > something else I'm going to have to change...
>>> >
>>> >
>>> > tl;dr
>>> > Not flaming you or disrespecting your opinion, just wondering if it's
>>> > really correct to patch the config from the point of install, or whether
>>> > a simple note in the README to remind the user "hey! you need to
>>> > configure this!") and maybe even a link to your blogpost so that new sys
>>> > admins might have some sensible example of what a good config would look
>>> > like.
>>> >
>>> > -klaatu
>>> >
>>> >
>>> >
>>> > On 04/13/2014 05:28 AM, Doogster wrote:
>>> >> Hey Larry. There's a pretty serious problem with the current SBo nginx
>>> >> SlackBuild: it removes the 40x and 50x error pages that are supposed
>>> >> to be included. I hope that as the new maintainer, you can address
>>> >> that.
>>> >>
>>> >> My LEMP Howto (http://duganchen.ca/lemp-on-slackware/) has a patch
>>> >> that might give you some ideas.
>>> >>
>>> >> On Sat, Apr 12, 2014 at 10:07 AM, Willy Sudiarto Raharjo
>>> >> <willysr at slackbuilds.org> wrote:
>>> >>>>> I'm interested.... Maintainer is sometimes slow to respond... Might
>>> >>>>> want to
>>> >>>>> wait a few days though.
>>> >>
>>> >> It's been more than a week :)
>>> >> Anyway, Larry Hajali was the first to respond to become a new
>>> >> maintainer
>>> >>
>>> >>
>>> >>>
>>> >>> _______________________________________________
>>> >>> SlackBuilds-users mailing list
>>> >>> SlackBuilds-users at slackbuilds.org
>>> >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> >>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> >>> FAQ - http://slackbuilds.org/faq/
>>> >>>
>>> >> _______________________________________________
>>> >> SlackBuilds-users mailing list
>>> >> SlackBuilds-users at slackbuilds.org
>>> >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> >> FAQ - http://slackbuilds.org/faq/
>>> >>
>>> >>
>>> >>
>>> >
>>> > _______________________________________________
>>> > SlackBuilds-users mailing list
>>> > SlackBuilds-users at slackbuilds.org
>>> > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> > FAQ - http://slackbuilds.org/faq/
>>> >
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - http://slackbuilds.org/faq/
>>>
>>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>>