Gitea - Revision history

Admin: /* Adding Static Content */

2018-04-23T20:14:31Z

Adding Static Content

← Older revision		Revision as of 20:14, 23 April 2018
Line 688:		Line 688:
	</pre>		</pre>

	=~~Adding Static Content~~=		=Using the API=

	~~This doesn't seem to work... https:~~/~~/github.com/go-gitea/gitea/pull/782~~		See [[Gitea/API]]

	=References=		=References=

2018-02-17T09:30:26Z

From Source

← Older revision		Revision as of 09:30, 17 February 2018
Line 325:		Line 325:
	* configure gitea: https://docs.gitea.io/en-us/config-cheat-sheet/		* configure gitea: https://docs.gitea.io/en-us/config-cheat-sheet/

	===~~First (Failed) Attempt~~===		===Errors With Build===

	[[~~Gitea/First Failed Attempt~~]]		If you see the error below, the problem is your version of Git:

			<pre>
			$ TAGS="bindata sqlite" make build
			go build -i -v -tags 'bindata sqlite' -ldflags '-s -w -X "main.Version=1.2.3+1-g6629ecf" -X "main.Tags=bindata sqlite"' -o gitea
			vendor/code.gitea.io/git/command.go:9:2: cannot find package "context" in any of:
			/home/charles/gocode/src/code.gitea.io/gitea/vendor/context (vendor tree)
			/usr/lib/go-1.6/src/context (from $GOROOT)
			/home/charles/gocode/src/context (from $GOPATH)
			Makefile:205: recipe for target 'gitea' failed
			make: *** [gitea] Error 1
			</pre>

			See [[Goenv]] for setting up a way of controlling your Go version, and use a veriosn of Go > 1.7.

	==Gitea with HTTPS==		==Gitea with HTTPS==

2018-02-15T08:06:13Z

Post Install Procedure

2018-02-15T08:02:12Z

From Source

@@ Line 282: / Line 282: @@
 </pre>
 }}
 Once this is complete, you will hae a standalone binary "gitea" that can be copied into your binary directory of choice for gitea.
 Links:

2018-02-15T07:58:57Z

From Source

← Older revision		Revision as of 07:58, 15 February 2018
Line 282:		Line 282:
	</pre>		</pre>
	}}		}}

			Once this is complete, you will hae a standalone binary "gitea" that can be copied into your binary directory of choice for gitea.

	Links:		Links:

2018-02-15T07:47:20Z

From Source

← Older revision		Revision as of 07:47, 15 February 2018
Line 55:		Line 55:

	<pre>		<pre>
	git checkout release/v1.0		git checkout release/v1.2
	</pre>		</pre>

Line 63:		Line 63:
	TAGS="bindata sqlite" make generate build		TAGS="bindata sqlite" make generate build
	</pre>		</pre>

			If building v1.2 or later, you'll need Go version 1.7 or later. See [[Goenv]] for a way to install particular go versions.

	===Successful Build===		===Successful Build===

2018-01-30T01:24:42Z

2017-10-22T17:28:44Z

Users and Permissions

← Older revision		Revision as of 17:28, 22 October 2017
Line 371:		Line 371:
	* to run gitea, I start up [[Screen]] and run the command <code>sudo su git</code> to get a shell as the user git. I then start up the gitea binary.		* to run gitea, I start up [[Screen]] and run the command <code>sudo su git</code> to get a shell as the user git. I then start up the gitea binary.

	NOTE: You may need to set the home directory for the git user when running the sudo command, like this: <code>sudo su -H /~~home~~/~~git git~~</code>. Otherwise, gitea may complain about not being able to access or modify the git configuration files in the home directory of the non-git user (you).		NOTE: You may need to set the home directory for the git user when running the sudo command, like this: <code>$ sudo -H -u git /www/gitea/bin/gitea web</code>. Otherwise, gitea may complain about not being able to access or modify the git configuration files in the home directory of the non-git user (you).

	Here's what that requires:		Here's what that requires:

2017-10-22T17:23:12Z

Users and Permissions

← Older revision		Revision as of 17:23, 22 October 2017
Line 370:		Line 370:
	* the public and private keys were made group-readable and owned by the ssl-certs group		* the public and private keys were made group-readable and owned by the ssl-certs group
	* to run gitea, I start up [[Screen]] and run the command <code>sudo su git</code> to get a shell as the user git. I then start up the gitea binary.		* to run gitea, I start up [[Screen]] and run the command <code>sudo su git</code> to get a shell as the user git. I then start up the gitea binary.

			NOTE: You may need to set the home directory for the git user when running the sudo command, like this: <code>sudo su -H /home/git git</code>. Otherwise, gitea may complain about not being able to access or modify the git configuration files in the home directory of the non-git user (you).

	Here's what that requires:		Here's what that requires:

2017-08-04T05:53:19Z

Successful Build

← Older revision		Revision as of 05:53, 4 August 2017
Line 92:		Line 92:
	Then make build:		Then make build:

			{{Scrollbox\|
	<pre>		<pre>
	$ TAGS="bindata" make build		$ TAGS="bindata" make build
Line 278:		Line 279:
	code.gitea.io/gitea		code.gitea.io/gitea
	</pre>		</pre>
			}}

			Links:
			* Customize gitea: https://docs.gitea.io/en-us/customizing-gitea/
			* configure gitea: https://docs.gitea.io/en-us/config-cheat-sheet/

	===First (Failed) Attempt===		===First (Failed) Attempt===