At some point in the future, the full-stack Rails app at https://github.com/falling-fruit/falling-fruit (currently running at https://fallingfruit.org) will be taken offline. Database management (database schema, migrations) will need to be moved, most logically to this repo, which is the backend for the new web app at https://github.com/falling-fruit/falling-fruit-api.
Without Rails to show us the way, we'll need to cobble a solution together. For now, I've chosen not to use a framework like Prisma or knext. If this continues, then a separate tool is needed for database migrations. I think my preference would be to write the migrations directly in SQL. But a tool to manage them would be nice.
At some point in the future, the full-stack Rails app at https://github.com/falling-fruit/falling-fruit (currently running at https://fallingfruit.org) will be taken offline. Database management (database schema, migrations) will need to be moved, most logically to this repo, which is the backend for the new web app at https://github.com/falling-fruit/falling-fruit-api.
Without Rails to show us the way, we'll need to cobble a solution together. For now, I've chosen not to use a framework like Prisma or knext. If this continues, then a separate tool is needed for database migrations. I think my preference would be to write the migrations directly in SQL. But a tool to manage them would be nice.
runSql