n lun., 2016-02-29 at 05:35 +0100, Sébastien Luttringer wrote:
On mar., 2016-02-23 at 01:18 +0100, Sébastien Luttringer wrote:
On dim., 2016-01-10 at 00:57 +0100, Sébastien Luttringer wrote:
Here is a short planning if we go through this option: 1) setup a new cgit on luna (with nginx and uwsgi) 2) copy repos for testing purpose 3) create gitshell access to users 4) plan official migration date 5) reduce dns ttl of projects.al.org 6) wait for it 7) cut write access to gerolde repo 8) final repo sync 9) update dns records and restore ttl 10) take a beer
.. I'm planning to finish the config and annonce the migration on a-d-p@al.org before the end of the week.
Cheers,
Ok, so I'm late, as usual...
Where we are now: - git.al.org dns is public. - the new download url (https, git, ssh) are working. - cgit config looks good. - a crontab is syncing git repos every hour (from gerolde to luna only). - users with git repo have been created on luna (via ansible). - I moved the remaining fellows devs git repos under the "Obsolete or Dead Projects".
As url will be redirected (except for pushing) I would plan a short migration delay. Something like this Saturday night CET.
If no objection, I will start discutions tomorrow about migration in a-d-p@al .o
Lukas objected to the move to the community version of cgit because we have a patch to remove the branch switch for svntogit tree in order to save few Kibibytes. This patch was rejected by upstream and he thinks it's not a valuable solution to add it to the community package. So, I will move back to the version we maintain in order to move forward to the migration. Cheers, -- Sébastien "Seblu" Luttringer https://seblu.net | Twitter: @seblu42 GPG: 0x2072D77A