Bearbeiten von „Diskussion:Server/GitLab“

== "Alternative" mit einfach nur Apache ==

http://www.bsdforen.de/threads/git-over-http-s-and-per-user-group-rights.28707/

== Alternative zu GitLab ==

; Gogs: Go Git Service - "A painless self-hosted Git service."

* https://gogs.io
* https://github.com/gogits/gogs

----

Gern kann wer eine Jail bekommen.

Der [https://www.codejam.info/2015/03/installing-gogs-on-freebsd.html Eintrag ''Installing Gogs on FreeBSD''] könnte ja eine Vorlage sein.

BTW: Erfolgreiches (oder bisherige Stände) könnten ja in einem Artikel [[Server/Gogs]] vermerkt verwerden. (Eigentlich sollte es dann auch einen Artikel [[Server/Git]] oder [[Server/Code]] geben. Ich warte mal ab. [[Server/GitLab]] steckt ja auch noch "in den Kinderschuhen".)

--[[Benutzer:PaulRiegel|Paul]] 10:27, 12. Mär. 2016 (CET)

; Kallithea:
* https://kallithea-scm.org/
* https://kallithea-scm.org/repos/kallithea

== testweise Installation ==

=== pre install ===

pkg update && pkg upgrade -y

=== install gitlab ===

pkg install -y gitlab
<pre>
</pre>
<pre>
Message from ruby-2.2.5,1:
====
Some of the standard commands are provided as separate ports for ease
of upgrading:

	devel/ruby-gems:	gem - RubyGems package manager
	devel/rubygem-rake:	rake - Ruby Make

And some of the standard libraries are provided as separate ports
since they require extra dependencies:

	databases/ruby-gdbm:	GDBM module

Install them as occasion demands.
====
</pre>
<pre>
Message from gcc-4.8.5_2:
To ensure binaries built with this toolchain find appropriate versions
of the necessary run-time libraries, you may want to link using

  -Wl,-rpath=/usr/local/lib/gcc48

For ports leveraging USE_GCC, USES=compiler, or USES=fortran this happens
transparently.
</pre>
<pre>
Message from node-6.1.0:
Note: If you need npm (Node Package Manager), please install www/npm.
</pre>
<pre>
Message from postgresql93-client-9.3.12:
The PostgreSQL port has a collection of "side orders":

postgresql-docs
  For all of the html documentation

p5-Pg
  A perl5 API for client access to PostgreSQL databases.

postgresql-tcltk 
  If you want tcl/tk client support.

postgresql-jdbc
  For Java JDBC support.

postgresql-odbc
  For client access from unix applications using ODBC as access
  method. Not needed to access unix PostgreSQL servers from Win32
  using ODBC. See below.

ruby-postgres, py-PyGreSQL
  For client access to PostgreSQL databases using the ruby & python
  languages.

postgresql-plperl, postgresql-pltcl & postgresql-plruby
  For using perl5, tcl & ruby as procedural languages.

postgresql-contrib
  Lots of contributed utilities, postgresql functions and
  datatypes. There you find pg_standby, pgcrypto and many other cool
  things.

etc...
</pre>
<pre>
Message from redis-3.0.7:
===>  CONFIGURATION NOTE:

      To setup "redis" you need to edit the configuration file:
      /usr/local/etc/redis.conf

      To run redis from startup, add redis_enable="YES"
      in your /etc/rc.conf.
</pre>
<pre>
Message from rubygem-sinatra-1.4.7:
**** NOTE ****

        Sinatra optionally integrates with haml/sass or Builder
        for templating and mongrel or thin as an HTTP server.
        To use them, install the respective ports separately:

                www/rubygem-haml
                devel/rubygem-builder
                www/rubygem-mongrel
                www/rubygem-thin
</pre>
<pre>
Message from gitlab-8.7.2:
Gitlab was installed successfully.

You now need to set up the various components of Gitlab, so please
follow the instructions in the guide at:

https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md

If you just installed an minor upgrade of GitLab please follow
the instructions in the guide at:

https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/update/freebsd_patch_versions.md

If you just installed an major upgrade of GitLab, for example you
switched from 8.6.x to 8.7.x, please follow the instructions in the guide at:

https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/update/8.6-to-8.7-freebsd.md
</pre>

sysrc gitlab_enable=YES

=== post install ===
Siehe auch:
* https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md
* http://docs.gitlab.com/ce/install/installation.html

==== PostgreSQL ====

===== PostgreSQL 9.5 =====

pkg install -y postgresql95-server postgresql95-contrib
<pre>
Message from postgresql95-client-9.5.2:
The PostgreSQL port has a collection of "side orders":

postgresql-docs
  For all of the html documentation

p5-Pg
  A perl5 API for client access to PostgreSQL databases.

postgresql-tcltk 
  If you want tcl/tk client support.

postgresql-jdbc
  For Java JDBC support.

postgresql-odbc
  For client access from unix applications using ODBC as access
  method. Not needed to access unix PostgreSQL servers from Win32
  using ODBC. See below.

ruby-postgres, py-PyGreSQL
  For client access to PostgreSQL databases using the ruby & python
  languages.

postgresql-plperl, postgresql-pltcl & postgresql-plruby
  For using perl5, tcl & ruby as procedural languages.

postgresql-contrib
  Lots of contributed utilities, postgresql functions and
  datatypes. There you find pg_standby, pgcrypto and many other cool
  things.

etc...
Message from postgresql95-server-9.5.2:
For procedural languages and postgresql functions, please note that
you might have to update them when updating the server.

If you have many tables and many clients running, consider raising
kern.maxfiles using sysctl(8), or reconfigure your kernel
appropriately.

The port is set up to use autovacuum for new databases, but you might
also want to vacuum and perhaps backup your database regularly. There
is a periodic script, /usr/local/etc/periodic/daily/502.pgsql, that
you may find useful. You can use it to backup and perfom vacuum on all
databases nightly. Per default, it perfoms `vacuum analyze'. See the
script for instructions. For autovacuum settings, please review
~pgsql/data/postgresql.conf.

If you plan to access your PostgreSQL server using ODBC, please
consider running the SQL script /usr/local/share/postgresql/odbc.sql
to get the functions required for ODBC compliance.

Please note that if you use the rc script,
/usr/local/etc/rc.d/postgresql, to initialize the database, unicode
(UTF-8) will be used to store character data by default.  Set
postgresql_initdb_flags or use login.conf settings described below to
alter this behaviour. See the start rc script for more info.

To set limits, environment stuff like locale and collation and other
things, you can set up a class in /etc/login.conf before initializing
the database. Add something similar to this to /etc/login.conf:
---
postgres:\
	:lang=en_US.UTF-8:\
	:setenv=LC_COLLATE=C:\
	:tc=default:
---
and run `cap_mkdb /etc/login.conf'.
Then add 'postgresql_class="postgres"' to /etc/rc.conf.

======================================================================

To initialize the database, run

  /usr/local/etc/rc.d/postgresql initdb

You can then start PostgreSQL by running:

  /usr/local/etc/rc.d/postgresql start

For postmaster settings, see ~pgsql/data/postgresql.conf

NB. FreeBSD's PostgreSQL port logs to syslog by default
    See ~pgsql/data/postgresql.conf for more info

======================================================================

To run PostgreSQL at startup, add
'postgresql_enable="YES"' to /etc/rc.conf
</pre>
<pre>
Message from postgresql95-contrib-9.5.2:
The PostgreSQL contrib utilities have been installed. Please see
/usr/local/share/doc/postgresql/contrib/README
for more information.
</pre>

===== PostgreSQL 9.3 =====
: … da wegen postgresql95-server der Bestandteil postgresql93-client deinstalliert wird, sollte vielleicht erstmal mit gesamtheitlich PostgreSQL 9.3 weitergemacht werden.

pkg install -y gitlab
<pre>
Installed packages to be REMOVED:
	postgresql95-server-9.5.2
	postgresql95-client-9.5.2
	postgresql95-contrib-9.5.2

New packages to be INSTALLED:
	gitlab: 8.7.2
	postgresql93-client: 9.3.12
	rubygem-pg: 0.18.4
</pre>