The "What to fix" page
The "What to fix" page turns a scan into a to-do list. Instead of hunting through a hundred results, you get one page that answers three questions in the order you actually ask them: what to change, what your server needs against what it has, and which credential comes from where.
What to change
One card per setting that needs attention. Each card shows what it is set to now, what it should be, which file it lives in, and what it costs your shop to leave it alone — ordered so the things that can stop orders come first.
Every value you would otherwise copy by hand sits behind a button. Show me every line to paste opens one block per destination file, holding only the lines that still need changing — because copying twenty values one at a time is how a digit gets dropped partway through. Settings to paste and commands to run are kept in separate blocks, since they go to different places and a block that mixes them is one nobody can actually use.
The database targets on these cards come from the same calculation that produces the paste-ready my.cnf block on the server and configuration guide — so the number on the card and the block you copy can never disagree with each other.
What your server needs, and what it has
The floor 6amMart needs to run at all, what to actually install on a new machine, and what this one has today — side by side, because a bare minimum is the wrong thing to build a shop on.
| Resource | Floor | What to pick |
|---|---|---|
| vCPU | 2 | 4 |
| RAM | 4 GB | 8 GB |
| Free disk | 20 GB | 40 GB+ |
| Storage type | SSD | NVMe |
One thing worth knowing about this table
The requirements table and the hardware check inside the scan disagree slightly on free disk — the requirements table asks for 20 GB, while the disk check itself only warns between 10 and 20 GB and fails below 10. Both numbers are shown on the page rather than picking one, because that is the honest way to report a tool disagreeing with itself. Either way, aim for 40 GB or more and you will never notice the gap.
Keys and credentials
Every value you have to fill in, and which console page it comes from — the part official documentation usually skips. Which Google Cloud screen issues the server key and why it must be IP-restricted while the client key must be referrer-restricted. That your Firebase service account and web config have to belong to the same project, or push notifications silently go nowhere. That Gmail needs an App Password, not your account password.
Full detail on where every one of these comes from lives in the server and configuration guide.
The tuning catalog behind it
Every recommendation on this page is pulled from a shared tuning catalog covering PHP, the web server, the operating system, MySQL, nginx, Laravel and 6amMart itself — around 84 entries.
Roughly 40 of them are safe to apply automatically without asking. The rest are either prompted with the tradeoff stated in one line, or printed as a manual instruction for you to follow.
That same catalog powers the automated setup script — see What the setup script does if you would rather have those changes applied for you than copy them by hand.
Where to go next
- The server and configuration guide — the full version, with setup instructions and where every credential comes from
- What the setup script does — apply these changes automatically instead of by hand