Process check: Spreading the Caddy Word

[basil (Basil Hendroff)]

A request has been submitted to the WP doc team. See Using Caddy to Give WordPress Its Own Directory · Issue #332 · WordPress/HelpHub · GitHub

A related issue…

@basil

I also notice there is the (one and only!) WordPress reference to Caddy in the permalinks article. This extract…

Pretty permalinks are available under:

• Apache web server with the mod_rewrite module
• Nginx using try-files, e.g. according to this tutorial
• Hiawatha web server with UrlToolkit support enabled.
• Lighttpd using a 404 handler or mod_rewrite
• Caddy using rewrite, e.g. according to this tutorial

Clicking the link to the tutorial takes me to a Caddy V1 article.

As the link refers to a Caddy V1 article, and as Caddy V1 is now obsolete, I’d like to get this bullet point changed This is what I’m proposing as the replacement text:

Pretty permalinks are available under:

• Caddy automatically in a default WordPress installation.

Just further down in the WP article, in the section Using “Pretty” permalinks, add the following bullet point:

• For Caddy, a web server that supports HTTPS natively, the rewrite rule may need to be adjusted if WordPress files are moved to a subdirectory. Refer to Using Caddy to give WordPress its own directory for details.

If you can improve on this wording, please have a go. I’ll submit a change request with issue #332.once we have agreement on the wording.

The draft wording is based on these follow-up comments from @francislavoie and @Whitestrake…

@francislavoie

@basil

Does this mean I shouldn’t have to take any further action i.e. the permalinks issue should inherently be addressed in Caddy V2? If so, ideas on how to proceed from here e.g. debug?

Hopefully. I don’t use WordPress so I can’t say for sure. You’ll have to try it to find out.

@Whitestrake

@francislavoie

The php_fastcgi directive should already be doing that for you though.

This part:

	# If the requested file does not exist, try index files
	@indexFiles file {
		try_files {path} {path}/index.php index.php
		split_path .php
	}
	rewrite @indexFiles {http.matchers.file.relative}

Might need to be overwritten in this case as we’ve put the main site in an arbitrary subdirectory. e.g.

try_files {path} {path}/index.php /my_subdir/index.php