400 - Signup is disabled for this server. about docker-etebase HOT 19 CLOSED

@tuxiqae I need to fix a problem with postgres, then I will add this ENV to the entrypoint.sh

from docker-etebase.

Sorry, but I don't know, There is no documented setting for that.
I think you should ask @tasn at https://github.com/etesync/server or https://www.etesync.com/community-chat/

from docker-etebase.

You need to add each user specifically from the admin or change the settings.py file. We didn't want signups enabled because almost no one wants this. They want to manually add users for each user they want to allow.

from docker-etebase.

You need to add each user specifically from the admin or change the settings.py file. We didn't want signups enabled because almost no one wants this. They want to manually add users for each user they want to allow.

@tasn Can we add users at the time of docker initialization. Like though a config file?

from docker-etebase.

@addy419 for that I need to change the entrypoint.sh and use the manage.py.

I could create some dir that load *.py scritpts at init.

from docker-etebase.

Thanks. I am trying to achieve the same thing with etesync-cli but cannot build it because of a gcc error. A directory could work as a better option.

from docker-etebase.

@victor-rds @tasn
Would you consider adding an environment variable to the Docker image ecosystem so it won't need to be changed in a Python file which we got no real access to?

from docker-etebase.

I don't remember from the top of my head, but isn't it already the case? I think there's an env variable or at least a config, no? Maybe I'm just misremembering.

from docker-etebase.

Wow, thanks for the hasty response! Ummm from what I see here, seems like users will have to edit settings.py on every instance.

from docker-etebase.

You guys both ROCK!
Super professional, it's apparent from the responses and from the code quality.
Thanks for doing so much for the community!

P.S. won't you also need to change the code on etesync/server?

from docker-etebase.

I wish I could take credit, but it's all @victor-rds making sure the self-hosting experience using docker is ROCK SOLID. Thank you Victor!

from docker-etebase.

I wish I could take credit, but it's all @victor-rds making sure the self-hosting experience using docker is ROCK SOLID. Thank you Victor!

This repo is amazing but I wasn't talking only about it :)

from docker-etebase.

P.S. won't you also need to change the code on etesync/server?

Well, the best way would be to add a setting to the etebase-server.ini, but since is just commenting a single line little sed can solve for now.

from docker-etebase.

P.S. won't you also need to change the code on etesync/server?

Well, the best way would be to add a setting to the etebase-server.ini, but since is just commenting a single line little sed can solve for now.

Of course, but that'd require a change on server.py

from docker-etebase.

We can do the etebase-server.ini change later on. Let's go with the quick fix for now. :)

from docker-etebase.

@victor-rds already fixed it, just checked and I can verify that it works on victorrds/etesync:latest

P.S. for some reason it does not yet appear under the documentation in Docker Hub

from docker-etebase.

Ah, great! :)

Documentation on dockerhub is done manually (or maybe @victor-rds has CI for it), so I guess he just hasn't updated it yet.

from docker-etebase.

Yeah, the docker hub README update is done manually, CI is only for builds at the moment.

from docker-etebase.

@victor-rds already fixed it, just checked and I can verify that it works on victorrds/etesync:latest

P.S. for some reason it does not yet appear under the documentation in Docker Hub

Now both repositories READMEs are updated.

from docker-etebase.