Mar 7, 2016
README was quite old
|
|
|
18 |
See [this blog |
|
19 |
post](http://betatim.github.io/posts/project-everware-reusable-science/) |
|
20 |
for more information about what `everware` is and how it can be useful. |
|
21 |
|
|
22 |
The idea for everware originated at the CERN Webfest 2015. The |
|
23 |
original everware team consists of |
|
24 |
[@OmeGak](https://github.com/omegak), |
|
25 |
[@ibab](https://github.com/ibab), [@ndawe](https://github.com/ndawe), |
|
26 |
[@betatim](https://github.com/betatim), |
|
27 |
[@uzzielperez](https://github.com/uzzielperez), |
|
28 |
[@anaderi](https://github.com/anaderi), and |
|
29 |
[@AxelVoitier](https://github.com/AxelVoitier). |
|
Mar 17, 2016
Updating install instructions and splitting config files
|
|
|
55 |
- [Create a Github OAuth application](https://github.com/settings/applications/new) |
|
56 |
with URL `http://localhost:8000/` and callback URL |
|
57 |
`http://localhost:8000/hub/oauth_callback` |
|
58 |
- Enter you OAuth information into `env.sh` and `source env.sh`. You will |
|
59 |
have to set these environment variables every time before running `everware` |
|
60 |
|
|
61 |
- If you are on **Mac OS** make sure the VM in which docker runs is |
|
62 |
started (`docker-machine start <vm-name>`) and your environment is |
|
63 |
setup properly (`docker-machine env <vm-name>`). Start `everware` with: |
