FWIW, I went another way here - with apache. Rather than pegging the
container to apache running, I used Kubernetes to health check the app, and
simply catted out the log files to stdio. It's not really the "docker-way"
of one process per container, but it's working pretty well.
The idea was
/rails.conf
-DFOREGROUND -DNO_DETACH
AH00534: apache2: Configuration error: No MPM loaded.
On Sun, Oct 25, 2015 at 5:03 PM, Kurtis Rader <kra...@skepticism.us> wrote:
> On Sun, Oct 25, 2015 at 3:55 PM, David Aronchick <aronch...@gmail.com>
> wrote:
>
>> Is it possi
Is it possible (or inadvisable) to run apache using the /usr/sbin/apache
binary directly? Is there any significant production issues that might
arise?
On Sun, Oct 25, 2015 at 3:26 PM, David Aronchick <aronch...@gmail.com>
wrote:
> I appreciate your feedback. I apologize for providing a
p to nginx.
Thanks everyone for the help!
On Sun, Oct 25, 2015 at 8:43 PM, Kurtis Rader <kra...@skepticism.us> wrote:
> On Sun, Oct 25, 2015 at 8:17 PM, David Aronchick <aronch...@gmail.com>
> wrote:
>
>> Thanks for all the help all! I dug into the apachectl and realized I
-DFOREGROUND -DNO_DETACH
On Sun, Oct 25, 2015 at 7:32 PM, Yehuda Katz <yeh...@ymkatz.net> wrote:
> You could try starting the service and run "ps auxf | grep apache".
> This doesn't always give you all the information, but it could help.
>
> - Y
>
> On Sun, Oct 25,
can't figure out
why. Thanks again all!
On Sun, Oct 25, 2015 at 7:52 PM, Kurtis Rader <kra...@skepticism.us> wrote:
> On Sun, Oct 25, 2015 at 7:26 PM, David Aronchick <aronch...@gmail.com>
> wrote:
>
>> Thank you, this is very helpful! Is there any way to get an
before, but had not tried -DNO_DETACH. I'll do
that.
On Sat, Oct 24, 2015 at 9:11 PM, Kurtis Rader <kra...@skepticism.us> wrote:
> On Sat, Oct 24, 2015 at 3:35 PM, David Aronchick <aronch...@gmail.com>
> wrote:
>
>> I understand it's not a best practice to run Apach
I understand it's not a best practice to run Apache in single process mode
for most situations, but what about inside a Docker container?
My goal is to have the logs & errors output to stdio/stderr, and to have
the entire container get killed if the process dies.
Hi--
I'm trying to use httpd in a Docker container. As a general rule, I'm
trying to write the access error logs to stdio and stderr instead of
writing them to disk. Is there a best practice here? I've tried posting to
stackoverflow, and the best idea given was creating a symlink in the