Q: Does GitLab support a search engine based on Elasticsearch or alike?
A: GitLab EE allows to leverage the search capabilities of Elasticsearch.
Q: Does GitLab provide project templates?
A: There are no project templates in GitLab at the moment.
Open issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/13210
Q: Do you have syntax coloring? For which languages? Is it extensible?
Q: Is there a max size (disk size) per project?
A: Projects have no limit in disk size. The size of each project is listed in the projects overview in the admin panel.
Merge request: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/1366
Q: Does GitLab supports groups of users?
A: GitLab does support user groups which allow you to group projects into directories and give users access to several projects at once.
Q: Does GitLab provide visibility levels for projects?
A: GitLab has three different visibility levels for each project: Public, internal, and private.
Q: Do you support default rights on users, not project?
Q: Does GitLab provide a way to block project creation for certain users?
A: GitLab admins can set a project limit for each user. If the limit is set to 0 the user cannot create any projects.
Q: Do blocked users count towards total user count?
A: No, only active users count towards total user count.
License FAQ: /license-faq/
Q: What kind of usage statistics are available for GitLab admins?
A: GitLab EE provides contribution analytics which provides an overview about the activity of issues, merge requests and push events of your organization and its members. The time period on which the analytics depend on, is spanned in three sections: last week, last month and last three months.
Q: How does GitLab provide log analysis?
A: GitLab has an advanced log system which enables the analysis of a GitLab instance using various system log files. Generally an admin can view the last 2000 lines of the log files in the logs section of the admin panel. Furthermore GitLab EE offers Audit Events to view security and audit events within the GitLab admin panel.
Log system: http://doc.gitlab.com/ee/logs/logs.html
Audit Events: http://doc.gitlab.com/ee/administration/audit_events.html
Q: What are the system requirements for a certain amount of users or repositories?
A: The respective hardware requirements with regards to the amount of users and repositories are listed in the GitLab documentation: http://doc.gitlab.com/ee/install/requirements.html#hardware-requirements
Q: Does GitLab support multi-server setups e.g. different servers for the database and each service?
A: Yes, e.g. this is the current setup for GitLab EE on GitLab.com.
Q: What is the process to request support?
A: For emergency issues that causes a standstill on a customer's operations, customers send an email to
email@example.com which will immediately notify a service engineer. For general issues and help with trouble shooting, customers send an email to
firstname.lastname@example.org which is then picked by any service engineer. There is no single point of contact necessary.
Support Handbook: /handbook/support/
Q: Does GitLab provide the possibility to have custom installations?
A: GitLab can be installed from source, which allows any customization. But the fast and reliable Omnibus package installation is recommended.
Q: What is the process to upgrade a GitLab instance?
A: Depending on the installation method and the GitLab version, there are multiple update guides in the documentation: http://doc.gitlab.com/ee/update/README.html
Q: Can I install and upgrade GitLab without an internet connection?
A: Yes. Our Omnibus packages are self-contained and require no internet access during installation, configuration, or afterwards.