5,705
edits
Changes
Jump to navigation
Jump to search
Line 32:
Line 32: − + − We do not have root on git.sugarlabs.org. Put the following aliases in your+ − ~/.bashrc to quickly switch to the Gitorious production, test and development − environments: − alias gitorious='sudo su - gitorious' + − alias gittest='sudo su - gittest' + − alias gitdev='sudo su - gitdev' − alias db='mysql -h db1.osuosl.org -u sugarlabs_git -p sugarlabs_git_dev' − === Get a MySQL prompt ===+ − type "db" at the prompt, then give the db password − from ~gitorious/config/database.yml − + − UPDATE projects SET user_id=(SELECT id FROM users WHERE login='jasg') WHERE slug='labyrinth'; + + + + + + + + + − + − UPDATE repositories SET user_id=(SELECT id FROM users WHERE login='jasg') WHERE name='mainline' AND project_id=(SELECT id FROM projects WHERE title='poll'); − === Add committer ===+ − INSERT INTO committerships SET + − user_id=(select id from users where login='bernie'),+ − repository_id=(SELECT id FROM repositories where+ − project_id=(SELECT id FROM projects WHERE title='sugar') AND name='mainline'), − kind=2, created_at=NOW(), updated_at=NOW(); − − === Hijack account to reset password === − update users set email='YOUREMAIL' where login='USER'; − − Then make Gitorious send you a password reset email. − − update users set email='OLDEMAIL' where login='USER'; − − === Zapping a user account === − − WARNING: to kill a user account, make sure you also remove *ALL* its associated records − from all tables, or Gitorious will break in non-obvious ways. − − SELECT id FROM users WHERE login='demian'; − DELETE FROM committers WHERE user_id=666; − DELETE FROM events WHERE user_id=666; − DELETE FROM comments WHERE user_id=666; − DELETE FROM merge_requests WHERE user_id=666; − DELETE FROM repositories WHERE user_id=666; − DELETE FROM projects WHERE user_id=666; − − NOTE: tch pointed out that Rails applications often provide a higher-level method − in class User which deletes the record and its associated entries. However, our − deployed version of Gitorious does not seem to provide it. − − === Restart gitorious after code/config changes === − touch tmp/restart.txt
→Notes
|}
|}
=== Gitorious environments ===
=== Database tweaks ===
To make runtime changes in Gitorious database, follow regular Rails workflow - run {{Code|scripts/console}}:
cd /srv/gitorious/app
sudo -u gitorious RAILS_ENV=production script/console
It is regular Ruby console and all feature like {{Code|TAB}} completion work. To tweak Gitorious data, just use its [http://gitorious.org/gitorious/mainline/trees/master/app/models model classes], e.g.:
=== Change project owner ===
# search of particular object by its attributes
user = User.find_by_login("user")
project = User.find_by_title("project")
# change object attributes
project.owner = User.find_by_email("foo@bas")
project.save!
# destroy object and all its dependencies
user.destroy
=== Change repo owner ===
=== Tips ===
# reset user password
user = User.find_by_login("user")
password_key = user.forgot_password!
Mailer.deliver_forgotten_password(user, password_key)
== Upgrade notes ==
== Upgrade notes ==
Upgrade will be triggered on every puppet session (if there is such need), vcs repository will be rebased to the HEAD commit with all related changes like database migration.
Upgrade will be triggered on every puppet session (if there is such need), vcs repository will be rebased to the HEAD commit with all related changes like database migration.