Deploy Gitea with Marketplace Apps
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Gitea Marketplace App
Gitea is a community managed, painless, self-hosted Git service. Gitea is a complete solution for all aspects of your software development. At its core, Gitea serves as your centralized remote Git repository. Gitea also features built-in tools that represent every task in your development workflow, from planning to testing to releasing.
Self-hosting your software development with the Gitea Marketplace App offers total control of your codebase. At the same time, its familiar interface eases collaboration for you and your team. Gitea is one of the most popular self-hosted Git repository platforms, allowing you to benefit from a robust set of integrated tools and an active community.
Deploy a Gitea Marketplace App
Linode’s App Marketplace allows you to easily deploy software on a Linode using the Linode Cloud Manager. To access Linode’s App Marketplace:
Log in to your Linode Cloud Manager account.
From the Linode dashboard, click on the Marketplace button in the left-hand navigation menu.
The Linode creation page appears, with the Marketplace tab pre-selected.
Under the Select App section, select the app you would like to deploy:
Once you have selected the app, proceed to the app’s Options section and provide values for the required fields.
You can configure your Gitea App by providing values for the following fields:
|MySQL root Password||The root password for your MySQL database. Required.|
|Gitea Database Password||The password for your Gitea database user. Required.|
|The limited sudo user to be created for the Linode||The Linux username created for this Linode with sudo permissions.|
|The password for the limited sudo user||The password for your limited sudo user.|
|SSH Public Key||The public key for SSH access with your limited sudo user.|
|Enable passwordless sudo access for the limited user?||Select Yes to disable SSH password authentication for your limited sudo user as an additional security measure. Requires an SSH Public Key for SSH access to your Linode.|
|Disable root access over SSH?||Select Yes to disallow root logins over SSH as an additional security measure. Requires a configuration of a limited sudo user for SSH access to your Linode.|
|Configure automatic security updates?||Select Yes to enable automatic security updates for your Linode.|
|Use fail2ban to prevent automated instrusion attempts?||Select Yes to enable SSH login protection with Fail2Ban as an additional security measure.|
|Your Linode API Token||Your Linode |
|Subdomain||The subdomain you wish the installer to create a DNS record for during setup, for example |
|Domain||The domain name where you wish to host your Gitea server, for example |
|SOA Email for your domain||The email address to register as your Start of Authority (SOA). This field is required for creating DNS records for a new domain.|
|Do you need an MX record for this domain?||Select Yes to automatically configure an MX record for the purpose of sending emails from your Linode. Additional configuration with Gitea is required after installation to enable sending emails with this app.|
|Do you need an SPF record for this domain?||Select Yes to automatically configure an SPF record for the purpose of sending emails from your Linode. Additional configuration with Gitea is required after installation to enable sending emails with this app.|
|Would you like to use a free Let’s Encrypt SSL certificate for your fully qualified domain name?||Select Yes to configure an SSL Certificate for HTTPS access to your Gitea remote desktop. Requires a |
|Admin Email for Let’s Encrypt certificate||The email address to register with Certbot when generating an SSL certificate for your fully qualified domain name. This field is required for HTTPS access to your Gitea remote desktop.|
This guide may involve or result in sending email. In an effort to fight spam, Linode restricts outbound connections on ports 25, 465, and 587 on all Linodes for new accounts created after November 5th, 2019. For more information, please see Sending Email on Linode.This guide may involve or result in sending email. In an effort to fight spam, Linode restricts …
After providing the app specific options, provide configurations for your Linode server:
|Select an Image||Debian 10 is currently the only image supported by the Gitea Marketplace App, and it is pre-selected on the Linode creation page. Required.|
|Region||The region where you would like your Linode to reside. In general, it’s best to choose a location that’s closest to you. For more information on choosing a DC, review the How to Choose a Data Center guide. You can also generate MTR reports for a deeper look at the network routes between you and each of our data centers. Required.|
|Linode Plan||Your Linode’s hardware resources. We recommend that you use, at minimum, an 4GB Linode plan for your Gitea server. For more information on Gitea’s system requirements see their official documentation. If you decide that you need more or fewer hardware resources after you deploy your app, you can always resize your Linode to a different plan. Required.|
|Linode Label||The name for your Linode, which must be unique between all of the Linodes on your account. This name is how you identify your server in the Cloud Manager Dashboard. Required.|
|Root Password||The primary administrative password for your Linode instance. This password must be provided when you log in to your Linode via SSH. The password must meet the complexity strength validation requirements for a strong password. Your root password can be used to perform any action on your server, so make it long, complex, and unique. Required.|
When you’ve provided all required Linode Options, click on the Create button. Your Gitea App will complete installation anywhere between 3-7 minutes after your Linode has finished provisioning.
Getting Started after Deployment
Access your Gitea Site
After Gitea has finished installing, you can access your Gitea site using a web browser to complete setup and begin using your app.
Enter your Linode’s fully qualified domain name (for example,
https://www.example.com) or IPv4 address (for example,
http://192.0.2.0) into a browser window to access the Gitea welcome page. Select the Register link to reach the initial configuration screen.
Enter your Gitea Database Password in the Password field.
localhostwith your Linode’s fully qualified domain name or IPv4 address under SSH Server Domain and Gitea Base URL fields. Specify
httpsin the Gitea Base URL field if you configured an SSL certificate for your domain.
Complete any other desired configurations, then select Install Gitea to complete initial configuration.
You can now register a new administrative user and manage repositories with your Gitea App. For more configuration instructions and settings, refer to the official Gitea Documentation.
The Gitea Marketplace App installs the following software on your Linode:
|Gitea||Open source remote Git repository software. v1.13.0|
|MariaDB||Open source relational database fork of MySQL.|
|NGINX||Open source web server. Used as a reverse proxy by this app. See our guide on Getting Started with NGINX for more information.|
|UFW||Firewall utility. Ports 22/tcp, 80/tcp, and 443/tcp for IPv4 and IPv6 are enabled with installation of this app. Additional ports must be opened to send email from your Linode for use with this app. See our guide on How to Configure a Firewall with UFW for instructions.|
NoteCurrently, Linode does not manage software and systems updates for Marketplace Apps. It is up to the user to perform routine maintenance on software deployed in this fashion.
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
- [Gitea Documentation](https://docs.gitea.io/
This page was originally published on