Small helper script for Caprover users (Linux/MacOS/WSL)

[Apple]

Oh, thanks for the heads-up! I had to go check how I was handling that.

So, as it is, I deploy from the Development target, but for running the migrations I actually have a Caprover target I switch on Wappler. So, the Caprover target has the credentials of the DB manager set to the Caprover instance, but I always deploy from the Development target for convenience

[JonL]

@Apple

but for running the migrations I actually have a Caprover target I switch on Wappler.

Same as me, but I didn't want to mention it to avoid further confusion. I still do that work manually via UI but whenever I find the time my idea is to migrate that process to CI/CD

[Apple]

@JonL

whenever I find the time my idea is to migrate that process to CI/CD

Automatically generate Knexfile for migrations

Hello, Please expose migrations directory .wappler/migrations inside the Docker container, as well as an appropriate Knexfile to facilitate automatic migrations. This will facilitate future automated deployments (outside of Wappler’s Docker-Machine), something that would carry the following arguments: knex --migrations-directory .wappler/migrations/db --migrations-table-name wappler_migrations --client pg --connection 'postgres://db_user:db_password@docker:9906/db-name' migrate:status Relate…