Base Repo OOMs on Fly.io about blues-stack

[smucode]

I had the same issue, managed to fix it by fly scale memory 512

https://fly.io/docs/apps/scale-machine/

[kwigley]

I've had success by setting the following in fly.toml

[deploy]
  release_command = "bash ./scripts/migrate.sh"

and creating a script that looks like

#!/bin/bash

fallocate -l 512M /swapfile
chmod 0600 /swapfile
mkswap /swapfile
echo 10 > /proc/sys/vm/swappiness
swapon /swapfile
echo 1 > /proc/sys/vm/overcommit_memory
npx prisma migrate deploy

related: https://community.fly.io/t/prisma-sqlite-causes-an-out-of-memory-error-on-deploy/11039

[mcansh]

@kwigley if you want to open a PR with those changes, i would gladly merge it :)

[graysonhicks]

I have attempted a paid plan, but without running machines I can't rescale the apps. I think starting over completely and choosing a higher configuration (multiple CPUs, 4GB RAM) may solve, but if that's the case it should be documented, and I'm not sure how that affects pricing on Fly.io.

[graysonhicks]

Yea, unfortunately mine was in a broken state where the app never successfully deployed, so I couldn't scale the memory for it and it was stuck at 256. Only solution was to delete the fly app and start over, choosing the 512 memory version to being. I think that is okay, but should be documented.

[kinggoesgaming]

Stuck on this as well...

Is the memory update applicable to the DB machine or the website machine(staging/production)?

My assumption is the DB but want to confirm before I blow something up

EDIT: figured it out, its for the staging/prod website machines.