Difference between revisions of "Gitea"

From Steak Wiki
Jump to navigationJump to search
(Created page with "Gitea is a self hosted git option, akin to gitlab. Gitea aims to be the simplest to deploy, and has good documentation. ==General== ==Customizations== ===Home page=== Find y...")
 
 
(One intermediate revision by the same user not shown)
Line 69: Line 69:
  
 
==Troubleshooting==
 
==Troubleshooting==
===error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413 Request Entity Too Large
+
===RPC failed 413 Request Entity Too Large The remote end hung up unexpectedly===
fatal: The remote end hung up unexpectedly===
 
 
I have a reverse proxy and I had to edit the following for this server config:
 
I have a reverse proxy and I had to edit the following for this server config:
 
   
 
   
 
Reference: https://stackoverflow.com/questions/7489813/github-push-error-rpc-failed-result-22-http-code-413   
 
Reference: https://stackoverflow.com/questions/7489813/github-push-error-rpc-failed-result-22-http-code-413   
 
  client_max_body_size 100m;
 
  client_max_body_size 100m;

Latest revision as of 01:27, 8 November 2019

Gitea is a self hosted git option, akin to gitlab. Gitea aims to be the simplest to deploy, and has good documentation.

General

Customizations

Home page

Find your custom path in gitea. This will be output if you run gitea --help. Create a directory named templates in this custom path, and then copy the home.tmpl file from the source repo of gitea (may need to copy for your specific distribution). Note that these steps are from https://docs.gitea.io/en-us/customizing-gitea/ I did the following.

mkdir /data/gitea/templates
cd /data/gitea/templates
wget <home.tmpl>
nano ./home.tmpl

The default home.tmpl uses some template macros but you can delete most of it and end up with something simple like this:

{{template "base/head" .}}
<div class="home">
        <div class="ui stackable middle very relaxed page grid">
                <div class="sixteen wide center aligned centered column">
                        <div>
                                <img class="logo" src="https://steakelectronics.com/logo3.jpg" />
                        </div>
                        <div class="hero">
                                <h2 class="ui icon header title">
                                        Steak Electronics Git Repository
                                </h2>
                                <h3>Electronics and IT Services</h3>
                        </div>
                </div>
        </div>
        <div class="ui stackable middle very relaxed page grid">
                <div class="eight wide center column">
                        <h1 class="hero ui icon header">
                        </h1>

                        <p class="large">

                        </p>
                </div>
                <div class="eight wide center column">
                        <h1 class="hero ui icon header">
                        </h1>

                        <p class="large">
                        </p>
                </div>
        </div>
        <div class="ui stackable middle very relaxed page grid">
                <div class="eight wide center column">
                        <h1 class="hero ui icon header">
                        </h1>
                        <p class="large">
                        </p>
                </div>
                <div class="eight wide center column">
                        <h1 class="hero ui icon header">
                        </h1>
                        <p class="large">
                        </p>
                </div>
        </div>
</div>
{{template "base/footer" .}}

Without the macros, you have a 2x2 grid you can put something in, and you have the logo which you can customize.

Troubleshooting

RPC failed 413 Request Entity Too Large The remote end hung up unexpectedly

I have a reverse proxy and I had to edit the following for this server config:

Reference: https://stackoverflow.com/questions/7489813/github-push-error-rpc-failed-result-22-http-code-413

client_max_body_size 100m;