Wappler Version : 6 Beta 13
Operating System : Windows 10
Server Model: Node
Database Type: MariaDB, Redis
Hosting Type: Custom Docker
Expected behavior
What do you think should happen?
When enabling Redis for a Docker Remote cloud database, it would use that cloud database when the target is that same cloud database
Actual behavior
What actually happens?
When creating a Redis cloud database on a cloud provider, it correctly creates the Redis database and is selectable from the Project Option targets, however when deploying the target an additional docker Redis database is additionally deployed and the cloud database is only “sometimes” used. I say sometimes since it sometimes works and sometimes doesn’t when when doing redeploys.
How to reproduce
- Detail a step by step guide to reproduce the issue
- A screenshot or short video indicating the problem
- A copy of your code would help. Include: JS, HTML.
- Test your steps on a clean page to see if you still have an issue
Under Cloud Providers, Right click Services, Add Service - Databases - Redis. Name it and deploy it. A redis:7.0 image is deployed and active.
Under Project Options for the Docker Remote target, enable Redis and set type to Cloud Database, select database server, database can be any option default or a numbered database. Save. Deploy target. A redis:alpine image is additional deployed and active when it should not be since it should be using the cloud provider Redis database.
I was running into issues where I was testing a project with the Bull Queue Extension and having issues where items were getting stuck in waiting status, I discovered that the project didn’t seem to know which Redis database to point to since two different docker containers were getting created and managed. I swapped to Type: Docker from Cloud Database to resolve the issue and it uses just the redis:alpine image that is deployed. I don’t believe the image itself is the problem, its the two separate containers being deployed.
Below are Portainer screenshots to show what is being deployed. The first screenshot is a Docker target, the second is a Cloud Database target. Both get created with Cloud Database is selected.