We're not moving to git.
If we move to git, in 12 months time there'll be the next fashion fad, and people will be moaning at us to move again.
No.
adam.
On 10/03/2011 02:23, Pas wrote:
On 2011.03.09. 12:59, Adam Armstrong wrote:
On 09/03/2011 11:56, Nikolay Shopik wrote:
I'm willing to provide deb package for Observium if anybody started work on that, please let me know. Also it is possible to make Observium run from sub-directory instead of virtual-host, like that http://example.com/observium? I did tried some rewrite rules on apache w/o luck.
It should work, but it's a pain. We generally forget that requirement when adding new features, because very few people do it.
In general we assume that if you need to run Observium, you control your DNS, and so a subdomain isn't a problem.
A debian package would be nice, but note that we like to use daily SVN to keep instances updated. We don't like people to use releases.
adam.
I'd recommend looking at how Jenkins does releases. They use git [1] and do continuous integration, and there's a release every ~7-9 days, basically weekly stable builds. And they build .debs [2] from these stable builds.
Also, I think a migration to git and/or github might have some great long term benefits. (Pull requests are easier to manage than patches, plus github's issue tracker is nice.)
There's a Debian package for phpMyAdmin, RedMine and a lot of web-interfaced software, most of them deploy into /usr/share/ and put symlinks all over the place and heavily utilize shell scripting magic (RedMine's init.d script comes to mind).
[1] http://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_main_trunk/566/git/...