-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add instructions for installing required software packages #261
Conversation
|
||
* Python 3.4 | ||
* PostgreSQL 9.4 / PostGIS 2.1 | ||
* virtualenv (1.7 or higher) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- ElasticSearch 2.3.2
- Redis 2.8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK thanks.
I have added those components to the list at 727756d
Not sure what packages should be installed though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For redis: redis-server
.
And for ElasticSearch the DEB can be downloaded from here: https://www.elastic.co/downloads/past-releases/elasticsearch-2-3-2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, updated!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that on the demo server ES 2.1.0 is still used. Should we upgrade to 2.3.2 on this server?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would make sense, yes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK I will open a ticket for the sysadmins.
I don't know if it is related but when I try to run the indexing on my instance on the dev server, the load skyrockets (I have succeeded to index the main DB though...).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if it is related but when I try to run the indexing on my instance on the dev server, the load skyrockets (I have succeeded to index the main DB though...).
Thanks for noticing (my work station is too powerful...). See #281
I have just added GEOS to the requirements, see 27430fa See also c2corg/v6_ui#446 I just wonder if this was necessary since GEOS is required by PostGIS I think and should be pulled when installing PostGIS, shouldn't it? |
PostGIS does not need the package with the header files (libgeos-dev) which seems to be required by Shapely. |
OK, then my recent change makes sense. Thanks for the tip! |
@@ -23,6 +23,7 @@ phpserialize==1.3.0 | |||
kombu==3.0.35 | |||
redis==2.10.5 | |||
apscheduler==3.1.0 | |||
requests==2.9.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can then remove it from dev-requirements.txt.
And yes, it is correct. It should be listed under requirements.txt
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, you answer my question below :P I will remove it from dev-requirements.txt.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK I have updated the PR. Looks good?
@tsauerwein Your link http://stackoverflow.com/a/31234304 was the good one to fix the "make install" crash with bcrypt. With the packages now listed in the README @gberaudo I had to add
Do you think it's OK? Should The PR is ready for reviewing. |
Looks good, thanks! |
Thanks for reviewing @tsauerwein ! |
Similar to c2corg/v6_ui#324