|
From: | Urs Liska |
Subject: | Re: RFC: new location for openLilyLib repository |
Date: | Fri, 13 Nov 2015 11:58:25 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 |
Am 13.11.2015 um 10:57 schrieb Davide
Liessi:
2015-11-13 6:02 GMT+01:00 Henning Hraban Ramm <address@hidden>:Why not combine the options? Use GitHub as long as it makes sense, but always keep a mirror on OLL server.That's my opinion, too: option a), plus mirroring the repositories at git.openlilylib.org. It seems discussion settles towards this, so we'll go that route. With regard to mirroring I think I'll do the following (please tell me if someone has a better solution). Create a Git repository on git.openlilylib.org's server (that is, a local repository on the filesystem, not in the server's Gitlab installation and have the Github repository as 'origin'. Add a web hook on the Gitlab repo that triggers a script on the openlilylib.org server. This script will fetch the updates from Github and can optionally perform further tasks, e.g. build openLilyLib documentation and deploy it. As I don't want to require an http server kept running for this task I would try to implement it in a way that the web server (Nginx) calls the script when the Github web hook calls a certain URL. I don't know how to do that yet but I assume it'll work similarly to calling up PHP stuff through fastCGI. ### One other thing to be discussed is the actual naming. As a prerequisite I have significantly cleaned up the namespace below https://github.com/openlilylib so that there are only three repositories left. However, it's not clear how I should proceed now. Currently we have the "openlilylib" repository which actually contains two different things:
What we want to achieve is:
This set-up will have the big advantage that we can keep the
existing repository so no user code will break. Whenever something
is moved to the new structure we can make the current functions
issue a deprecation warning, telling the user where the new
functionality should be taken from (I have already done this
several times and provided some helper functions). I suggest (and if noone objects will do it)
|
[Prev in Thread] | Current Thread | [Next in Thread] |