Managing auto-created `db` app from same repo as main application?

Hi! I created a fly app to run my Phoenix code using fly launch, and it was incredibly seamless. I have loved using the product so far.

However, it is now time to scale my DB, and I realized it created a separate app for that. I’m not quite sure how to scale my DB, with the same infrastructure-as-code pipeline that was automatically set up in my git repo, for this second app. It seems like only configuration for my phoenix deployment is actually contained in fly.toml.

I was able to download my fly config for the db via fly config save --app app-db, but I was unable to push any changes via fly deploy -c ./fly.toml

==> Verifying app config
Validating ./fly.toml
✓ Configuration is valid
--> Verified app config
==> Building image
==> Building image
Error: failed to fetch an image or build from source: app does not have a Dockerfile or buildpacks configured. See https://fly.io/docs/reference/configuration/#the-build-section

I’m really just trying to increase the RAM and CPU on my database, preferably maintaining infra-as-code. Does anybody have any pointers here?

Thanks for your time.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.