I know this looks weird, but - given a starter project, I would love to properly configure
AshPostgres
AshPostgres
, and then to "comment out" it and swap with an in-memory (non actually persistent) alternative, e.g.
Ash.DataLayer.Ets
Ash.DataLayer.Ets
(even better if any accidental entry gets deleted in 24hrs).
Use case: I just want to start and deploy a simple static HTML page that requires no logic, nor authentication. In the near future, as I develop features, I want to put them back in. But in the meantime, I want to deploy my app without actually spending $38 per month for a postgres db I would not hit (yes, I'm using fly.io).
If I'm tackling this problem wrong, or if you suggest a better workflow, I'm all ears!
Solution
But also if you're just not going to be using the resources at all, you can just not start your repo
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.