Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MariaDB issues #3453

Closed
petrk94 opened this issue Aug 11, 2018 · 3 comments
Closed

MariaDB issues #3453

petrk94 opened this issue Aug 11, 2018 · 3 comments

Comments

@petrk94
Copy link

petrk94 commented Aug 11, 2018

Hello Etherpad Community,

Im facing a problem to run Etherpad as productive.
I have it run sucessfully on CentOS 6 with dirtyDB, unfortunately, the shared host provide not the latest MySQL which is needed to use the charset utf8mb4. As altenative the shared host provide MariaDB, which is able to work with utf8mb4.
My theory, just change the config and let it work, but its wrong. while mysql need to be called localhost, the port ist 3306, but for the mariadb its called 127.0.0.1:3307 ; This is a problem, due etherpad try to add the port additional and than it shows: 127.0.0.1:3307:3306

Now is my question, can the port number be set manually or can there be another database charset?
DirtyDB is only for testing, sqlite is not available, postgres is hard to set up on the server.
I would really prefer the mysql utf8 charset.
I hope you can help

@muxator
Copy link
Contributor

muxator commented Aug 11, 2018

Hi @petrk94,

try putting this in your settings.json:

  "dbSettings" : {
                   "user"    : "youruser",
                   "host"    : "127.0.0.1",
                   "port"    : 3307,          // <-- see below
                   "password": "PASSWORD",
                   "database": "your_database_name",
                   "charset" : "utf8mb4"
                 },

If you have a look at the mysqldriver's source code the port configuration parameter is allowed.
Thank you for bringing this up: I think that settings.json.template could be updated to actually mention port.

Tell me if this solves your problem, and do not forget to update to 1.7 once it is released.

@petrk94
Copy link
Author

petrk94 commented Aug 11, 2018

@muxator
yes, works well, the just the port parameter was necessary, now it works fine with MariaDB.
Thanks for the help.

Ps. It were nice if the database can be checked/switched in the backend or adjusted there manually without typing all in the settings.json.

@petrk94 petrk94 closed this as completed Aug 11, 2018
muxator added a commit that referenced this issue Aug 11, 2018
…rameter

The port parameter is supported by the mysql driver, but to know this one has to
read through ueberDB's code.

At least for this simple case, it may make sense to be explicit.

Fixes #3453
@muxator
Copy link
Contributor

muxator commented Aug 11, 2018

Committed d38f531 to mention the existence of port in settings.json.template, so these customizations are easier in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants