@piwi maybe we should have a generic Linux deploy guide and link the specific providers to that? In terms of actual Linux implementation almost every cloud VPS is functionally the same (minus AWS and how they handle the root user account).
Keep provider specific guides to just their interface differences
Step 5, can I do it with a build in the folder or do I need to delete the previous build folder?
Got this error:
`$ NODE_ENV=production yarn build
yarn run v1.22.10
$ strapi build
Building your admin UI with production configuration …
[55568:0x586b120] 162309 ms: Mark-sweep (reduce) 488.2 (491.9) → 487.8 (493.6) MB, 1434.5 / 0.0 ms (+ 289.8 ms in 36 steps since start of marking, biggest step 65.2 ms, walltime since start of marking 1935 ms) (average mu = 0.318, current mu = 0.343) [55568:0x586b120] 164697 ms: Mark-sweep (reduce) 488.9 (495.6) → 488.0 (495.9) MB, 2384.5 / 0.0 ms (average mu = 0.165, current mu = 0.001) allocation failure scavenge might not succeed
No the build step requires 2GB of RAM, if you have to build on the server then you need 2GB of free ram. The only alternative would be to build locally or in a CI/CD and commit the build folder into the source control.