hardcoded localhost on query when create new user eprints 3.3 8000 #518
Comments
|
I was looking at the code recently and I was a bit puzzled why this was hardcoded. I suspect it has not caused anyone an issue up to now is that you would not be creating a user (or database) on a remote server, as they would require you to use another user account that has permissions to do this. Normally you would probably want to avoid having an account that can create other accounts from a remote server, so typically you would manually create the user and database on the remote server and then run "epadmin update" rather than "epadmin create". However, as that would mean having to manually run the other commands to initial setup EPrints (i.e. add an EPrints initial admin user, add subjects, generate static pages, etc.). EPrints 3.3 is no longer being actively developed so I have created eprints/eprints3.4#182 where any change could be failry easily backported to 3.3 |
|
See eprints/eprints3.4@0e28f10 if you want to backport the change. |
I try to create docker compose for eprints version 3.3 based on eprints 3.4 docker-compose from here.
but when creating sample repository from inside the container I got access denied when create database
after check the database, by default generated user's host is
localhost. and I try to trace the query, and I found that localhost was hardcoded here.and when I change the
localhostto%, and then reconfig the database, everything work as expected.but the user become redundant
and my question is,
is the hardcoded
localhostis intentionally defined or for other reason?and is there possibly issues when I change the
localhostto%on the mysql.pm?The text was updated successfully, but these errors were encountered: