Update readme in preparation for next caddy release

[elee1766]

In future versions of caddy, filesystems have been changed to be declared in the global block, then referenced using the fs directive, see caddyserver/caddy#5833

this is a breaking change, see #288

it shouldn't break the actual plugin (if it does, let me know, and i can investigate), but the readme should be updated.

also probably shouldn't merge until the next official caddy release.

[sagikazarmark]

@elee1766 thanks for the PR!

Since this change isn't released yet, would you mind adding back the original example with a note that prior to 2.8.x the old configuration has to be used?

We can remove it once 2.8+ becomes the standard, but until then, I think it would be confusing for people to have an unreleased version config in the docs.

[elee1766]

yeah that makes sense. i was just going to leave this pr until the new caddy release but this makes more sense

[tetra12]

We can remove it once 2.8+ becomes the standard, but until then, I think it would be confusing for people to have an unreleased version config in the docs.

@sagikazarmark You should create a new branch like caddy v2.8.0, update docs properly and add a note that it will be merged to main when caddy v2.8 arrives

Now my issue is fixed thanks to @elee1766 and I can build your module against caddy master

[sagikazarmark]

This just documentation, so I’m satisfied with the current version.

[srenatus]

Five months later, I ran into this problem 😅 Thanks for helping me out indirectly here! 🥳