is an example. Ubuntu Server 18.04 LTS with firstname.lastname@example.org
installed via docker using
"my_geonode.settings") config for WSGI.py. SITE_BASE.CSS has not
But both, either settings and local_settings in WSGI.py, SITE_BASE.CSS has not been retrieved.
Thank you for your time in advance
Any help will be very appreciated
On Wed, Dec 5, 2018 at 6:22 AM Alessio Fabiani <[hidden email]> wrote:
historically geonode-project followed the path described by Matteo for
whatever reasons that I don't remember now.
I agree that we should align the two approaches in order to avoid confusion.
Il giorno lun 3 dic 2018 alle ore 16:21 juliermegithub < [hidden email]> ha scritto:
> Hi Alessio and Matteo,
> I tried installing a new instance, using local_settings.py and configuring
> wsgi.py as os.environ.setdefault("DJANGO_SETTINGS_MODULE",
> But the installation did not succeed.
> Kind regards
> On Mon, Dec 3, 2018 at 11:38 AM Julierme Pinheiro <
> [hidden email]> wrote:
> > Dear Alessio and Matteo,
> > Thank you both for the highlights. Let me understand what you both
> > here:
> > By Alessio:
> > I understood that I can use local_settings.py, and still configure
> > as os.environ.setdefault("DJANGO_SETTINGS_MODULE",
> > Is that the correct understanding?
> > Sorry Alessio, one thing I did not understand: I currently have
> > "DJANGO_SETTINGS_MODULE", "my_geonode.local_settings" set in WSGI.py for
> > the installed email@example.com instance, Can I revert this
> > configuration to "my_geonode.settings" by adding the line <
> > DJANGO_SETTINGS_MODULE=my_geonode.settings> to the file uwsgi.ini?
> > By Matteo:
> > First of all, I could not understand why we run the command
> > DJANGO_SETTINGS_MODULE=my_geonode.local_settings paver setup, as we
> > have a geoserver4my_geonode container. But anyway, I ran the commands
> > bellow and got the response for paver start:
> > $ docker exec -it django4my_geonode paver reset
> > $ docker exec -it django4my_geonode paver setup
> > $ docker exec -it django4my_geonode paver sync
> > $ docker exec -it django4my_geonode paver start
> > Java was not found in your path.
> > Any comment on that will be very appreciated it.
> > Kind Regards
> > Julierme
> > On Mon, Dec 3, 2018 at 7:21 AM Matteo De Stefano <
> [hidden email]>
> > wrote:
> >> This is an issue in gonode-project settings and local_settings
> >> management, in my opinion.
> >> Currently, local_settings.py are always imported by settings.py, and not
> >> overriding but just "extending" settings.py.
> >> This diverges from the behavior of local_settings in vanilla geonode,
> >> where local_settings.py are importing settings.py, and overriding:
> >> This is confusing, and the instructions in README are wrong, since wsgi
> >> needs always to load settings.py, with current approach (to be fixed?).
> >> Pointing to local_settings.py is wrong.
> >> The following lines of instructions in README should be removed, or
> >> modified:
> >> **# Using Custom Local Settings
> >> cp my_geonode/local_settings.py.sample my_geonode/local_settings.py
> >> vim my_geonode/wsgi.py
> >> --> os.environ.setdefault("DJANGO_SETTINGS_MODULE",
> >> "my_geonode.local_settings")
> >> DJANGO_SETTINGS_MODULE=my_geonode.local_settings paver reset
> >> DJANGO_SETTINGS_MODULE=my_geonode.local_settings paver setup
> >> DJANGO_SETTINGS_MODULE=my_geonode.local_settings paver sync
> >> DJANGO_SETTINGS_MODULE=my_geonode.local_settings paver start**
> >> —
> >> You are receiving this because you were mentioned.
> >> Reply to this email directly, view it on GitHub
> >> <
> >> or mute the thread
> >> <
> >> .
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> or mute the thread
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
Ing. Alessio Fabiani
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail.