apache-fpm (and probably apache-cgi) webserver_type don't work on windows

[rfay]

Describe the bug
Ooops. We never tested apache-fpm on Windows, (and don't have automated tests yet). And we probably weren't planning on automated tests on Windows for apache-fpm :(

Basically, we generate a username in apache's envvars directory, and it comes out to be uid_0, but we don't have uid_0 in /etc/passwd.

To Reproduce

Try running any project with apache-fpm for the webserver type on Windows. It doesn't work.

Additional context

This can be fixed by just adding uid_0 and gid_0 to the /etc/passwd and /etc/group file, I think.

[outdoorsman]

Just confirming what you've already said here. I'm getting this error in Windows after doing ddev config and setting it to apache-cgi or apache-fpm.

Failed to start test2: web service health check timed out: labels map[com.ddev.site-name:test2 com.docker.compose.service:web] timed out without becoming healthy, status=unhealthy

[rfay]

@outdoorsman Would love to have you test the artifacts for #1111 in https://circleci.com/gh/drud/ddev/3537#artifacts/containers/0

[outdoorsman]

@rfay I installed .exe file in Windows from above and DDEV started successfully, but I still got this error in a TYPO3 6.2 frontend. When I did ddev start I saw this in the output The following packages will be REMOVED: php-igbinary php-memcached php-redis and it appeared to succeed. So not sure why I'm still getting the igbinary error in the frontend. I haven't tried doing it manually yet, but I'm aware of that issue as I've had to do this manually before.

#1: PHP Warning: igbinary_unserialize_header: unsupported version: "O:44"..., should begin with a binary version header of "\x00\x00\x00\x01" or "\x00\x00\x00\x02" in /var/www/html/example.com/typo3_src-6.2.31/typo3/sysext/core/Classes/Cache/Frontend/VariableFrontend.php line 99

[rfay]

Do you have some post-start steps in your config.yaml? Please comment them out for now if you would, and do a ddev rm and a ddev start again.

[rfay]

Wait a minute. TYPO3 6.2? We haven't ever deliberately supported anything before TYPO3 8... ???

[outdoorsman]

Oops, yes this was in config.yaml to probably address the error I was seeing a while back, but apparently it's not quite working so need to do it manually or something. After removing these lines, I did a ddev remove and ddev start again and got the same error.

hooks:
  post-start:
  - exec: sudo apt-get remove --yes php-igbinary

This may just be a TYPO3 6.2 issue as you're pointing out. My personal reason for needing Apache is because I can't get TYPO3 4.5 or 6.2 to run in Nginx and I have ton of these to update still.

[rfay]

Can you point me to some step-by-step instructions on how to do a simple 6.2 project? Maybe you could do one and see if you have this problem on a plain vanilla TYPO3 6.2. Push it to github or give me a tarball? I'll give it a try. But I don't have that much expertise with TYPO3 in general, and certainly not with old versions.