Mostra la font per a Development Servers

[[Category:Infrastructura]]
[[Category:Devel]]
[[Category:tinki]]

[[Fitxer:devel-setup.png]]

= tinki-team-build =

Inside the container server, the stack should be located at <code>/srv/data/tinki-team-build</code> holding a <code>docker-compose.yml</code> manifest with the following services described below. To install and run the stack, execute <code>docker-compose up -d</code> from the project folder. In a similar fashion, use <code>docker-compose down</code> to halt the services. To backup the whole stack use the <code>backup-all.sh</code> script. To backup a particular service run the <code>backup.sh</code> script from its folder, if present.

* Docker registry, at <code>docker-reg.cadt.com</code>.
* Gitlab, at <code>git.cadt.com</code>.
* Jenkins, at <code>jenkins.cadt.com</code>.
* Jira, at <code>jira.cadt.com</code>.
* NPM, at <code>npm.cadt.com</code>.

== Docker Registry ==

The Docker Registry service exposes '''port 5000'''. This service is not backed up, as it holds and serves compiled Docker images from Gitlab via Jenkins.

== Gitlab ==

The Gitlab service exposes its web interface on '''port 8101''' and its SSH access through '''port 22'''. Backup is mainly done by a Rake task, as stated in the [https://docs.gitlab.com/ce/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system official guide]. The following folders are mapped to the host in order to backup configuration files and logs, according to the [https://docs.gitlab.com/ce/raketasks/backup_restore.html#storing-configuration-files same guide]. Restoration can be found in another section of the [https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore same document].

* <code>/var/opt/gitlab</code> to <code>/srv/data/gitlab/data</code>.
* <code>/etc/gitlab</code> to <code>/srv/data/gitlab/cfg</code>.
* <code>/var/log/gitlab</code> to <code>/srv/log/gitlab</code>.

== Jenkins ==

The Jenkins service exposes its web interface on '''port 8080'''. It is fairly simple to backup and the process is described in its [https://wiki.jenkins.io/display/JENKINS/Administering+Jenkins administration guide]. The following folders are mapped to the host in order to backup configuration files and logs.

* <code>/var/jenkins_home</code> to <code>/srv/data/jenkins</code>.
* <code>/var/jenkins_home/logs</code> to <code>/srv/log/jenkins</code>.

== Jira ==

The Jira service exposes its web interface on '''port 8102'''. According to the information present in their [https://confluence.atlassian.com/adminjiraserver/backing-up-data-938847673.html official guide], the current backup script will save the dump inside the host's <code>/srv/data/jira/db</code> folder. The following folders are mapped to the host in order to backup configuration files and logs.

* <code>/opt/jira</code> to <code>/srv/data/jira/data</code>.
* <code>/opt/jira/log</code> to <code>/srv/log/jira</code>.

== References ==

* Backing up and restoring GitLab. Creating a backup of the GitLab system [online]. Available at https://docs.gitlab.com/ce/raketasks/backup_restore.html#creating-a-backup-of-the-gitlab-system (Accessed 16 March 2018).
* Backing up and restoring GitLab. Storing configuration files [online]. Available at https://docs.gitlab.com/ce/raketasks/backup_restore.html#storing-configuration-files (Accessed 16 March 2018).
* Backing up and restoring GitLab. Restore [online]. Available at https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore (Accessed 16 March 2018).
* Jenkins Wiki. Administering Jenkins [online]. Available at https://wiki.jenkins.io/display/JENKINS/Administering+Jenkins (Accessed 16 March 2018).
* Atlassian Documentation. Backing up data [online]. Available at https://confluence.atlassian.com/adminjiraserver/backing-up-data-938847673.html (Accessed 16 March 2018).