-
Install
TeamCity.conf
andTeamCityAgent.conf
in /etc/init/ -
Create TeamCity in /etc/default/TeamCity
-
Make sure TEAMCITY_DATA_PATH and TEAMCITY_SERVER_PATH are owned by www-data
-
Start TeamCity
sudo service TeamCity start
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zend_extension="/usr/lib/php/extensions/no-debug-non-zts-20090626/xdebug.so" | |
[xdebug] | |
xdebug.idekey="macgdbp" | |
xdebug.remote_enable=1 | |
xdebug.remote_host="localhost" | |
xdebug.remote_port=9089 | |
xdebug.remote_handler="dbgp" |
Some text to describe it all here.
A simple list of regular applications and plugins.
URL: http://teamcity:8111/httpAuth/app/rest/projects/
Method: POST
Accept: application/xml
I hereby claim:
- I am devdetonator on github.
- I am devdetonator (https://keybase.io/devdetonator) on keybase.
- I have a public key ASCkKElgnpIX5iJo9eyN4IrUuE6_6V7-BJeoKF4zZ_IGpgo
To claim this, I am signing this object:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Check Your I/O Scheduler | |
If you are using SSDs, make sure your OS I/O scheduler is configured correctly. When you write data to disk, the I/O scheduler decides when that data is actually sent to the disk. The default under most *nix distributions is a scheduler called cfq (Completely Fair Queuing). | |
This scheduler allocates time slices to each process, and then optimizes the delivery of these various queues to the disk. It is optimized for spinning media: the nature of rotating platters means it is more efficient to write data to disk based on physical layout. | |
This is inefficient for SSD, however, since there are no spinning platters involved. Instead, deadline or noop should be used instead. The deadline scheduler optimizes based on how long writes have been pending, while noop is just a simple FIFO queue. | |
This simple change can have dramatic impacts. We’ve seen a 500-fold improvement to write throughput just by using the correct scheduler. | |
Link: https://www.elastic.co/guide/en/elasticsearch/guide/2.x/har |