search

datagovuk / dgu-vagrant-puppet

[unmaintained] Container environment for booting fresh DGU virtual machines. Create VMs with Vagrant, configure them with Puppet.
37 stars 29 forks source link

Rename of shared_dguk_assets repo broke the `togo` branch installation #55

Closed CarlQLange closed 9 years ago

CarlQLange commented 9 years ago

Broke things in new and interesting ways - the clone_all script then checked me out of togo in my main dir because the repo didn't exist and it travelled up the filesystem, and because the master branch doesn't have a provisioner set in the Vagrantfile it was causing weirdness, and then when I changed back, it made npm give me ENOPACKAGEJSON. Fun, if fairly shallow, rabbithole.

Anyway, will add pull request later, just making sure it's known. Think it's just renaming the repo in git_clone_all.sh.

Is togo still actively supported, by the way? Or is there a new, better way to do things?

CarlQLange commented 9 years ago

Whoops, I was wrong - the repo still exists https://github.com/datagovuk/shared_dguk_assets. Sorry about that!

CarlQLange commented 9 years ago

yep - I checked my logs, for some reason my connection dropped my initial clone of shared_dguk_assets, but it still created the empty directory, and then the provisioner created npm-debug.log inside it, so git wouldn't clone into the directory on re-run of git_clone_all.sh. Fun times.