We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The documentation at https://docs.geonode.org/en/master/devel/installation/ reports about creating a local_settings.py file, but it is not used when running the migrate command line or when starting the application.
local_settings.py
It should be documented that, if you have your local_settings.py, you should run the commands with the DJANGO_SETTINGS_MODULE env var set.
DJANGO_SETTINGS_MODULE
You can set it locally on the command line running the command, such like:
DJANGO_SETTINGS_MODULE=geonode.local_settings python manage.py migrate
and
DJANGO_SETTINGS_MODULE=geonode.local_settings paver start
Also, in the section documenting the customization of the DB, the sample snippet reports:
DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'geonode_dev', 'USER': 'geonode_dev',
but if you replace the default
'ENGINE': 'django.contrib.gis.db.backends.postgis',
with
'ENGINE': 'django.db.backends.postgresql_psycopg2',
you'll get the error
AttributeError: 'DatabaseOperations' object has no attribute 'geo_db_type'
during the migration command.
The text was updated successfully, but these errors were encountered:
The info
is only reported in this page: https://docs.geonode.org/en/master/install/advanced/core/index.html#update-the-settings-in-order-to-use-the-postgresql-database
Sorry, something went wrong.
@etj as this is regarding docs I've transferred the issue. Your contribution is very welcome ;)
No branches or pull requests
The documentation at https://docs.geonode.org/en/master/devel/installation/ reports about creating a
local_settings.py
file, but it is not used when running the migrate command line or when starting the application.It should be documented that, if you have your
local_settings.py
, you should run the commands with theDJANGO_SETTINGS_MODULE
env var set.You can set it locally on the command line running the command, such like:
and
Also, in the section documenting the customization of the DB, the sample snippet reports:
but if you replace the default
with
you'll get the error
during the migration command.
The text was updated successfully, but these errors were encountered: