I have made this project (Docker For LAMP
) publically available on Github, under the MIT license.
The target user group is php developers who want or need a simple, minimal (yet very current) LAMP development environment. I want this to be friendly to new developers, and a useful alternative to localhost environments like xamp, mamp or wamp.
Ideally it offers the type of convenience and isolation of a vagrant lamp environment except with orchestrated containers.
Continue reading "docker4lamp - A LAMP Docker development environment"
Certainly the most convenient way to develop a Symfony 5.x app is to use the symfony server. Eventually however, you may have to deploy the application. For a number of years nginx with php-fpm was the preference for many sysadmins seeking to wring the maximum performance out of a webserver that also has to run php scripts, but there are now simple ways of configuring apache to use php-fpm while achieving comparable performance to nginx.
For example a vhost setting like this one is possible:
Continue reading "Symfony 5.2 and Apache 2.4"
SetEnv ENVIRONMENT "dev"
# for Unix sockets, Apache 2.4.10 or higher
# Proxy .php requests to port 9000 of the php-fpm container
DirectoryIndex index.php index.html
Options Indexes FollowSymLinks
Require all granted
# Send apache logs to stdout and stderr
CustomLog /proc/self/fd/1 common
So you have a private Bitbucket Repo and you want to utilize it in your project composer.json
. You may find that when you run the composer install you get an error pulling your private Bitbucket repo with messages about Oauth failure that may include "Invalid OAuth consumer provided
Continue reading "Composer install of Private Bitbucket VCS "aka" 'Invalid OAuth consumer provided'"
is a simple self contained Markdown html renderer and server from developer Andreas Koch, that is written in Go.
You could certainly install Allmark locally, but there are numerous editors or standalone operating system specific markdown parsers you could use.
But what if you have some markdown documentation on a server, and need a quick and easy way to access that documentation? You can always just look at the raw markdown using vim, but what fun is that?
Allmark is a full markdown server, but installing a server just to read a couple of markdown documents is something very few people would want to do. If however, your server has docker installed, you can be reading your documentation in all its rendered glory in a matter of a few seconds. Here is how:
Continue reading "Howto serve a markdown document"
As more and more people utilize virtualization for development the need to easily and securely share your work in progress with team members or clients can be a great boost to productivity. Such a tool is also not bad when your kid wants to let his friend access that local minecraft server you are running on your workstation for him
, not that I would know anything about that. There are several utilities that are available, and now a plug and play option that is available if you use vagrant.
In recent versions of Vagrant, Hashcorp has added a plugin called Vagrant-share. You can see if its installed by running
vagrant plugin list
And you should see something like this:
vagrant-share (1.1.9, system)
Continue reading "Vagrant Share and Ngrok"
In this article I'm going to go over some of the details of how Apache works, and uses memory. As you will see, the apache processes that serve requests will grow to include the amount of memory they need for a particular request, and they will still be using that memory, even when they are serving something simple like a .css file or an image.
For this reason, the first limitation you are likely to encounter running Apache is a limitation on memory. I will explore this topic and show you how you can do the same.
The first thing need to determine about Apache is what mode it is running in. If your plan is to use Apache with php via mod_apache, then the prevailing wisdom for many years has been that there may be library extensions in PHP that are not thread safe. For this reason, people have tended to avoid running Apache as a threaded server, for fear that scripts may randomly die producing the dreaded 500 Internal server error pages we all know and love.
This fear may be overstated depending on the nature of your php code, but the defaults for apache packages I've seen, seem almost always to be using the prefork worker.
Prefork vs Worker?
So the first question you might be asking yourself is, which mode is my current apache server running in? There is a simple safe way to determine this -- run the httpd(apache) program with a specific command line switch. There are programs like which and whereis that might help you locate it, if you don't know where it is.
httpd: /usr/sbin/httpd.worker /usr/sbin/httpd /usr/sbin/httpd.event /etc/httpd /usr/share/man/man8/httpd.8.gz
So let's run the /usr/sbin/httpd with the -h for help and see what happens:
Continue reading "Putting Apache on a diet - how to get a lean configuration, Part 1"