SPADS AutoHost

[nixtux]

OMG OMG thank you, you deserve some cookies for this

[FabriceFABS]

Excellent... Very nice job.
Merci beaucoup et encore merci pour le support.

Fabrice

[bibim]

You're welcome, don't hesitate to ask if you need help with the upgrade process and new version configuration.

[Jools]

Same here. Vielen Dank für das ausständige Arbeit!

[Forboding Angel]

Your upgrade instructions are hard to follow, especially for anyone running multiple spads instances.

I made them marginally easier to parse: https://pastebin.com/FQsu1sbx

[Forboding Angel]

PSA: Atm it is impossible to get the 32bit version of activeperl (Which is what I've always used) from the ActiveState site. I don't know if it will stay like that, but in case anyone is worried, strawberry seems to work 100% perfectly.

[bibim]

PSA: Atm it is impossible to get the 32bit version of activeperl (Which is what I've always used) from the ActiveState site. I don't know if it will stay like that, but in case anyone is worried, strawberry seems to work 100% perfectly.

Indeed, ActivePerl download page seems to be missing 32bit versions currently. They are still available from official ActiveState download site though (ActivePerl 5.24 Win32 x86, ActivePerl 5.26 Win32 x86). Thanks for the information.

Anyway, as you said SPADS should work as well with Strawberry Perl as with ActivePerl.

[bibim]

Here are two diagrams to help autohost administrators understand how SPADS settings and presets are organized in the 3 main configuration files: spads.conf, hostingPresets.conf and battlePresets.conf. It is important to understand these 3 files contain different settings, you can't move settings from spads.conf to battlePresets.conf for example.

SPADS settings and presets structure
SPADS presets dependencies

The presets structures are just examples of course, lots of things are possible...

[bibim]

Experimental support for TLS has been added in SPADS 0.12.6 (only in "unstable" release for now).
You can try it by adding "lobbyTls=on" as command line parameter when launching SPADS.

[Jools]

Do we need out our certificates? I know that Let's Encrypt provides that...

[bibim]

Not sure if this answers your question, but afaik currently only (self-signed) server side certificates are used in lobby protocol encryption, so you don't need your own certificates to run a SPADS instance.
SPADS does the same as SpringLobby: it validates the server certificate based on a trusted certificate fingerprint.

[bibim]

Starting with SPADS version 0.12.7 (only in unstable SPADS release for now), TLS is enabled by default for lobby server connection if it is supported by your Perl environment. You can still disable TLS for lobby server connection if you want by adding "lobbyTls=off" as command line parameter when you launch SPADS.

TLS support requires a specific Perl module named IO::Socket::SSL.

On Windows, this module is already included by default in your Perl environment so you shouldn't have anything to do to enable TLS.

On Linux, you may have to install this module manually, depending on your distribution. On main Linux distributions, the installation of this module can be performed through the standard package manager. For example for Debian based distributions (Ubuntu...):

Code: Select all

apt-get install libio-socket-ssl-perl

For RPM-based distributions (RedHat, CentOS...):

Code: Select all

yum install perl-IO-Socket-SSL

More generally, it is also possible to install this module without using the package manager, by using the Perl "cpan" tool:

Code: Select all

cpan IO::Socket::SSL