Madanswer Technologies Interview Questions Data|Agile|DevOPs|Python - Recent questions and answers in Gitea

Answered: Why are Emoji displaying only as placeholders or in monochrome?

Thu, 13 Jan 2022 01:02:03 +0000

Gitea requires the system or browser to have one of the supported Emoji fonts installed, which are Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol, Noto Color Emoji and Twemoji Mozilla. Generally, the operating system should already provide one of these fonts, but especially on Linux, it may be necessary to install them manually.

Answered: Why Are Emoji Broken On MySQL in Gitea?

Thu, 13 Jan 2022 01:01:12 +0000

Unfortunately MySQL’s utf8 charset does not completely allow all possible UTF-8 characters, in particular Emoji. They created a new charset and collation called utf8mb4 that allows for emoji to be stored but tables which use the utf8 charset, and connections which use the utf8 charset will not use this.

Please run gitea convert, or run ALTER DATABASE database_name CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci; for the database_name and run ALTER TABLE table_name CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci; for each table in the database.

You will also need to change the app.ini database charset to CHARSET=utf8mb4.

Answered: How to Upgrade errors with MySQL in Gitea?

Thu, 13 Jan 2022 01:00:13 +0000

If you are receiving errors on upgrade of Gitea using MySQL that read:

ORM engine initialization failed: migrate: do migrate: Error: 1118: Row size too large...

Please run gitea convert or run ALTER TABLE table_name ROW_FORMAT=dynamic; for each table in the database.

The underlying problem is that the space allocated for indices by the default row format is too small. Gitea requires that the ROWFORMAT for its tables is DYNAMIC.

If you are receiving an error line containing Error 1071: Specified key was too long; max key length is 1000 bytes... then you are attempting to run Gitea on tables which use the ISAM engine. While this may have worked by chance in previous versions of Gitea, it has never been officially supported and you must use InnoDB. You should run ALTER TABLE table_name ENGINE=InnoDB; for each table in the database.
If you are using MySQL 5, another possible fix is

SET GLOBAL innodb_file_format=Barracuda;
SET GLOBAL innodb_file_per_table=1;
SET GLOBAL innodb_large_prefix=1;

Answered: Why is my markdown broken in Gitea?

Thu, 13 Jan 2022 00:59:03 +0000

In Gitea version 1.11 we moved to goldmark for markdown rendering, which is CommonMark compliant.
If you have markdown that worked as you expected prior to version 1.11 and after upgrading it’s not working anymore, please look through the CommonMark spec to see whether the problem is due to a bug or non-compliant syntax.
If it is the latter, usually there is a compliant alternative listed in the spec.

Answered: How can a user’s password be changed?

Thu, 13 Jan 2022 00:58:06 +0000

As an admin, you can change any user’s password (and optionally force them to change it on next login)…
- By navigating to your Site Administration -> User Accounts page and editing a user.
- By using the admin CLI commands.
  Keep in mind most commands will also need a global flag to point the CLI at the correct configuration.
As a user you can change it…
- In your account Settings -> Account page (this method requires you to know your current password).
- By using the Forgot Password link.
  If the Forgot Password/Account Recovery page is disabled, please contact your administrator to configure a mail service.

Answered: How can we enable password reset in Gitea?

Thu, 13 Jan 2022 00:57:15 +0000

There is no setting for password resets. It is enabled when a mail service is configured, and disabled otherwise.

Answered: How can I create users before starting Gitea?

Thu, 13 Jan 2022 00:56:12 +0000

Gitea provides a sub-command gitea migrate to initialize the database, after which you can use the admin CLI commands to add users like normal.

Answered: What is LFS Issues in Gitea?

Thu, 13 Jan 2022 00:55:25 +0000

For issues concerning LFS data upload

batch response: Authentication required: Authorization error: <GITEA_LFS_URL>/info/lfs/objects/batch
Check that you have proper access to the repository
error: failed to push some refs to '<GIT_REPO_URL>'

Check the value of LFS_HTTP_AUTH_EXPIRY in your app.ini file.
By default, your LFS token will expire after 20 minutes. If you have a slow connection or a large file (or both), it may not finish uploading within the time limit.

