Shared folders

[mortenwh]

At the moment we define shared folders for each virtual machine, e.g., shared/develop_vm. Is this necessary? Why not have just one folder shared/code or something like that?

[akorosov]

No, I would like to isolate development in different machines. Why do you actually need several machines if you use the same code?

[mortenwh]

Presently, we have the following vm's: course, geospaas_core, doppler, metsarvind, travis. They all use nansat.

As long as you provision your machines before switching from one to another, version control should be handled well with ansible.

On 7 March 2017 at 15:28, Anton Korosov notifications@github.com wrote:

No, I would like to isolate development in different machines. Why do you actually need several machines if you use the same code?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nansencenter/geo-spaas-vagrant/issues/1#issuecomment-284736150, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGqBbkYpy8_hHAZN95WKPICV3AplNnsks5rjWmAgaJpZM4MVcjQ .

-- T.: (+47) 915 47 844

[akorosov]

In fact it is very easy to share code etc. between selected VMs. Just set dev_sources_dir (to be found in group_vars) variable to be the same for some selected hosts.

On 07/03/17 16:27, Morten W. Hansen wrote:

Presently, we have the following vm's: course, geospaas_core, doppler, metsarvind, travis. They all use nansat.

As long as you provision your machines before switching from one to another, version control should be handled well with ansible.

On 7 March 2017 at 15:28, Anton Korosov notifications@github.com wrote:

No, I would like to isolate development in different machines. Why do you actually need several machines if you use the same code?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nansencenter/geo-spaas-vagrant/issues/1#issuecomment-284736150, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGqBbkYpy8_hHAZN95WKPICV3AplNnsks5rjWmAgaJpZM4MVcjQ .

[mortenwh]

hmm - ok, so we don't actually have a standard of setting 'dev_sources_dir'='_vm' - it has just been convenient until now...? what if I just call my dev_sources_dir "develop"?

On 7 March 2017 at 16:35, Anton Korosov notifications@github.com wrote:

In fact it is very easy to share code etc. between selected VMs. Just set dev_sources_dir (to be found in group_vars) variable to be the same for some selected hosts.

On 07/03/17 16:27, Morten W. Hansen wrote:

Presently, we have the following vm's: course, geospaas_core, doppler, metsarvind, travis. They all use nansat.

As long as you provision your machines before switching from one to another, version control should be handled well with ansible.

On 7 March 2017 at 15:28, Anton Korosov notifications@github.com wrote:

No, I would like to isolate development in different machines. Why do you actually need several machines if you use the same code?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nansencenter/geo-spaas- vagrant/issues/1#issuecomment-284736150, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGqBbkYpy8_ hHAZN95WKPICV3AplNnsks5rjWmAgaJpZM4MVcjQ .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nansencenter/geo-spaas-vagrant/issues/1#issuecomment-284756417, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGqBU7Zwo0cQ8ojfURvCAm7MAw7fHgEks5rjXlBgaJpZM4MVcjQ .

-- T.: (+47) 915 47 844

[mortenwh]

I have been running with an src directory on several machines now. It seems to work fine except that it crashes if the the database setup (i.e., the apps) differ between the vm's. This could be solved by calling the geospaas-project up after the vm-name, or putting this folder in the vm itself - like /home/vagrant/geospaas-project