I've had experience maintaining a private Gitolite installation; we ended up migrating to Gitlab.
Managing SSH keys and repo permissions from the command line was just enough of a learning curve for users (internal developers) that they really didn't like it and tended not to use it unless forced. Gitlab has had much less pushback.
Really, it depends on whether your users are more comfortable with the command line or web interface.
Also, I found Gitolite to be a bit easier to administer than Gitlab. Gitlab is a Rails web app, with lots of moving parts. Gitolite is essentially a bunch of Perl scripts which use authorized_keys and SSH_ORIGINAL_COMMAND hackery to convince ssh to do the actual authenticating.
If you already know and love deploying Rails web apps (I don't), then you might find Gitlab easier.
Managing SSH keys and repo permissions from the command line was just enough of a learning curve for users (internal developers) that they really didn't like it and tended not to use it unless forced. Gitlab has had much less pushback.
Really, it depends on whether your users are more comfortable with the command line or web interface.
Also, I found Gitolite to be a bit easier to administer than Gitlab. Gitlab is a Rails web app, with lots of moving parts. Gitolite is essentially a bunch of Perl scripts which use authorized_keys and SSH_ORIGINAL_COMMAND hackery to convince ssh to do the actual authenticating.
If you already know and love deploying Rails web apps (I don't), then you might find Gitlab easier.