Default Ports
These defaults can be changed either at install time, or afterwards by modifying the relevant config file and restarting the service.
| Incoming | Outgoing | Used for | Set in | |
|---|---|---|---|---|
| Server | 9000 | 9002 | Communication with agents | Continua.Server.Service.exe.config |
| Server | 80 | Web UI | IIS configuration | |
| Server* | 9010 | SSH/SFTP | Continua.Server.Service.exe.config | |
| Agent | 9002 | 9000 | Communication with server | Continua.Agent.Service.exe.config |
| Agent* | 9010 | SSH/SFTP with server | Continua.Agent.Service.exe.config |
*SSH access is optional, however agents must be able to access files on the server via either SSH or a UNC share. See below for more info.
Services
At install time, you specify which Windows user the Server and Agent services run as. We do not use Local System because many external tools (version control systems, build tools etc) expect to be run in a user context, and some require configuration that can only be performed by logging in as a user.
Shares and SSH
The Server must have a share (by default \\localhost\ContinuaShare) where the repository caches and build workspaces are stored. Agents can access this share either directly or via SSH.
To access the share directly, the user that the Agent service runs as must have read/write access to the share. Within a domain a share will perform significantly faster than SSH.
Continua also ships with an embedded SSH server for communication between the Server and Agent, which means that access to the share can be locked down. This is useful if you are working in a more secure network or if your agents are on the same domain as your sever.
The Agent does not require any externally accessible shares.
HTTPS
It is possible to enable HTTPS in IIS for use with Continua. Please see this IIS Config guide for more details: http://learn.iis.net/page.aspx/144/how-to-set-up-ssl-on-iis/#IISManager