Tag Info

Hot answers tagged

4

You are much better off tracking changes inside the machine, as git etc. won't work very well with a large binary blob like a VM disk image. To be able to roll back to another state, snapshots are an excellent solution, but they have a performance impact. The best method (IMHO) is to use a configuration management tool (e.g. Puppet) and track the changes ...


1

Ah, I was looking for the wrong revision when I was searching. Turns out I can do: cat ~/git/<app>.git/refs/heads/master


1

After many tries I've found the solution. The problem was in incorrect VirtualHost configuration for git-http-backend. Here's my working config: <IfModule mod_ssl.c> <VirtualHost _default_:443> DocumentRoot /git/myrepos SetEnv GIT_PROJECT_ROOT /git/myrepos SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /myrepos/ ...


1

/var/opt/gitlab/backups by default. https://gitlab.com/gitlab-org/gitlab-ce/blob/a64d0f79173301dd86db073e9b6a329b56554dbd/doc/raketasks/backup_restore.md says that: This archive will be saved in backup_path (see config/gitlab.yml) Then ...


1

This doesn't sound like an ideal application for Git. Git isn't oriented toward storing large binary files. You might look at the git-annex project, which uses Git for version control of binary files, but doesn't actually store the binaries in Git. If you're just talking about dynamically swapping a hierarchy of directories and files you could do this ...



Only top voted, non community-wiki answers of a minimum length are eligible