Hello,
just thought I'd give a heads-up on two small additions in mainline.
Feedback & merge requests are very welcome on both, I'll probably
iterate on both of them a bit.
1) CLI diagnostics rake tasks
Earlier this spring we added a web diagnostics page to make it easier to
find problems in gitorious installations. (see /admin/diagnostics in the
web UI). I've now also added a quick way to access the same info from
the CLI via two new rake tasks. " rake diagnostics:healthy" will check
if everything is set up and running ok (returns true|false). If
something is wrong you can get more detailed information with "rake
diagnostics:summary", kinda like the web diagnostics page. Note that
both rake tasks must currently be explicitly invoked by the same user
that owns the gitorious installation (usually the "git" user).
Example: sudo su git -c "RAILS_ENV=production bundle exec rake
diagnostics:summary"
More info:
https://gitorious.org/gitorious/mainline/commit/6cd4f938af07dde195bbace31a78d7f1d3a9015b
2) Backup rake tasks
I was inspired by an earlier discussion of Gitorious backup/restore
procedures here, and added Gitorious rake tasks (backup:snapshot and
backup:restore) for snapshotting the Gitorious instance to and from a
single tarball. Note that it's only tested on a simple stock Ubuntu
installation of Gitorious so far, but feel free to start playing with it
(or just use it as inspiration/blueprint to create your own backup
regimes - it may not cover the needs of some more custom/exotic
Gitorious configurations out there)
Examples:
sudo bundle exec env TARBALL_PATH="current_snapshot.sql" rake
backup:snapshot
sudo bundle exec env TARBALL_PATH="current_snapshot.sql" rake backup:restore
(Assumptions and examples more thoroughly documented in
/lib/tasks/backup.rake)
More info:
https://gitorious.org/gitorious/mainline/commit/60db3854e0028f003fb78081d13dd937d74ea9cc
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
