Skip to content
Permalink
Browse files

www/gitea: Update to 1.8.3 and merge changes from upstream port

  • Loading branch information
decke committed Jun 24, 2019
1 parent 985b029 commit aa83db111c6a18b501a2d737830037d2121176e8
Showing with 25 additions and 13 deletions.
  1. +5 −5 www/gitea/Makefile
  2. +3 −3 www/gitea/distinfo
  3. +12 −5 www/gitea/files/app.ini.sample.in
  4. +5 −0 www/gitea/pkg-message
@@ -1,9 +1,9 @@
# Created by: Stefan Bethke <stb@lassitu.de>
# $FreeBSD: head/www/gitea/Makefile 497010 2019-03-28 10:40:56Z rodrigo $
# $FreeBSD: head/www/gitea/Makefile 504853 2019-06-22 08:51:02Z kai $

PORTNAME= gitea
DISTVERSIONPREFIX= v
DISTVERSION= 1.8.2
DISTVERSION= 1.8.3
CATEGORIES= www

MAINTAINER= stb@lassitu.de
@@ -17,23 +17,23 @@ RUN_DEPENDS= git:devel/git
USES= go
USE_GITHUB= yes
GH_ACCOUNT= go-gitea
USE_RC_SUBR= gitea

GO_PKGNAME= code.gitea.io/${PORTNAME}
GO_TARGET= -tags "${GO_TAGS}"

USE_RC_SUBR= gitea
SUB_FILES+= app.ini.sample
SUB_LIST+= GITUSER=${USERS}

USERS= git
GROUPS= git

OPTIONS_DEFINE= CERT PAM SQLITE
OPTIONS_DEFAULT= ${OPTIONS_DEFINE}

CERT_DESC= Automatic creation of self-signed certificates
PAM_DESC= Authentication using PAM

OPTIONS_DEFAULT= ${OPTIONS_DEFINE}

CERT_VARS= GO_TAGS+=cert
PAM_VARS= GO_TAGS+=pam
SQLITE_VARS= GO_TAGS+="sqlite sqlite_unlock_notify"
@@ -1,3 +1,3 @@
TIMESTAMP = 1559291720
SHA256 (go-gitea-gitea-v1.8.2_GH0.tar.gz) = bb4a641776b0cbd50d2405e9efd785dec998c42f7267737dad401163ea16b61d
SIZE (go-gitea-gitea-v1.8.2_GH0.tar.gz) = 24321492
TIMESTAMP = 1561382340
SHA256 (go-gitea-gitea-v1.8.3_GH0.tar.gz) = 77ca5fe4468a94454c05c433eace1a7e282a588aeae268387d8651751f8d4e27
SIZE (go-gitea-gitea-v1.8.3_GH0.tar.gz) = 24320679
@@ -6,11 +6,16 @@
# contains the settings incorporated into the gitea binary.
#
# This sample configuration runs Gitea with a local database. Before
# running this configuration, make sure to change the SECRET_KEY and the
# INTERNAL_TOKEN at the end of this file. SECRET_KEY is a password of your
# choosing, INTERNAL_TOKEN is a 64-byte random number in BASE64 encoding.
# running this configuration, make sure to change the INTERNAL_TOKEN,
# JWT_SECRET, and SECRET_KEY variables. SECRET_KEY is a password of your
# choosing, INTERNAL_TOKEN is a 64-byte random number in BASE64 encoding,
# JWT_SECRET is a 32-byte random number in BASE64 encoding.
#
# Your can generate the token using for example:
# openssl rand -base64 64
# openssl rand -base64 64
#
# You can let Gitea add these to the config for you; you need to make
# app.ini writeable by the git user.
#
# There are no pre-configured users; the first user to register becomes an
# admin. In this sample configuration, the HTTP server only listens on
@@ -43,6 +48,9 @@ LEVEL = Info
[mailer]
ENABLED = false

[oauth2]
JWT_SECRET = D56bmu6xCtEKs9vKKgMKnsa4X9FDwo64HVyaS4fQ4mY

[picture]
AVATAR_UPLOAD_PATH = /var/db/gitea/data/avatars
DISABLE_GRAVATAR = false
@@ -83,4 +91,3 @@ ENABLE_NOTIFY_MAIL = false
DISABLE_REGISTRATION = false
ENABLE_CAPTCHA = true
REQUIRE_SIGNIN_VIEW = false

@@ -0,0 +1,5 @@
When upgrading to Gitea 1.8, Gitea requires the addition of another secret
to the config file in order to start up. Either manually add JWT_SECRET to
the ${PREFIX}/etc/gitea/conf/app.ini config file (see app.ini.sample), or
allow Gitea to make the change for you by making the config file writable to
the git user.

0 comments on commit aa83db1

Please sign in to comment.
You can’t perform that action at this time.