-
Notifications
You must be signed in to change notification settings - Fork 0
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
Intial draft of installation guide #25
Intial draft of installation guide #25
Conversation
Some notes: I wrote the install instructions whilst going through the process on a fresh Ubuntu VM (in csewell-test on CSCS OpenStack), which now works (after conda-forge/aiida-core-feedstock#31). You might want to comment, since it feeds into the other discussion we've had e.g. in chrisjsewell/activate_aiida#1. Note that I wrote the install instructions whilst going through the process on a fresh Ubuntu VM (in csewell-test on CSCS OpenStack) The next steps is intended to be reminiscent of:
Here they use a lot of raw HTML; for the panels and the "accordian" drop downs. Currently I have added |
In c946c9f I've also added a panels directive. They look like this: |
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 a lot @chrisjsewell !
The panels look great!
I see it requires a bit of extra python code but I'd be ok with this if we all agree that these panels are what we want.
As for using conda as the default route, I think there are some open questions that would be good to discuss with a broader audience.
docs/source/intro/get_started.rst
Outdated
Installation | ||
============ | ||
|
||
There are numerous routes to setting up the full AiiDA environment, |
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.
"numerous routes" should probably be a link to the place where they are listed
docs/source/intro/get_started.rst
Outdated
depending on your use case. | ||
Here we first provide the simplest approach for installation on your local computer. | ||
|
||
`Conda <https://docs.conda.io>`_ provides a cross-platform package management system, |
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.
While, until you arrived, I've been the guy in the AiiDA team pushing most for supporting the conda route, I still feel that before we make conda the default installation path we need a little more testing of this for production.
I guess, so far, you are the only one using the aiida-core coda package (? we should ask!).
Since the availability with python 3.6-3.8 has now been taken care of, my main remaining doubts are these:
- In my experience, people are easily confused when mixing
pip
andconda
installations of packages and the will need to use pip to install most of the plugins. How can we effectively mitigate this? - Do people prefer to have Postgresql & rabbitmq be a system service (that restarts when they restart their computer) or are they fine starting them manually every time?
I think we should discuss these two questions within the AiiDA team and, possibly, also in the plugin-developers
github team.
And, if in the end we decide to go with conda, I'd be happy to integrate your aiida-active script in to the aiida.services
package (or add a perhaps slightly reduced version of it as a dependency).
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.
Yes certainly this requires a group decision. The main thing with Conda is that it works cross-platform, so in this "quick install" I don't have to complicate things with discussing the OS dependent installations of the services. Obviously there will also be the advanced/detailed installation section, where I will go in to more detail about the different routes to setting up the services.
In my experience, people are easily confused when mixing pip and conda installations of packages
What would you say exactly is the confusion? Do we just need to say that you can use pip
within a conda environment?
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.
What would you say exactly is the confusion? Do we just need to say that you can use pip within a conda environment?
I've often heard of problems with dependencies being overwritten by pip / conda when doing this (e.g. pip installs a different version of a dependency without conda being informed, etc.). This can be very nasty, up to the point where people no longer know how to fix the problem.
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.
This can be very nasty, up to the point where people no longer know how to fix the problem.
Well just start again from a fresh environment 😉 Personally I have never had this problem, and the other thing is that it is very easy with Conda for people to share conda-env.yaml
(which as you know can include conda and pip packages) containing version specifications that are known to be compatible.
But either way we should definitely be encouraging the use of isolated environments: e.g. https://medium.com/@krishnaregmi/pipenv-vs-virtualenv-vs-conda-environment-3dde3f6869ed
As for the drop-down stuff, we are already using something similar here We should just decide which one we prefer; then we can drop one of the two implementations. |
Ta, yes obviously it was easier to quickly code these up internally, but I could imagine extracting them into some packages in https://github.com/executablebooks at some point. |
Co-authored-by: Leopold Talirz <leopold.talirz@gmail.com>
Yep my ones better 😉 I may also eventually fold my one in to executablebooks/sphinx-togglebutton#11 |
Replaced by aiidateam#4011 |
No description provided.