Iterative Development Workflow

One of the reasons developer avoid putting any logic in the database is because it's a pain to move that logic from a file (stored in git) to the environment (the database) where it is executed. In many ways it's similar to the workflow you have when developing in a compile language like C/Java/Go where there is an additional step, compiling, before you can see the code in action. But with databases it's a bit worse because it's not as easy to move that code as a one line command to compile a C program.
This is the main reason we developed the subzero-cli. The goal is to make the development workflow for writing code that lives in the database (tables/views/stored procedures/...) as close as possible to the workflow of a Ruby/PHP/Node developer. We want to be able to just save a (sql) file and have that logic immediately running in the database, ready for you to execute. While moving SQL code from files to the database is a core feature, subzero-cli does a lot more, it will also do the same thing for nginx configs and lua code (running in nginx). It will also give you a nice interface to look at the logs of each component of the stack and see the result of a HTTP call to the api in addition to creating and managing your database migrations.

Check out how the whole process looks (although you don't see in the gif the process of saving the file).

Notice the result of this in each dashboard window/tab (OpenResty/PostgREST/PostgreSQL) each showing a log line of the event they registered.
Probably the most interesting window for now will be PostgreSQL where you can see the actual queries that were executed for that REST call,
which in this case look something like this (with a bit of formatting compared to the real thing)