I have not used the virtual appliance, but i'll strongly recommend gitlbhq,
we are using it to  cater hunderds of repos and 1700+ users. Initially we
struggled to maintain gitorious based system (due bugs, no support for
private repos etc)

my 2 cents


On Tue, Jun 5, 2012 at 9:11 PM, Edward Ned Harvey <[email protected]>wrote:

> > From: [email protected] [mailto:[email protected]]
> > On Behalf Of John Coleman
> >
> > Yale University is considering whether to purchase the Github
> > Enterprise virtual appliance to run on premises.  We'd like to hear
> > from existing customers about the appliance and the support they
> > receive from Github.  If you'd be willing to speak with us, please
> > email me privately at [email protected], or, if you wish, share
> > your experiences with the list.
>
> I'm currently supporting a site using Github Enterprise.  You pay per block
> of 20 users, per year.  They have different ways you can run it - In our
> case, we downloaded a vmware virtual appliance, and we simply launched it
> in
> our existing vmware infrastructure.
>
> If you have a lot of users, and/or it's a free open source product, then
> most likely you're better off to use a "standard" git server without
> github,
> or just use github itself (because they will host unlimited open source
> products for free.)  If you're considering github enterprise, I have to
> assume, it's because you have a private product that you will not expose to
> massive numbers of people.  You want to host it yourself for reasons of
> security/privacy.
>
> Out of the box, it supports both https and ssh.  This is important, because
> many users find themselves in corporate networks that disallow outbound
> ssh.
> The main difference between the two is:  ssh is authenticated using keys,
> so
> you never have to enter a password.  https is authenticated via password,
> and your git client has the optional of being configured to cache the
> password for a limited time, but not for infinite time or beyond reboots.
>
> The main advantage of GHE versus a standard git server is:  GHE wraps a
> bunch of social stuff together.  Wiki, bug tracker, etc are included
> out-of-the-box.  Zillions of plugins also exist for all the usual social
> network / collaborative software development suspects.  If you want, you
> can
> try to "build your own github" by going and building/installing all the
> social tools you want with your vanilla git server.  They all exist; it's
> just a question of effort versus money to buy the prebuilt thing.
>
> Unfortunately the GHE product doesn't have any way to do backups.  So
> hopefully you put it on some storage where you can snapshot & backup
> yourself.  Or, maybe the only stuff you care about is the actual contents
> of
> the repository, in which case, you can simply create some cron job
> somewhere
> to clone/pull your repo.  That would count as "backup" depending on your
> needs.
>
> Their support is pretty good - I just email them, and typically within an
> hour or two, I have a very knowledgeable reply.  There is no emergency
> phone
> support or anything like that.
>
> Anything else you would like to know?
>
> _______________________________________________
> Tech mailing list
> [email protected]
> https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
> This list provided by the League of Professional System Administrators
>  http://lopsa.org/
>
_______________________________________________
Tech mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to