Bitrix from a hosting archive: 404 or 502, urlrewrite dead

I unpacked a client Bitrix into www/shop — exactly the Herd gap I care about. I created a project: home is blank or 502, admin will not open. Production is Apache with .htaccess. Does Native nginx read that?

No. Native nginx does not read .htaccess. Unlike a naive MAMP drop-in, MacFullStack finds the real root (the folder with bitrix/ and upload/, not Laravel public/) and writes rewrite/security equivalents into the vhost. A hosting archive is a first-class path, not “our templates only”.

Do this:

1. On the project card check docroot — Bitrix root, not a neighbour public/.
2. More → Bitrix check (if present) and Diagnostics → Sync vhosts.
3. Pin PHP to production (often 8.1–8.3).
4. Import .sql by dropping it on the project list; in dbconn.php / .settings.php use 127.0.0.1, user macstack / macstack (port from Stack, not always 3306).

Custom Apache modules from prod will not appear by magic. Odd rewrites go in .macstack/nginx.conf without listen/root/ssl.

One site like this can run on Free. Several client Bitrix trees in parallel — Pro.

Help: /help/docroot, /cms.