Installing Gibbon Git Server is straightforward and requires no special installer. Follow the steps below to get it up and running on your Windows machine.
First, you’ll need to clone the Gibbon Git Server repository to your local machine.
git clone https://github.com/Code-iX/Gibbon-Git-Server.git
cd Gibbon-Git-Server
Once you have the code on your machine, you need to publish the application. This step builds the app and prepares the files for deployment.
Ensure that you have the .NET Core SDK installed (you can check by running
dotnet --version
).
Run the following command to publish the application:
dotnet publish -c Release -o ./publish
This command compiles the project in release mode and outputs the files to a folder named publish
.
Now that the application is published, you’ll need to adjust the configuration settings to match your environment.
Open the appsettings.json
file in the publish
folder.
Update the connection string to point to your preferred database. By default, SQLite is configured, so you can leave this as-is for a simple setup.
Example of the default SQLite configuration:
{
"ConnectionStrings": {
"DefaultConnection": "Data Source=app_data/GibbonGit.db"
}
}
Now that the application is published and configured, it’s time to deploy it.
publish
folder you created earlier.http://localhost
).For simpler setups, you can run Gibbon Git Server directly using the Kestrel web server, which comes built-in with ASP.NET Core.
publish
folder in your terminal.
dotnet Gibbon-Git-Server.dll ```
5000
. You can access the web interface at http://localhost:5000
(or the configured port).Once the server is running, open your web browser and go to the following URL:
http://localhost
or the domain/port you configured in IIS.http://localhost:5000
or the port you configured in appsettings.json
.You should see the Gibbon Git Server login page. From here, you can start managing repositories, users, and more.
That’s it! With just a few simple steps, you can have Gibbon Git Server running on your Windows machine. For more detailed configuration options or deployment strategies, refer to the official documentation on our website.