Closed ingomueller-net closed 8 years ago
ingomueller-net
commented
8 years ago Another disadvantage of having oms-core as a submodule of ldap-poc is that it does not work well with the fork-merge-model: if I make a pull request of the oms-core repository, I also have to make one for the ldap-poc repo, and they should be forked-in at the same time. Deploying with puppet would mean that only oms-core has to be changed.
Original comment by: Ingo Müller
ingomueller-net
commented
8 years ago BTW, a disadvantage of deploying via puppet is that either you can only run things that are pushed to the server (which is obviously not what we are going to do), or you have to ssh to the guest for development. The latter is fine for me, but it's not ideal. Maybe there are other ways to work around...
Original comment by: Ingo Müller
ingomueller-net
commented
8 years ago
When started with vagrant from a windows host, /vagrant/oms-core is on a windows file systems, which does not support symlinks. Symlinks however are necessary to install node packages with
npm.I am not sure what the best deployment model is yet. An alternative to the current one (having oms-core as submodule of the vagrant repository) is to have puppet clone it from within the vagrant box (for example to
/srv/aegee/calaf/).