Open francescobianco opened 2 years ago
Hi @francescobianco thanks for this idea, we would have to think about this carefully before deciding whether or not we would want to implement this system. One thing that worries me at the moment is the security aspect of this.
Also, I think it would probably be better to add Adminer as part of the Docker configuration (in the docker-compose file) instead of the public folder but to access the Myddleware database only, I wouldn't be comfortable adding access to the other third-party applications' databases.
Another parameter that we need to take into account is that most Myddleware users would already have their own system set in place to access their databases (Adminer, HeidiSQL, DBeaver, phpMyAdmin, ....) and I wouldn't want to impose another system onto the users if they're already using something else.
What do you think?
Hi @EstelleMyddleware . We normally install adminer becouse we manage lots of instance and different people work on them. So it's faster if who is working on the istance have a "fast" access to database managed with myddleware. That's why we asked to Francesco to add adminer as default in our case.
Very often, too often, it is necessary to open the database with a consultation tool, which allows you to look inside and study the structure of the data.
integrate Adminer https://www.adminer.org/ into the 'public/' folder, it could be a very useful move
even more could be to add a button that opens in a second tab of the browser adminer already authenticated to the database using the autologin function with submit to hidden fields
@simonetravaglini @EstelleMyddleware @Myddleware