tgstation-server-v4.3.2

Please refer to the README for setup instructions.

Component Versions

Core: 4.3.2
HTTP API: 6.6.0
DreamMaker API: 5.2.2
Web Control Panel: 0.4.0
Host Watchdog: 1.1.0

The recommended client is currently the legacy Tgstation.Server.ControlPanel. This will be phased out as the web client is completed.

Patch 2

Core

• Postgres support has been enabled. (#1030)
• Fixed a database constraint issue when dropping instances. (#1030)
• Fixed a typo in the standard message for API ErrorCode 52. (#1030)
• Configuration field Database:MySqlServerVersion renamed to Database:ServerVersion. Now also supports Postgres. (#1030)
• Fixed configuration option General:RestartTimeout not being respected. (#1030)
• Added scripts for all events. (#1034)
• Added Windows DreamDaemon output logging to Windows. (#1042)
• Fixed a NullReferenceException when deploying with no repository present. (#1040)
• Attempting to restart a stopped watchdog will now result in API error code 80 from the job. (#1036)
• Fixed a basic/Windows watchdog startup failure when reattaching to a set of servers launched with the experimental watchdog. (#1036)
• Fixed log files containing the string {Date}. (#1045)
• Fixed detection of services running on requested DreamDaemon port. (#1045)
• Fixed the DMAPI not being notified of instance renaming. (#1045)
• Fixed being unable to repeatedly change the auto update interval. (#1045)
• Heavily enriched log message context. (#1045)

Patch 1

Core

• You can now change the watchdog heartbeat interval and startup timeout without triggering a soft restart. (#1031)
• Fixed a watchdog crash loop that could potentially occur during the commit phase of deployment. (#1031)
• Changing the auto-update interval will no longer cancel pull/deploy jobs that are in progress. (#1031)
• Fixed an auto update failure that could occur if auto updates began with the latest origin commit and test merges active. (#1031)
• Fixed a crash that could occur as a result of a race condition when the watchdog reattaches. (#1031)
• Fixed a watchdog crash lop that could potentially occur when updating DreamDaemon settings. (#1031)
• Fixed a Windows watchdog crash that would occur after the first deployment after a reattach. (#1031)
• Fixed the watchdog detach event not being sent to the DMAPI. (#1031)

HTTP API

• Patch version bump to facilitate implementation changes. (#1031)

Update 3.X

Core

• The default config value for General:RestartTimeout has been changed from 5s to 60s. It is recommended server operators make this change as well since if it is hit, running DreamDaemon processes may become orphaned during reboot/update operations and must be killed manually before being launched again with TGS. (#1021)
• Added failed query retrying to the MSSQL database backend. (#1021)
• Deployment messages with Discord bots are now delivered via an updating rich embed. (#1019)
• HTTP/2 has been enabled in addition to HTTP/1 for the web server. (#1022)
• The API port has a new configuration location. Please migrate from the legacy Kestrel configuration section to the new General:ApiPort option. (#1022)
• This release includes the framework for supporting PostgresSql as a DB backend. It is currently disabled due to an upstream bug that will be fixed in a few days (npgsql/efcore.pg#1392). (#1029)

HTTP API

• Removed recursion from some API model definitions. (#1026)

Update 2.X

• Added DreamDaemon heartbeats and automatic restarts (Along with associated right). The watchdog will automatically restart if 4 heartbeats are missed. (#975)
• Minor DMAPI update to properly support heartbeats though it is not mandatory. (#975)
• Fixed being unable to suspend and resume processes on POSIX systems. (#975)
• Fixed a crash that could occur if the server was shutdown with watchdogs running waiting on topic requests to complete. (#975)
• Minor C# client patch for moving some API properties across their inheritance tree. (#975)
• Fixed consistency issues surrounding graceful watchdog actions. (#975)
• Attempting to download invalid BYOND versions will no longer create empty directories for them. (#975)
• Fixed being able to make API requests before initial instance startup had completed. (#975)
• Fixed a rare NullReferenceException when launching DreamDaemon. (#977)
• Enabled connection resiliency for MySQL connections. This was causing heavy instability across the server. (#977)
• Fixed a potential issue where chat bots could report the watchdog was starting instead of restarting. (#977)
• Fixed deployment messages showing an extra .0 after the BYOND version. (#977)

RTM Update 1.X

• Most failed requests now come with an error code defined in the API spec. (#920)
• We now independently version several internal components such as the REST and DM APIs. (#920)
• A hard limit of 1000 UTF-8 characters have been added to most strings in models. (#920)
• Improved server-side validation of many models. (#920)
• It's no longer possible to set rights enums to invalidly high values. (#920)
• It's no longer possible to create multiple users with the same system identifier. (#920)
• Fixed chat bot names conflicting with those in separate instances. (#920)
• Added configurable limits for the maximum number of users and instances in the server. (#920)
• The dotnet framework used has been upgraded to .NET Core 3.1. (#927)
• SQLite support has been added, though a full relational database is still the recommended option. (#927)
• Added a startup error if the server detects it cannot create symbolic links (#929)
• Added a startup error if the server detects it cannot create or load git repositories (#929)
• Added configurable limits for the number of chat bots in an instance and the number of channels in a chat bot. There are new permissions for these API fields. (#930)
• Fixed an issue where custom commands could become "de-synced". (#935)
• TGS now uses DMAPI v5.0.0. It has been rewritten to communicate via exclusively via HTTP, /world/Topic(), and world.params. Because of this, the ultrasafe security level is now supported. (#935)
• Reattaching now remembers the launch security level. (#935)
• Fixed the workarounds for trusted mode .dmbs that regressed. (#935)
• CompileJob models now have the received DMAPI version in their dataset. (#935)
• If an instance is renamed, this updated will be reflected in the DMAPI. (#935)
• Added some logging to the script used when starting docker containers. (#936)
• The ServerInformation schema object now includes the minimum password length, instance, and user limits. (#940)
• All version strings returned from the API are now in semantic versioning format. Returned versions in the BYOND model will have their patch number set to zero. (#940)
• You can no longer downgrade to server versions below v4.1.0. (#940)
• Failed job may now include error codes. (#942)
• Fixed not being able to checkout remote branches other than the initially cloned branch. (#943)
• Fixed an issue where checking out a specific SHA in the repository would be a no-op. (#943)
• You can now limit where instances may be installed in the configuration. (#945)
• Detaching an instance will no longer fail due to database integrity issues. (#946)
• Added support for joining IRC channels with keys. (#950)
• Automatic .dme detection is now recursive within a repository. (#956)
• Fixed changing the reboot mode with the basic watchdog preventing staged compile jobs from being applied. (#956)
• On POSIX, BYOND cache cleanup will now target the correct directory. (#956)
• Retrieving compile job details after its job completes will now no longer possibly return out of date data. (#956)
• Fixed issues with receiving BYOND topic responses. (#956)
• Console logging is now asynchronous. This is good for performance. (#956)
• Reduced memory requirements while sending BYOND topics. (#956)

Initial Release

Whats New:

• Agnostic HTTP API: The replaces the WCF service calls used in TGS3. This helps avoid Windows vendor lock-in and get away from the SOAP API that literally no one understood (not even me). With it, it's much easier to expose TGS to the internet, all you need is a HTTPS reverse proxy in front of it. A rundown of the new API exists here: https://tgstation.github.io/tgstation-server/api.html.
• Granular Access Controls: Windows users are no longer (required to be) the basis for authentication to the server. We now have database-backed users as a login option. These use a combined Basic/JWT authentication scheme with industry standard password hashing and salting. Users are fully customizable and can be given granular access to every bit of the server via the new permissions system. From changing the BYOND version, to test merging a PR, to restarting the server, every action may now be granted or revoked on a per user basis.
  • Limitation: Users can be disabled but not deleted.
• Proper Long Running Operation Support: Server actions take a long time, from a git pull to a DreamMaker compile. TGS now internally allows for them to be run in parallel with each other and provides an audit record via the database. This is an improvement over the old system where connections had to be held open for the duration of operations.
• Database Backend: TGS requires an SQL database to operate. This allows for much better concurrency and is just overall much cleaner than the old single json file storage blob per instance.
  • Limitation: There is a one-to-one relationship with a TGS server and a database. DO NOT SHARE TGS DATABASES.
• Linux/Docker Support: TGS4 is Linux and docker compatible. (Note this does not mean that rust-g and BSQL work out of the box, they must be compiled using event scripts like PreCompile.sh).
  • Limitation: TGS4 has a dependency on the native library libgit2 which is known to cause issues on Linux. The binaries distributed with TGS are kept up to date with the upstream repository, but out of the box Linux support can't be assured in every environment. Docker is guaranteed to always work, however. See the repository for the distributed binary here: https://github.com/libgit2/libgit2sharp.nativebinaries.
  • Limitation: System based logins are not supported on Linux. #709
• Incredibly Detailed Logging: Various log levels exist now (Trace/Debug/Info/Warning/Error/Critical) and are sanely output to a rolling file on the host. Significant improvement over having to use the Windows event viewer with TGS3. Until such a point where bugs stop copping up I'd recommend Trace logging for the main log level.
• Historical Deployment Data: Every time code is compiled the following data is logged and stored.
  • The User that initiated it.
  • When it was started.
  • When it finished.
  • All revision information including local/remote SHAs, test merged pull requests and their SHAs.
  • The BYOND version used.
  • The DMAPI version in the binary
• Multiple chat bots per instance: Up to 65535 as a matter of fact (who knows why I chose that number?)!
• Automatic Chat Bot Reconnection Intervals: Set in minutes.
• Better Error State Handling: The Server and Watchdog aren't your momma's boys anymore. Every error state will be automatically resolved or reported with recommended actions.
• Watchdog Heartbeats: An interval in seconds can now be set at which TGS will send /world/Topic() packets to DreamDaemon. If four of these are missed, the server will be rebooted. No more endless @key Holder pings in discord (and I can finally unmute the /tg/ guild)! This feature can be disabled.
• Better DMAPI: No longer requires injecting a .NET runtime .dll into the DreamDaemon process. DD -> TGS communication is now handled securely via BYOND's native /world/Export() API ("But Cyberboss, BYOND only supports GET requests." Who said anything about respecting HTTP standards when dealing with BYOND?).
• Safe/Ultrasafe Security Support: Thanks to the new DMAPI, the ultrasafe and safe security levels may be used without running into BYOND's limitations. But no one really cares...
• Self Upgrading: To upgrade TGS3 you needed to download and run the installer. This was pretty seamless, but it's now even better in V4 as the command to upgrade can be given straight to the API. At that point the server will handle downloading the update, detaching running DreamDaemon instances, restarting with the new version, and reattaching to them. Easier than ever patch delivery.
• Gasp TESTING: TGS4 currently has over 60% code coverage in automated unit and full stack integration tests. I aim to have that number ever increasing to prevent trivial mistakes. Big improvement over V3 which had... literally none...

Along with these features, nearly every single V3 feature has been included and possibly improved in some fashion. This includes stuff like Windows accounts for logins, and using ACLs for static file handling. The following exceptions exist but are planned for future updates:

• Process memory/CPU diagnostic data is not generated: #611
• Process dumps may not be created: #612
• The DMAPI is required in DreamMaker code: #934
• The option to "Initialize Game Directories" is no longer present, but a variant is still performed every deployment for smoother error handling.
• Direct server announcements are no longer present but may be readded upon request.

Note that V3 instances cannot be imported into TGS4. This doesn't prevent the transfer of static game files however.

TGS4 is set to be the final major version. There will be no TGS5, not from me.