-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
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
What's the proper way to install GeoNode core for development? #11588
Comments
HI @gbassiere
That's true, paver should work out of the box, feel free to open an issue on it. Related to the development there are two main choices: The docker way is the easiest to have everything already prepared
We use circleCI to run the whole test suite for each PR. So if something happen dont worry :) |
Hi Mattia, Thanks for your guidance. I think I'm now close to have geonode-core properly configured. Paver didn't work because of the Unfortunately, I'm still unable to run the test suite :
I get the same results with Docker or without. I don't quite understand what's wrong in my setup. Is it possible that the test suite depends on some parameters in
I'm aware that CircleCI will check any incoming pull request but I feel like running the test before submitting a PR is the least I could do. Also, it is much easier to fix a breaking test if I can run it on my local instance. Best regards |
I took inspiration from CircleCI config to have the test suite running. For anyone interested, here is how I run tests using Docker:
I'm using |
I'm running Ubuntu and installed all necessary packages, I have both Postgresql 14 and Tomcat 9 up and running on localhost. Geoserver works fine. Then:
I can see a bare GeoNode running on http://localhost:8000. Everything seems fine.
But paver commands do not work:
It seems like there is an import loop because
local_settings
importsettings
which importserializer
which import the project's settings module (e.g.local_settings
). I've been able to use paver after I've editedpavement.py
so that settings are imported from local_settings module. I feel like paver should work out-of-the-box, without editing files under version control. Therefore, I must have done something wrong while installing but I basically followed the documentation...Then I tried to run the test suite, eihter with
paver test
orpython manage.py test
or./test.sh
. But I keep on getting errors such as this one:Many tests returned this error:
connection already closed
. What could be wrong with the database? The same database config works fine withrunserver
.I'm about to submit a fix for PR #10321 but I wish I could run Django's test suite to validate that my contribution don't break anything.
Regards
Gilles
The text was updated successfully, but these errors were encountered: