Wappler auto creating database that doesn't exist

Hi Wappler Community,

I’ve been posting a lot about how I am struggling to publish my Wappler cite. One issue that I’ve run into was that Wappler was referencing a database that doesn’t exist named db. I’ve edited my docker-compose.yml file to not reference this database, but when I go into my targets and save it, it automatically creates another db database with the correct connection string as my real database. Here are some screenshots to show you what I mean.

image

I will delete this database on Wappler, and I’ll delete it from my files, yet nothing changes and this database is still created. I believe that this is preventing me from publishing my cite and has been a major cause for headaches for almost a week now.

I am confused as I am new to web development and Wappler and am unsure if this is user error or if this is a bug from Wappler itself. Some clarification as the proper steps to move forward and get my cite published would be very much appreciated. These are the error messages I receive when going to publish:

What are your target settings? And on which target is that?

Here are my target settings. This is my discretecap target. I’ve even made a new project and hooked it to DO but still receive the error in the second picture. Any help on this matter would be greatly appreciated.

This seems like an error from docker desktop. I think I saw this somewhere as reported bug from docker desktop. Try updating to a different version

I’m on the most updated version of Docker

Looks like your area little confused by the difference between an actual database name and how wappler stores database connection settings.
This is how database connections work with docker. Wappler creates all the database connection setting for you and stores them under a connection name “db”.
This is NOT a database, this is a connection settings .json file with the settings for the default docker created database.
You can also see all the settings in the project settings file.
It should NOT be deleted nor should references be removed from the .yml file.
This may be the cause of some of your problems.

I was told that it was a bug, my previous post was flagged and taken down on this matter and I was told to manually edit my .yml file. I’m still having issues in regard to posting my cite. My most recent post delves into this more.

Furthermore, it seems to be a bug because in my database manager I will have my one database “Discrete_Database” and when I go into my targets and exit another database appears named db. It has no tables in it and has an error message on it. If I delete it it doesn’t stay deleted.

as you reported multiple issues in your previous post, some of them got solved and that’s why the post got flagged as resolved bug.

That it why it is important to report a single issue per topic.

As @Hyperbytes explains you seems confused between the databases and database connections in Wappler.

If you use docker a single database is created and it is called “db” also a connection to it is created.

So there is no need to create additional databases for the same project.

Ok so you’re saying I don’t need to delete the db. It’s fine being in my database manager. Furthermore, I should add back into the .yml file the reference to the db. This will give me the same error message as I reported in my previous post where I was told to delete it.

I have made a more recent post on wappler general that highlights a lot of my issues in posting the cite. I’m confused as to where I am going wrong and have been trying to just publish the cite for a week now.