Problems with Sequoia Apache PHP and spaces in directories

kapser

I was previously able to run PHP8.1 etc. with Apache directly from a directory which had couple of spaces in the directory names, but it seems that starting on a fresh computer with Sequoia and reloading the stack breaks the functionality. Local sites display 'File not found' and Apache log displays 'AH01071: Got error 'Primary script unknown'.

Index.html files work as expected so this is only for PHP. Moving the folder to a directory path without spaces in the directory names and adding that directory to Indigo's Apache brings back the functionality, so it seems the spaces are the issue.

The whole thing would not be an issue if I didn't want to run local php from Dropbox (The root folder has spaces for the team folder.), but it would be interesting to know what kind of a bug this is.

Cheers,
Jonatan

kapser

Also a big thank you to the Indigo team. Everything else works like a dream.

Indigo

@kapser thanks for your encouraging words, they go a long way! Regarding the Apache issue, unfortunately it's a known issue, outside of our control. See here for an earlier discussion. The pertinent Apache issue is here.

In your case, I think the most pragmatic solution for now is probably to symlink dropbox into a non-space path eg: ln -s /absolute/path/to/drop box/sites/ /somewhere/without/spaces/sites. Of course you'll have to re-point all your indigo site configurations to the new path which is a hassle, but I do think this should work. Let me know how you go!

kapser

Ah! Interesting. So I'm not alone. Would it make sense to be able to use end of life Apache versions in Indigo as services (similar to PHP)? Thank you for the prompt reply!

Indigo

Your idea is definitely feasible, and the infrastructure can support it. However, it would mean extra maintenance for me, a larger app bundle, and potential confusion for users deciding which version to choose. My hope is that this kind of issue will be very rare, so we can avoid the need to ship two versions of Apache.

I'm hoping the symlink workaround will help until Apache merge the PR that fixes the bug!