Installing GitList for Local Repos
While GitHub is an excellent solution for code collaboration and repository management, some individuals and companies prefer to maintain code in the intranet for security reasons. It is easy to provide warehouse access on the local intranet, but it is not that simple to have a friendly interface to interact with these warehouses and simplify team collaboration. Git comes with a web interface gitweb
, but it is not elegant and modern enough, it is difficult to view changes, authors and time, and browsing workspaces is also quite cumbersome. Some other solutions are difficult to install or the interface is not friendly enough. Recently I discovered GitList, a free and open source Git repository viewer. Its interface is very similar to GitHub, but it focuses more on conciseness and clarity. This article will guide you to set up your own Git repository viewer. Don't worry, it's simple, faster than installing WordPress!
Environmental preparation
This guide assumes that you are using a Debian-based Linux distribution, but GitList can run on any system. You need:
- Apache Server (enable
mod_rewrite
) or Nginx - Git
- PHP 5.3 or later
If it is not installed yet, please run it in the terminal:
sudo apt-get update sudo apt-get install php5 apache2 git
I also assume that your environment is as follows:
- Git repository path:
/home/bob/code
- Apache document root directory:
/var/www
- Git executable file path:
/usr/bin/git
- Apache root URL:
http://localhost
Apache users will access your Git repository, so you need to set the correct access permissions:
sudo chmod -R 744 /home/bob/code
Installing and configuring GitList
First, download GitList. You can choose the latest stable version or major version, but be aware that there may be bugs in the main version because the developers are still actively developing. After selecting the package, unzip it into the gitlist
folder in the root directory of the Apache document.
Next to configure GitList! Rename the config.ini-example
file to config.ini
, open it with a text editor and make sure its content is as follows:
[git] client = '/usr/bin/git' ; Git可执行文件路径 repositories = '/home/bob/code/' ; 仓库路径 ; 可以隐藏GitList中的仓库,为每个要隐藏的仓库复制此行 ; hidden[] = '/home/bob/code/SecretProject' [app] baseurl = 'http://localhost/gitlist' ; 应用的基准URL ; 如果需要为特定扩展名指定自定义文件类型,请在此处进行设置 [filetypes] ; extension = type ; dist = xml
The last step: Create a folder named /var/www/gitlist
in the cache
directory and give it the correct permissions:
cd /var/www/gitlist mkdir cache chmod 777 cache
Now visit http://localhost/gitlist
to check.
Help! Page not found!
GitList uses Apache's mod_rewrite
module to create a friendly URL. If the page is not found, make sure Apache is enabled: mod_rewrite
:
sudo a2enmod rewrite
Also make sure Apache can read the .htaccess
files in the GitList directory. .htaccess
Files are used to overwrite and add new rules for Apache directories. Open your default Apache website profile (usually located at /etc/apache2/sites-enabled/000-default
) and look for the following:
<Directory></Directory> Options Indexes FollowSymLinks MultiViews AllowOverride None Order allow,deny allow from all
Change the AllowOverride
option from None
to All
. Save changes and restart Apache:
sudo apt-get update sudo apt-get install php5 apache2 git
Custom
GitList interface is built using Twitter Bootstrap and LESS. The LESS file is located in the web/less
directory. A Makefile is provided, so you can generate the final CSS file by simply customizing the LESS file to your preferences and running web
in the make
directory. Of course, you need to install lessc
, which can be done easily by running npm install less
. GitList is powered by the Twig template engine, and all templates are located in the views
directory. To better understand how it works, it is recommended that you read the related Twig tutorial. After modifying the .twig
file, be sure to clear the contents of the cache
folder!
(Picture from Fotolia)
(The following is the FAQ part, which has been adjusted and streamlined according to the original content to avoid duplication)
FAQ (FAQ)
-
What are the prerequisites for installing GitList? Requires PHP 5.3.3 or later, Git and Composer.
-
How to clone a GitList repository? Run
git clone https://github.com/klaussilveira/gitlist.git
. -
How to configure GitList? Edit
config.ini
files, configure repository paths, Git clients, etc. -
How to install dependencies using Composer? Run
composer install
. -
How to set the
.htaccess
file? Make sure Apache is enabled and setmod_rewrite
toAllowOverride
.All
-
How to access GitList after installation? Access the URL of your GitList directory, such as .
http://localhost/gitlist
-
Apart from Apache, can GitList be used with other servers? Yes, for example, Nginx or IIS, but the configuration may be different.
-
How to update GitList? Run and
git pull
.composer install
-
Can you customize the appearance of GitList? You can modify the CSS file in the directory, but it may be overwritten when updating GitList.
public
-
What should I do if I encounter problems during the installation process? Check for error messages, refer to GitList issues on GitHub or seek help.
The above is the detailed content of Installing GitList for Local Repos. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

Session hijacking can be achieved through the following steps: 1. Obtain the session ID, 2. Use the session ID, 3. Keep the session active. The methods to prevent session hijacking in PHP include: 1. Use the session_regenerate_id() function to regenerate the session ID, 2. Store session data through the database, 3. Ensure that all session data is transmitted through HTTPS.

RESTAPI design principles include resource definition, URI design, HTTP method usage, status code usage, version control, and HATEOAS. 1. Resources should be represented by nouns and maintained at a hierarchy. 2. HTTP methods should conform to their semantics, such as GET is used to obtain resources. 3. The status code should be used correctly, such as 404 means that the resource does not exist. 4. Version control can be implemented through URI or header. 5. HATEOAS boots client operations through links in response.

The main function of anonymous classes in PHP is to create one-time objects. 1. Anonymous classes allow classes without names to be directly defined in the code, which is suitable for temporary requirements. 2. They can inherit classes or implement interfaces to increase flexibility. 3. Pay attention to performance and code readability when using it, and avoid repeatedly defining the same anonymous classes.

In PHP, exception handling is achieved through the try, catch, finally, and throw keywords. 1) The try block surrounds the code that may throw exceptions; 2) The catch block handles exceptions; 3) Finally block ensures that the code is always executed; 4) throw is used to manually throw exceptions. These mechanisms help improve the robustness and maintainability of your code.

There are four main error types in PHP: 1.Notice: the slightest, will not interrupt the program, such as accessing undefined variables; 2. Warning: serious than Notice, will not terminate the program, such as containing no files; 3. FatalError: the most serious, will terminate the program, such as calling no function; 4. ParseError: syntax error, will prevent the program from being executed, such as forgetting to add the end tag.

In PHP, the difference between include, require, include_once, require_once is: 1) include generates a warning and continues to execute, 2) require generates a fatal error and stops execution, 3) include_once and require_once prevent repeated inclusions. The choice of these functions depends on the importance of the file and whether it is necessary to prevent duplicate inclusion. Rational use can improve the readability and maintainability of the code.

PHP and Python each have their own advantages, and choose according to project requirements. 1.PHP is suitable for web development, especially for rapid development and maintenance of websites. 2. Python is suitable for data science, machine learning and artificial intelligence, with concise syntax and suitable for beginners.