You may want to set this value to 60m or 120m.

Answered: How to fix Missing releases after migrating repository with tags

Thu, 13 Jan 2022 00:53:54 +0000

To migrate an repository with all tags, you need to do two things:

Push tags to the repository:

 git push --tags

(Re-)sync tags of all repositories within Gitea:

gitea admin repo-sync-releases

Answered: What are SSH Common Errors in Gitea?

Thu, 13 Jan 2022 00:52:23 +0000

Permission denied (publickey).
fatal: Could not read from remote repository.

This error signifies that the server rejected a log in attempt, check the following things:

On the client:
- Ensure the public and private ssh keys are added to the correct Gitea user.
- Make sure there are no issues in the remote url. In particular, ensure the name of the Git user (before the @) is spelled correctly.
- Ensure public and private ssh keys are correct on client machine.
On the server:
- Make sure the repository exists and is correctly named.
- Check the permissions of the .ssh directory in the system user’s home directory.
- Verify that the correct public keys are added to .ssh/authorized_keys.
  Try to run Rewrite '.ssh/authorized_keys' file (for Gitea SSH keys) on the Gitea admin panel.
- Read Gitea logs.
- Read /var/log/auth (or similar).
- Check permissions of repositories.

The following is an example of a missing public SSH key where authentication succeeded, but some other setting is preventing SSH from reaching the correct repository.

fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

In this case, look into the following settings:

On the server:
- Make sure that the git system user has a usable shell set
  - Verify this with getent passwd git | cut -d: -f7
  - usermod or chsh can be used to modify this.
- Ensure that the gitea serv command in .ssh/authorized_keys uses the correct configuration file.

Answered: How to fix Hooks aren’t running for Gitea?

Thu, 13 Jan 2022 00:49:30 +0000

If Gitea is not running hooks, a common cause is incorrect setup of SSH keys.
You can also try logging into the administration panel and running the Resynchronize pre-receive, update and post-receive hooks of all repositories. option.

Answered: Translation is incorrect/how to add more translations?

Thu, 13 Jan 2022 00:48:14 +0000

Our translations are currently crowd-sourced on our Crowdin project
Whether you want to change a translation or add a new one, it will need to be there as all translations are overwritten in our CI via the Crowdin integration.

Answered: How to fix Gitea is running slow ?

Wed, 12 Jan 2022 05:33:20 +0000

The most common culprit for this is loading federated avatars.
This can be turned off by setting ENABLE_FEDERATED_AVATAR to false in your app.ini
Another option that may need to be changed is setting DISABLE_GRAVATAR to true in your app.ini

Answered: What is difference between SSHD vs built-in SSH?

Wed, 12 Jan 2022 05:30:28 +0000

SSHD is the built-in SSH server on most Unix systems.
Gitea also provides its own SSH server, for usage when SSHD is not available.

Answered: How to add/use custom themes in Gitea?

Wed, 12 Jan 2022 05:28:56 +0000

Gitea supports three official themes right now, gitea (light), arc-green (dark), and auto (automatically switches between the previous two depending on operating system settings). To add your own theme, currently the only way is to provide a complete theme (not just color overrides)

As an example, let’s say our theme is arc-blue (this is a real theme, and can be found in this issue)
Name the .css file theme-arc-blue.css and add it to your custom folder in custom/public/css
Allow users to use it by adding arc-blue to the list of THEMES in your app.ini

Answered: How to Adjusting your server for public/private use in Gitea?

Wed, 12 Jan 2022 05:26:46 +0000

Adjusting your server for public/private use

Preventing spammers

There are multiple things you can combine to prevent spammers.

By whitelisting or blocklisting certain email domains
By only whitelisting certain domains with OpenID (see below)
Setting ENABLE_CAPTCHA to true in your app.ini and properly configuring RECAPTCHA_SECRET and RECAPTCHA_SITEKEY
Settings DISABLE_REGISTRATION to true and creating new users via the CLI, API, or Gitea’s Admin UI

Only allow/block certain email domains

You can configure EMAIL_DOMAIN_WHITELIST or EMAIL_DOMAIN_BLOCKLIST in your app.ini under [service]

Only allow/block certain OpenID providers

