README out of date, no description of setup for non integrated Vagrant file.

[openi-fokus]

The recent changes will need to be supported with a documentation / instructions, otherwise the setup can not be understood. The README is out of date and no description of setup for non integrated Vagrant file is given.

[philipobrien]

The README does need to be updated, but the steps to setup the environment are the same now as they were before

[openi-fokus]

The steps will not result in the .sh files availability if I am not mistaken. (You need to actually clone the repo to get the .sh's). Concerning the outdated README: I think it was outdated before as well on how to use the dev env (or we have outdated .sh files like start_openi and create symlinks).

[philipobrien]

But you always had to clone the repo to get the vagrantfile anyway? So nothing has changed in that regard. There are outdated files, but that doesn't affect anything. You still follow the same steps to get the vm configured

[openi-fokus]

You did, but outside of the machine, unless you kept the path as "" or "./" they should not be visible in the machine, no? As to the rest of the files: I agree I thought we do it in one bug report but I guess two will do too.

[philipobrien]

Well no, because I imagine you would want this repo in the same directory as the other openi repos. Following that logic would then mean the dev-env repo would be synced to the vm, and the scripts also. If you have a better approach by all means implement it and push the changes up

[openi-fokus]

Maybe we are missing each other here. From the README:

1) git clone this repo
2) vagrant up && ssh
3) ./provision_openi.sh
=> Does provision_openi.sh exist? I think it doesn't, no?

So if we want the scripts we need to do something like:

1) git clone this repo
2) vagrant up && ssh
3) git clone this repo
4) cd this repo
5) ./provision_openi.sh

That's all I meant.

[philipobrien]

Yeah fair enough, the steps could be clearer. I'll leave it for now though because Donal is going to break up the bootstrap.sh further tonight

On 17 September 2014 17:24, openi-fokus notifications@github.com wrote:

Maybe we are missing each other here. From the README:

1) git clone this repo 2) vagrant up && ssh 3) ./provision_openi.sh => Does provision_openi.sh exist? I think it doesn't, no?

So if we want the scripts we need to do something like:

git clone this repo cd this repo ./provision_openi.sh

That's all I meant.

— Reply to this email directly or view it on GitHub https://github.com/OPENi-ict/openi-dev-env/issues/12#issuecomment-55920117 .

[openi-fokus]

No problem, sorry for not being clear enough. I posted it specifically as a bug instead of changing it because I thought as well that the scripts will probably be changed further (reminder). Reassigning.

[dmccarthy-dev]

The provision_openi.sh files used to be created while the Vagrant image was provisioning, does it not do that any more?

[dmccarthy-dev]

All files in the host machines directory that runs vagrant are available on the guest machine in the directory /vagrant. The readme now reflects the scripts new location.