Commiting Geonode-Project Changes to Geonome Production
I had try to commit genode-project template (index.html) changes to geonode production installed via apt-get, but I had an issue related to the production database. After configuring geonode.conf, I could see the changes over geonode production templates, made through geonode-project, however my production database would get covered / disappeared after geonode.conf according to geonode-project WSGI.
Now, I am having the same issue, my production database "development.db" = sqlite that is in ~/Envs/geonode/lib/python2.7/site-packages/geonode/development.db is being covered or disappears after geonode.conf configuration.
I have granted all permissions to development.db (-rwxrwxrw- 1 www-data www-data 425984 Mai 14 13:40 development.db) but the issue remains and I am unable to sign in to geonode production.
Could someone help me to figure out what is going on and get this problem fixed? Find bellow my geonode.conf
Re: Commiting Geonode-Project Changes to Geonome Production
After configuring geonode.conf, I could see the changes over geonode production templates, made through geonode-project, however my production database would get covered / disappeared after geonode.conf according to geonode-project WSGI.
I´m not sure if I can follow you as your write about dev and production
geonode.conf and databases. Let´s try to sort things out.
First as you write you´re using sqlite in „dev mode“.
Following the docs for production postgresl is setup/used instead.
Which database is in use is configured in your settings.py or local_settings.py
In „dev mode“ requests are served by djangos build in webserver.
In production (following documentation) by apache which passes requests to
WSGI or Tomcat. Apache is configured with geonode.conf. It f.e. grants or denys access
to different directories or binds hostnames to ports and so on. But it does
not care about your database ;)
I´m unsure if I met the point. Don´t hesistate to ask if something is unclear.