fix: support image processing on CPUs without x86-64-v2
Some checks failed
Test and deploy / Verify production build (push) Failing after 15m8s
Some checks failed
Test and deploy / Verify production build (push) Failing after 15m8s
This commit is contained in:
@@ -57,6 +57,11 @@ Drizzle Kit, npm installs, or a compiler at runtime. Startup applies the committ
|
||||
SQL migrations and seeds samples only when the database is empty. `/api/health`
|
||||
checks database readiness without rendering the portfolio.
|
||||
|
||||
Sharp uses native image processing where supported and includes a WebAssembly
|
||||
fallback for servers without the required x86-64 CPU features. The fallback
|
||||
preserves uploads and image optimization, but can use more CPU time. Keep
|
||||
`@img/sharp-wasm32` at the same version as `sharp` when upgrading.
|
||||
|
||||
Use one application instance with a local filesystem. Do not mount the SQLite
|
||||
database over NFS/SMB, use an ephemeral serverless disk, or run multiple replicas
|
||||
against the same data volume. PostgreSQL would be the next step if those become
|
||||
|
||||
Reference in New Issue
Block a user