HI @George , @notum and I are not talking about different problems but if you need a separate topic from me, can I point you to the bug report I made two weeks ago?
The issue is that when creating a new project with a database, the current version of wappler does create a database that we can see in docker but it does not and cannot connect to the database manager. Creating a new project with a database in earlier versions of wappler does do everything properly and can also be opened and working properly in the current version. This is what @Notum is describing and also what I have been describing. Please try it so you can see what we’re talking about.
When @Notum provided this,
It was from creating a new project with a database. @Notum described that in the first post in this topic. Your response assumes it is not a brand new project, as does @Apple ’s response because @Notum even replied that you missed the essence of the problem. Why would we need to destroy database data and deploy again when all we’ve done before is create a new project with a database? Wouldn’t that mean there’s a bug in how wappler is creating the database for us? Would it be possible for you to try to create a new Docker project and a new docker database in the current version so we don’t feel like we’re going crazy? You would see what we’re talking about and that we are both talking about the same thing. My bug report was ignored and this thread is frustrating because it is easily reproduced, if only you would try it.
And as a side note, there are also posts about not being able to create connections in production targets. Could there be something with the way the current version is attempting to create database connections? Again, everything works fine in previous versions.