Is there a tutorial to correctly configure the database manager setting?
- Server -> VPS Cloud (Hetzner)
- System -> Docker / Ubuntu / Nodejs
- Development target -> DB created by Docker
- Production target -> DB created in Ubuntu
I can’t find the solution
You only really need to work with the remote ‘hosted’ DB Marzio otherwise you’ll be syncing back and fourth a lot with local and remote. This is set-up the same as any other DB in the DB Manager, enter your credentials for the DB, Test the Connection, and Save. Define in your Global DB settings and go from there as normal in any other environment. Maybe I’m wrong but its how we have been doing it, aside from a recent Project where we have actually been refactoring an old DB in to a new more performance derived schema, then we’ll copy this schema across to the host and restore the data from local to remote.
so if I understand correctly it is better to avoid creating a Docker database and use the database created with Ubuntu, both for development and for production?
If you already have a database then you can connect to it as normal in the DB Manager Marzio, then would be no need for one within your container. Unless you want to consolidate everything in to a single environment, which is essentially a primary aspect of Docker for easy migration between hosts… Does that make sense? 
I already have a database on the provider’s server where the domain is, but I want to move it to the cloud vps server
what confuses me is if I have to configure the database in the development target (Docker db) and in the production target (Ubuntu db)
or do I not have to enter anything in the targets and I just have to configure the db in the Database Manager?
in practice I don’t understand the usefulness of a Docker database, which is reachable only locally and not remotely
You do not 'have to' use Docker for your database its just an option you can take advantage of. Allows you to have everything in a single container, thus if you want to migrate all you do is take the image and host it, everything within the image is contained within it so you don't have to go about setting up all your services. The Production database is your hosted database option.
You could get two birds stoned with one joint and use the Production database as your hosted database saving the need for creating a database at the host level. It will use the same IP as your server for connection, only thing I'd suggest is changing the DB Port to 3306, the standard port for MySQL. Connecting to this database is exactly the same as any other database once it is uploaded to your host. You set-up the database manager connection the same way you would for any other database simply using the credentials you specify in the development DB area for your Docker environment, Username, Password, DB Name.
This is not the case with Production, its on the host you uploaded it to, thus is a remote DB, its not local. You'll use the same IP to connect to it.
Some help:
Thank you I am increasingly oriented not to use Docker database.
I do some tests to see which can be the best solution for me
1 Like
If you change your mind later and select to use Docker for your DB you can always add MySQL to the image and import your DB schema in to it using Workbench etc. That way you can play safe with what you know, and in the future after learning more about Docker implement your DB in to the container. Best of both worlds.
Good luck with the Project @Marzio
2 Likes
But before leaving, I would like to understand how Wappler manages databases with Docker
Summarizing, I have a Nodejs project created on VPS Cloud Hetzner, a MySQL database was created via Ubuntu’s server that works perfectly with Navicat.
With Wappler
In the development target I chose a MySQL database (created automatically by Docker) to which I only changed the 7.5 version
In the production target instead I configured a connection to the remote database.
Theoretically, if I’m not mistaken, it should be all correct !!!
But if under development I see the database created by Docker (with test folders), in the production phase, instead there is a database that does not display the folders (as it happens with Navicat)
And I cannot configure the direct connection because I receive a message that invites me to change the targets of the project