You can configure WHITELISTED_URIS or BLACKLISTED_URIS under [openid] in your app.ini
NOTE: whitelisted takes precedence, so if it is non-blank then blacklisted is ignored

Issue only users

The current way to achieve this is to create/modify a user with a max repo creation limit of 0.

Restricted users

Restricted users are limited to a subset of the content based on their organization/team memberships and collaborations, ignoring the public flag on organizations/repos etc.__

Example use case: A company runs a Gitea instance that requires login. Most repos are public (accessible/browsable by all co-workers).

At some point, a customer or third party needs access to a specific repo and only that repo. Making such a customer account restricted and granting any needed access using team membership(s) and/or collaboration(s) is a simple way to achieve that without the need to make everything private.

Enable Fail2ban

Use Fail2Ban to monitor and stop automated login attempts or other malicious behavior based on log patterns

Answered: What is Swagger?

Wed, 12 Jan 2022 05:25:07 +0000

Swagger is what Gitea uses for its API.
All Gitea instances have the built-in API, though it can be disabled by setting ENABLE_SWAGGER to false in the api section of your app.ini

Answered: What is difference between Active user vs login prohibited user ?

Wed, 12 Jan 2022 05:24:08 +0000

In Gitea, an “active” user refers to a user that has activated their account via email.
A “login prohibited” user is a user that is not allowed to log in to Gitea anymore

Answered: How to reslove Custom Templates not loading or working incorrectly or Gitea?

Wed, 12 Jan 2022 05:21:37 +0000

Gitea’s custom templates must be added to the correct location or Gitea will not find and use them.
The correct path for the template(s) will be relative to the CustomPath

To find CustomPath, look for Custom File Root Path in Site Administration -> Configuration

If that doesn’t exist, you can try echo $GITEA_CUSTOM

If you are still unable to find a path, the default can be calculated above
Once you have figured out the correct custom path, you can refer to the customizing Gitea page to add your template to the correct location.

Answered: What is mean by File upload fails with: 413 Request Entity Too Large?

Wed, 12 Jan 2022 05:15:01 +0000

This error occurs when the reverse proxy limits the file upload size.

Answered: What is mean by Not seeing a clone URL or the clone URL being incorrect in Gitea?

Wed, 12 Jan 2022 05:12:24 +0000

There are a few places that could make this show incorrectly.

If using a reverse proxy, make sure you have followed the correction directions in the reverse proxy guide
Make sure you have correctly set ROOT_URL in the server section of your app.ini

If certain clone options aren’t showing up (HTTP/S or SSH), the following options can be checked in your app.ini

DISABLE_HTTP_GIT: if set to true, there will be no HTTP/HTTPS link
DISABLE_SSH: if set to true, there will be no SSH link
SSH_EXPOSE_ANONYMOUS: if set to false, SSH links will be hidden for anonymous users

Answered: Where does Gitea store files?

Wed, 12 Jan 2022 05:09:23 +0000

WorkPath
- Environment variable GITEA_WORK_DIR
- Else binary location
AppDataPath (default for database, indexers, etc.)
- APP_DATA_PATH from app.ini
- Else %(WorkPath)/data
CustomPath (custom templates)
- Environment variable GITEA_CUSTOM
- Else %(WorkPath)/custom
HomeDir
- Unix: Environment variable HOME
- Windows: Environment variable USERPROFILE, else environment variables HOMEDRIVE+HOMEPATH
RepoRootPath
- ROOT in app.ini
- Else %(AppDataPath)/gitea-repositories
INI (config file)
- -c flag
- Else %(CustomPath)/conf/app.ini
SQLite Database
- PATH in database section of app.ini
- Else %(AppDataPath)/gitea.db

Answered: How to migrate from Gogs/GitHub/etc. to Gitea?

Wed, 12 Jan 2022 05:08:11 +0000

To migrate from Gogs to Gitea:

To migrate from GitHub to Gitea, you can use Gitea’s built-in migration form.
In order to migrate items such as issues, pull requests, etc. you will need to input at least your username.
Example (requires login)

To migrate from GitLab to Gitea, you can use this non-affiliated tool:
https://github.com/loganinak/MigrateGitlabToGogs