Adding TeamCity Stack to the Rancher (#254)

* Adding support for database auto creation

* Creation v0.8.44 for auto-database-creation

* Update config.yml

* Fixing syntax

* Fixing syntax

* Update

* Fixing uuid for gogs-1

* Create README.md

* Delete README.md

* Create README.md

* Add files via upload

* Create docker-compose.yml

* Create rancher-compose.yml

* Create config.yml

* Update docker-compose.yml

* Update README.md

* Initial TeamCity commit

* Addin variable for postgress_container

* Addin variable for postgress_container

* Setting Internal Docker port for Agents

* Fix for Rancher autoselect

* Syntax correction

* Adding details to the Readme

* Update rancher-compose.yml

* Fixing vocabulary

* Adding support for autoscale

* Adding support for autoscale

* Adding support for autoscale

* Adding Sidekicks

Enabling Sidekicks for teamcity-server and postgress services with shared working wolumes. This will help with easy upgrades of both containers.

* Added info about Sidekicks.

* fix

* Reverting newer version of goog

* Adding back missing category

templates/teamcity/README.md

@@ -0,0 +1,14 @@
+## What is inside TeamCity Stack?
+* TeamCity Server
+* Postgres Database
+* Scalable TeamCity Agents
+
+## Info
+* In default TeamCity stack will create "teamcity" postgres database with teamcity user.  
+* Additional variables `http_proxy` and `https_proxy` are included, which can be helpfull in some cases.
+* Once TeamCity will start, make sure you setup correct information in setup page.
+* For easy upgrades there are sidekicks for both postgress and teamcity-server with dedicated storage.
+
+## TeamCity Agents
+TeamCity Agents will start automatically and connect to the TeamCity Server.  
+Agents should be available in TeamCity Server in about 5 minutes after stack's start.