Skip to content
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 Binder playbook #67

Closed
wants to merge 1 commit into from
Closed

Conversation

jraddaoui
Copy link
Contributor

With stable/0.8.x and qa/0.9.x options. WIP.

Fixes #66.

@jraddaoui jraddaoui self-assigned this Apr 3, 2018
@jraddaoui
Copy link
Contributor Author

jraddaoui commented Apr 3, 2018

Hi @hakamine and @scollazo,

This is in a working state but I'd love to hear your thoughts about the 'stable' vs 'qa' situation. The issues I'm facing:

  • Both require PHP 5 to work, that's why I'm adding only and Ubuntu Trusty option.
  • Elasticsearch 1.x is used in stable while 5.x is used in qa.
  • The Elastic ES Ansible role doesn't support ES < 2.x.
  • Our ES role doesn't support ES 5.x.
  • The Elastic ES role doesn't install Java 8 in Ubuntu 14.04 as it's not available by default in there.

Therefore, I have ended with two different playbooks and requirements instead of only a few var changes like I was hopping for.

Do you think I should create two different folders? Maybe 'binder-qa' and 'binder-stable'. Or do you have a better option?

Thanks.

@jraddaoui jraddaoui added the Request: help wanted Someone working on the issue lacks the skills/knowledge to move forward and needs help. label Apr 3, 2018
@qubot qubot force-pushed the dev/issue-66-binder-playbook branch from 42c932e to 939c93d Compare April 3, 2018 17:54
@jraddaoui
Copy link
Contributor Author

jraddaoui commented Apr 3, 2018

Depends on artefactual-labs/ansible-atom#19, I'll change the AtoM role version once that's merged and improve the readme(s) when we decide what to do with the 'stable' vs 'qa' situation.

@qubot qubot force-pushed the dev/issue-66-binder-playbook branch from 939c93d to ef71565 Compare April 3, 2018 19:47
@qubot qubot force-pushed the dev/issue-66-binder-playbook branch 4 times, most recently from a34189f to 5d29e6f Compare May 12, 2018 20:24
@qubot qubot force-pushed the dev/issue-66-binder-playbook branch 2 times, most recently from 56326fd to dd6e19a Compare May 20, 2018 22:58
Over Ubuntu 14.04, with stable/0.8.x and qa/0.9.x options.
@qubot qubot force-pushed the dev/issue-66-binder-playbook branch from dd6e19a to 3f5994a Compare October 25, 2018 09:38
@jraddaoui jraddaoui removed the Request: help wanted Someone working on the issue lacks the skills/knowledge to move forward and needs help. label Jun 30, 2019
@jraddaoui jraddaoui removed their assignment Jun 30, 2019
@jraddaoui jraddaoui closed this Jun 30, 2019
@jraddaoui jraddaoui deleted the dev/issue-66-binder-playbook branch June 30, 2019 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Task: Create Binder playbook
1 participant