I was able to install and configure Caddy with Phalcon3 crazy easily, however, to actually be able to use Phalcon correctly I need to translate a mod_rewrite block to Caddy speak.
@zqueal, Phalcon needs a .so to works, no? Phalcon Framework is a module to NGINX and/or Apache - PHP 5.6 and 7.0… I do not know if works properly with PHP 7.1. Anyway, you need to use Caddy as proxy server first and running Phalcon Framework into NGINX or Apache.
After trying to {path} {path}/ /index.php?_url=/{path}&{uri_escaped} Caddy refused to start under any circumstances no matter what I did–even after reverting the changes in my Caddyfile.
As far as I can tell the string should beto {path} {path}/ /index.php?_url=/{uri} but it simply doesn’t work.
Drop r subdirective. Selecting via regex is unnecessary, and a waste of resources just to match everything (which rewrite does by default, unless you specify a basepath).
Drop ext subdirective. That would cause your rewrite not to work unless the URL has no file extension. It’s not necessary because the first rewrite target is {path}.
Escaped URI is not necessary. Placeholder {uri} includes leading slash, so prepending another is not necessary.
rewrite {
to {path} {path}/ /index.php?_url={uri}
}
Trailing slashes are unecessary? {uri} instead {path}&{query} or {query}? I’m asking because I really do not know the boundaries between one and the other - in practice.