Docker-compose issue - wrong db dependency

Wappler General Bugs
#1

Hi all, have a potential bug here (but is also just as likely to be an issue somewhere between the chair and the keyboard). Using latest 5.2.3.

Instantiated a brand new project, Docker + NodeJS. Set the DB as custom, externally hosted. Development enviro spins up just fine on the local enviro. Making zero changes to the vanilla starter app, I create a DigitalOcean cloud provider and then a QA target of the same config. However, when attempting to deploy to this second hosted target, immediately a docker-compose error gets thrown. It seems the yml may be getting setup incorrectly with an externally-hosted custom DB?

That or I’m screwing something up within the first three minutes of a new project start. Help is appreciated!!
issue|690x428

#2

Seems the docker web instance is wrongly marked as dependent from a db instance that you don’t have because you are using custom database connection.

Will improve that in next update.

For now you can just edit the docker-compose.yml file under the .wappler/target/yourtargetname and remove depends: db

#3
#4

Perfect, thank you!

#5

(If it’s not too much trouble, while you’re at it would you guys mind adding all the additional options to the DB definition for Custom type DB’s in the Project Settings targets? Options that are typically available in the direct DB connection configuration, things like SSH and the all-important SSL? Thanks so much)