Advice needed on sub-apps - one update for all

[Apple]

Important question:

1. Were you planning to use Wappler UI for this deployment of multiple instances?

Now, my advice following ahead assuming you answered “no” to the question above:

@daves88

So the idea would be to duplicate the current platform, rebrand and redeploy on a new server with a blank fresh DB.

So, the idea would be to re-use the same docker-compose file as different projects:

customer_1/docker-compose.yml
customer_2/docker-compose.yml

This would create “customer_1”, “customer_2”, etc. “projects”

@daves88

However, this poses a problem. I would like to be able to update all “sub apps” from the Master App.

A Bash script to re-deploy the docker-compose files would do the job, which would pull an updated container (Docker) image (which you’d have to create previously somehow). However, this doesn’t apply migrations (DB changes), because it’s missing this feature request (or similar):

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…

@daves88

Also, would be good if each sub app had their own custom domain.

In each project folder (in each customer folder) write a docker-compose.override.yml that adds the custom domain setting (e.g.: Traefik labels)

I know this post is a bit technical, but “complex” requests have “complex” solutions

If you need professional help, @ tbvgl is available for hire. Do note, regardless, Wappler is still lacking exposing DB migrations inside containers which is required for decent DB schema updates. This could be worked around by creating another Bash script that would rsync the migrations from your project to the remote server, and somehow apply them