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

Database types #57

Closed
plsnotracking opened this issue Feb 18, 2021 · 3 comments
Closed

Database types #57

plsnotracking opened this issue Feb 18, 2021 · 3 comments
Labels
Feature Request Feature Request question Further information is requested wontfix This will not be worked on

Comments

@plsnotracking
Copy link

plsnotracking commented Feb 18, 2021

Hello,

Thank you for maintaining an image and keeping it up to date.

etebase 2.0 allows different database types (such as mariadb, mysql), but the README.md currently only seems to provide two options:

  1. sqlite
  2. postgres

I was wondering if there was a reason or maybe I could help if there was any needed.

Specifically:

elif [ "${DB_ENGINE}" = "postgres" ]; then

We edit this line to have more freedom, we should be good (and all the other relevant options with it).

Link:

engine = django.db.backends.postgresql

engine = django.db.backends.mysql
name = etebase
user = etebase
password = your-password
host = 127.0.0.1
port = 3306

Source^: https://www.linuxbabe.com/ubuntu/install-etesync-server-ubuntu

Another question was, the docker would potentially give an error if it's above 1024 (or maybe I read it incorrectly)? MySQL typically runs on 3306, is there a good way to handle this?

Current I placed the etebase-server.ini in /data and pre fill the configuration if anyone is in the same boat as I.

Edit: added links to make the issue more specific, added current workaround.

@victor-rds
Copy link
Owner

Sadly MySQL and MariaDB are not officially supported by the Etebase Server, there is an open issue on the etebase repository.

etesync/server#69

@victor-rds
Copy link
Owner

Another question was, the docker would potentially give an error if it's above 1024 (or maybe I read it incorrectly)? MySQL typically runs on 3306, is there a good way to handle this?

Sorry but I didn't understand this, but you can and should listen on ports 1024 and above, ports 0 to 1023 are privileged ports only process running with superuser permissions listen to them.

My image does not run as root (unless you force it), by default most databases uses unprivileged users, postgres por example uses the 5432 TCP port .

@victor-rds
Copy link
Owner

if [ "${PORT}" -lt "1024" ] && [ "${C_UID}" -ne '0' ]; then
    dckr_error "Only root can use ports below 1024"
fi

If you talking about the code above, this is about the port used by the etebase server, not the port for database communications, and as stated previously the error only happens if you try to use ports below 1024 with an unprivileged user

@victor-rds victor-rds added Feature Request Feature Request question Further information is requested wontfix This will not be worked on labels Feb 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Feature Request question Further information is requested wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants