yes, sorry, me again :P
documentation of Ralph takes place in http://ralph-ng.readthedocs.io or in the git repo?
or: which is newer / better / more relevant ?
source code is in git repo, but every time there is change in docs in git repo, it's built on http://ralph-ng.readthedocs.io/ automatically
the sample configuration for LDAP you show, where exactly would I have to put that?
the part starting with
import ldap
lib/python3.4/site-packages/django_auth_ldap/config.py ?
hm, probably not.
it'll be the best if you'd create your own settings file and run ralph like
DJANGO_SETTINGS_MODULE=local_settings ralph runserver ..., where local_settings.py is file with settings in your current dir. On top of this file you should place from ralph.settings.prod import *
it's not tested so it might not work exactly as i told you - but maybe one of Ralph folks ( @szok @ar4s @xliiv @vi4m or me) could test it in next few days
I#ll also combine that with running Ralph not as root, but as a standard user
for that I would
chown -R ralph.ralph /opt/ralph
do you think it's safe to do that?
I created a user ralph
in his homedir I have
local-settings.py
from ralph.settings.prod import
AUTHENTICATION_BACKENDS = (
'django_auth_ldap.backend.LDAPBackend',
'django.contrib.auth.backends.ModelBackend',
)
LOGGING['loggers']['django_auth_ldap'] = {
'handlers': ['file'],
'propagate': True,
'level': 'DEBUG',
}
import ldap
from django_auth_ldap.config import LDAPSearch, GroupOfNamesType
AUTH_LDAP_SERVER_URI = "ldap://private.domain:389"
AUTH_LDAP_BIND_DN = "CN=bla,DC=private,DC=domain"
AUTH_LDAP_BIND_PASSWORD = "securepw"
AUTH_LDAP_PROTOCOL_VERSION = 3
AUTH_LDAP_USER_USERNAME_ATTR = "sAMAccountName"
AUTH_LDAP_USER_SEARCH_BASE = "OU=users,DC=private,DC=domain"
AUTH_LDAP_USER_SEARCH_FILTER = '(&(objectClass=)({0}=%(user)s))'.format(
AUTH_LDAP_USER_USERNAME_ATTR)
AUTH_LDAP_USER_SEARCH = LDAPSearch(AUTH_LDAP_USER_SEARCH_BASE,
ldap.SCOPE_SUBTREE, AUTH_LDAP_USER_SEARCH_FILTER)
AUTH_LDAP_USER_ATTR_MAP = {
"first_name": "givenName",
"last_name": "sn",
"email": "mail"
"company": "company",
"manager": "manager",
"department": "department",
"employee_id": "employeeID",
"location": "officeName",
"country": "ISO-country-code",
}
then I created a (very very basic) start-script
export DATABASE_NAME=ralph
export DATABASE_USER=ralph
export DATABASE_PASSWORD=blabla
export DATABASE_HOST=localhost
export PATH=/opt/ralph/ralph-core/bin/:$PATH
export RALPH_DEBUG=1
export DJANGO_SETTINGS_MODULE=local_settings
ralph runserver 0.0.0.0:8000
what I now get is
ImportError: No module named 'local_settings'
what am I doing wrong?
should I put local_settings.py into
/opt/ralph/ralph-core/lib/python3.4/site-packages/django/conf/ ?
no, didn't help
@ar4s @kasim1r @mkurek i think we should ship django-auth-ldap inside the package
it's small enough to be zero-problem for us, and for user it will be more user friendly to just have it installed
/opt/ralph/ralph-core/lib/python3.4/site-packages/ralph/settings/prod.py
base.py : lots of them under /opt/ralph
/opt/ralph/ralph-core/lib/python3.4/site-packages/ralph/settings/
and then try DJANGO_SETTINGS_MODULE=ralph.settings.local ralph runserver (if your file is called local.py)
or DJANGO_SETTINGS_MODULE=ralph.settings.local_settings ralph runserver
and remember about the difference between local-settings.py / local_settings
the up tick cpoint to the ":"
you are missing comma before company in the preceeding line
success
the code was copy-paste from the Docu :P
yahooo, I can log in. after adding "staff status" to the user, which got auto created
works like a charm:)
OK. do I need to adapt the URL anywhere? cos it's no longer going to be
ralph.my.domain:8000 but https://ralph.my.domain
which I call in the browser
and in the API
what you have to do is something like that: in nginx conf you define server for port 80. In there you create
return 301 https://$server_name$request_uri;and in second the server section for 443 you create a section
location / {
proxy_pass http://ralph.my.domain:8000;
}
yes, thx, what I meant is: does ralph need to know that the URL it's actually running on is different nbow
*now
very nice