Gitea¶

Gitea. Key Features¶

• Repository management: Gitea allows you to create, clone, merge, and delete repositories. You can configure access to repositories for different users and groups.
• Code review: Gitea provides the ability to conduct code reviews, which helps to detect errors and improve code quality. You can comment on changes, propose fixes, and merge changes into the main branch.
• Issue tracking: A bug tracking system that allows you to create, track, and assign tasks. It helps the team effectively manage tasks and improve the development process.
• Integration with CI/CD: Gitea can be integrated with various continuous integration and deployment (CI/CD) systems. You can configure automatic build, testing, and deployment of your code with each update.
• User and access management: You can create users, assign them roles, and configure access to repositories and features.
• Integration with external services: Gitea can be integrated with various services such as Slack, Mattermost, SMTP servers, and others. It allows you to receive notifications about events in Gitea and interact with other development tools.
• Open-source: Gitea is an open-source software, allowing you to customize it according to various needs.
• Extensibility: Gitea provides an API for integration with other tools and systems.

Features of the assembly¶

• Installation on Debian 10. 11,12; Ubuntu 20.04, 22.04, 22.10, 23.04 is possible.
• Installation is performed using the package manager apt.
• After installation, the configuration file /etc/gitea/app.ini* is configured.
• JWT_SECRET (secret key used for signing and verifying JSON Web Tokens (JWT)) is generated and set to the corresponding variable.
• The self-signed certificates are generated and set to the variables CERT_FILE and KEY_FILE.
• The domain (DOMAIN) and URL (ROOT_URL) are specified in the variable {{domain_path}} (gitea<server_id>.hostkey.cloud).
• After installing and configuring Gitea and MySQL, the Gitea service is started, and an administrator account is created. The login is set to root, the password is taken from Invapi, and the client's email is specified from the server’s card.
• After installing and configuring Gitea and MySQL, the Gitea service is started, and an administrator account is created. The login is set to root, the password is taken from Invapi, and the client's email is specified from the server’s card.
• /etc/gitea/app.ini - the configuration file was taken from the Docker installation and adapted for the template.

Getting started after deploying Gitea¶

A notification will be sent to the e-mail specified during registration that the server is ready for work after paying for the order. It will contain the IP address of the VPS, as well as the login and password for the connection. Clients of our company manage the hardware in the server`s and API control panel — Invapi.

Here is the data for authorization:

• Link to access the Gitea dashboard with a web interface: in the webpanel tag;
• Login: root;
• Password: in a letter to your e-mail upon receipt of the server.

Ordering Gitea using the API¶

curl -s "https://invapi.hostkey.com/eq.php" -X POST \
--data "action=order_instance" \
--data "token=" \
--data "deploy_period=" \
--data "deploy_notify=" \
--data "email=" \
--data "pin=" \
--data "id=" \
--data "os_id=" \
--data "root_pass=" \
--data "hostname=" \
--data "ssh_key=" \
--data "post_install_callback=" \
--data "post_install_script=" \
--data "reinstall_key=" \
--data "os_name=" \
--data "imitate_deploy=" \
--data "imitate_error=0" \
--data "own_os=" \
--data "jenkins_task=" \
--data "traffic_plan=" \
--data "invoice_relid=" \
--data "preset=" \
--data "location_name=" \