Server Setup - Revision history

Cheese at 07:56, 29 May 2011

2011-05-29T07:56:56Z

← Older revision		Revision as of 07:56, 29 May 2011
Line 1:		Line 1:
	This page will guide you through the process of configuring an [[ASSS]] server. This page is a continuance of [[Installing ASSS\|~~The~~ installation instructions]].		This page will guide you through the process of configuring an [[ASSS]] server. This page is a continuance of [[Installing ASSS\|the installation instructions]].

	== Configuring ASSS ==		== Configuring ASSS ==

Cheese at 07:55, 29 May 2011

2011-05-29T07:55:45Z

← Older revision		Revision as of 07:55, 29 May 2011
Line 1:		Line 1:
	This page will guide you through the process of configuring an [[ASSS]] server. This page is a continuance of [[Installing ASSS\|The installation instructions]].		This page will guide you through the process of configuring an [[ASSS]] server. This page is a continuance of [[Installing ASSS\|The installation instructions]].

	Before beginning, you should probably read the '''userguide''' located in /docs ]. It's probably most important to read the "File Layout" section, which explains where the important files reside when you extract the ASSS package.

	You also want to make sure that if you are not going to use MySQL or Python that you disable the appropriate modules. Or conversely, make sure that all the System Requirements are installed before proceeding any further.

	== Configuring ASSS ==		== Configuring ASSS ==

Cheese at 07:54, 29 May 2011

2011-05-29T07:54:36Z

← Older revision		Revision as of 07:54, 29 May 2011
Line 1:		Line 1:
	This page will guide you through the process of ~~setting up~~ an [[ASSS]] server. It is ~~assumed that you have already downloaded the appropriate release from~~ [~~http://sscx.net/asss/ the website~~]. Before beginning you should read the '''userguide''' located in /docs ~~or [http://sscx.net/asss/userguide.html on the ASSS website~~]. It's probably most important to read the "File Layout" section, which explains where the important files reside when you extract the ASSS package.		This page will guide you through the process of configuring an [[ASSS]] server. This page is a continuance of [[Installing ASSS\|The installation instructions]].

			Before beginning, you should probably read the '''userguide''' located in /docs ]. It's probably most important to read the "File Layout" section, which explains where the important files reside when you extract the ASSS package.

	You also want to make sure that if you are not going to use MySQL or Python that you disable the appropriate modules. Or conversely, make sure that all the System Requirements are installed before proceeding any further.		You also want to make sure that if you are not going to use MySQL or Python that you disable the appropriate modules. Or conversely, make sure that all the System Requirements are installed before proceeding any further.

	~~== Building Linux Version ==~~

	* tar zxvf asss-1.x.y.tar.gz
	* cd asss-1.x.y/src
	* edit [[system.mk]] (in your favorite text editor)
	* make deps
	** If you're running into mysql, db, python, and other dependency errors check build/[[deps.mk]].
	* make

	== Configuring ASSS ==		== Configuring ASSS ==
Line 182:		Line 175:
	In Linux, just run ./scripts/run-asss, which handles ?shutdown -r. ''IMPORTANT:'' You will need to edit the ASSSHOME variable defined inside the script to point to the directory you extracted ASSS.		In Linux, just run ./scripts/run-asss, which handles ?shutdown -r. ''IMPORTANT:'' You will need to edit the ASSSHOME variable defined inside the script to point to the directory you extracted ASSS.

			[[Category:ASSS]]
	[[Category:Guides]]		[[Category:Guides]]
	~~[[Category:ASSS]]~~

An Alabatross: Restored User's Guide link to http://asss.yi.org/asss/files/userguide.html

2007-01-18T01:54:27Z

Restored User's Guide link to http://asss.yi.org/asss/files/userguide.html

← Older revision		Revision as of 01:54, 18 January 2007
Line 129:		Line 129:
	</pre>		</pre>

	You've probably noticed that lines prefixed with cmd_ enable a player to use that command. Also, a line prefixed with privcmd_ allows a player to use a private command (one that can be messaged to a player). There are other capabilities, such as changesettings above, that a player needs in order to perform some actions, such as change the settings. Here's a complete list of the non-command capabilities (from [[grelminar]]'s User Guide):		You've probably noticed that lines prefixed with cmd_ enable a player to use that command. Also, a line prefixed with privcmd_ allows a player to use a private command (one that can be messaged to a player). There are other capabilities, such as changesettings above, that a player needs in order to perform some actions, such as change the settings. Here's a complete list of the non-command capabilities (from [[grelminar]]'s [http://asss.yi.org/asss/files/userguide.html User Guide]):

An Alabatross: Took out reference to grelminar's user guide at http://sscx.net/asss/userguide.html - dead link

2007-01-18T01:51:10Z

Took out reference to grelminar's user guide at http://sscx.net/asss/userguide.html - dead link

← Older revision		Revision as of 01:51, 18 January 2007
Line 129:		Line 129:
	</pre>		</pre>

	You've probably noticed that lines prefixed with cmd_ enable a player to use that command. Also, a line prefixed with privcmd_ allows a player to use a private command (one that can be messaged to a player). There are other capabilities, such as changesettings above, that a player needs in order to perform some actions, such as change the settings. Here's a complete list of the non-command capabilities (from [[grelminar]]'s ~~[http://sscx.net/asss/userguide.html~~ User Guide]):		You've probably noticed that lines prefixed with cmd_ enable a player to use that command. Also, a line prefixed with privcmd_ allows a player to use a private command (one that can be messaged to a player). There are other capabilities, such as changesettings above, that a player needs in order to perform some actions, such as change the settings. Here's a complete list of the non-command capabilities (from [[grelminar]]'s User Guide):

An Alabatross: changed 'edit the ones in groupdef.dif' to 'edit the ones in groupdef.dir', other spelling errors

2007-01-18T00:29:16Z

changed 'edit the ones in groupdef.dif' to 'edit the ones in groupdef.dir', other spelling errors

← Older revision		Revision as of 00:29, 18 January 2007
Line 16:		Line 16:
	You will probably want to take a look at the [[modules.conf]] file before running ASSS for the first time to check for dependency issues.		You will probably want to take a look at the [[modules.conf]] file before running ASSS for the first time to check for dependency issues.

	Note: A ';' ~~preceeds~~ a comment and all following characters before a newline are ignored.		Note: A ';' precedes a comment and all following characters before a newline are ignored.

	=== Changing Zone Name and Description ===		=== Changing Zone Name and Description ===
	The zone name and description are both defined in the /conf/[[global.conf]] file. Edit this file to set your zone's name and description. Set both Billing:ServerName and Directory:Name to your desired zone name, and set Directory:Description to the description you want listed on the [[directory server]]. You'll also want to set the current directory servers in Server1, Server2, etc. At this time the following directory servers work: ''sscentral.sscuservers.net'' and ''sscentral.subspacehq.com''.		The zone name and description are both defined in the /conf/[[global.conf]] file. Edit this file to set your zone's name and description. Set both Billing:ServerName and Directory:Name to your desired zone name, and set Directory:Description to the description you want listed on the [[directory server]]. You'll also want to set the current directory servers in Server1, Server2, etc. At this time the following directory servers work: ''sscentral.sscuservers.net'' and ''sscentral.subspacehq.com''.

	To have ASSS send its info to the directory servers, uncomment (remove the semicolon ~~preceeding~~) the ''directory'' module in [[modules.conf]]:		To have ASSS send its info to the directory servers, uncomment (remove the semicolon preceding) the ''directory'' module in [[modules.conf]]:
	<pre>		<pre>
	directory		directory
Line 57:		Line 57:
	You may also need to log in once using ?passwd <subspace login password> and rejoining the zone before commands work. This is to validate that only someone using your password is allowed to use sysop commands, in case the [[Biller\|Billing server]] goes down or you don't use a biller.		You may also need to log in once using ?passwd <subspace login password> and rejoining the zone before commands work. This is to validate that only someone using your password is allowed to use sysop commands, in case the [[Biller\|Billing server]] goes down or you don't use a biller.

	Notice that you have given yourself access to group Sysop in (global). This means that you will have Sysop ~~privilages~~ in all arenas. To limit a player to have only access in a single arena, put the player in the section pertaining to that arena. For example, to only have sysop powers in arena basketball you would do:		Notice that you have given yourself access to group Sysop in (global). This means that you will have Sysop privileges in all arenas. To limit a player to have only access in a single arena, put the player in the section pertaining to that arena. For example, to only have sysop powers in arena basketball you would do:

	<pre>		<pre>
Line 72:		Line 72:
	</pre>		</pre>

	Also note that Sysop is an arbitrary group that can have any number or ~~privilages~~. You can make up your own groups, too, and limit their special abilities and commands. Say we wanted to add a group called SettingChanger, who could change the settings in a single arena (let's say basketball), but not use arena messages or spec other players. First we'll add the players (in this case, Priitk) to the appropriate group in staff.conf:		Also note that Sysop is an arbitrary group that can have any number or privileges. You can make up your own groups, too, and limit their special abilities and commands. Say we wanted to add a group called SettingChanger, who could change the settings in a single arena (let's say basketball), but not use arena messages or spec other players. First we'll add the players (in this case, Priitk) to the appropriate group in staff.conf:

	<pre>		<pre>
Line 87:		Line 87:
	</pre>		</pre>

	Then, in groupdef.conf we'll add the group and it's ~~privilages~~.		Then, in groupdef.conf we'll add the group and it's privileges.

	<pre>		<pre>
	; conf/groupdef.conf		; conf/groupdef.conf
	; don't edit this file, edit the ones in groupdef.~~dif~~		; don't edit this file, edit the ones in groupdef.dir

	[SettingChanger]		[SettingChanger]
Line 109:		Line 109:
	<pre>		<pre>
	; conf/groupdef.conf		; conf/groupdef.conf
	; don't edit this file, edit the ones in groupdef.~~dif~~		; don't edit this file, edit the ones in groupdef.dir

	[SettingChanger]		[SettingChanger]
Line 120:		Line 120:
	</pre>		</pre>

	and then create a file in groupdef.dir called setchanger which contains the ~~privilages~~ and commands:		and then create a file in groupdef.dir called setchanger which contains the privileges and commands:

	<pre>		<pre>

BaK: /* Editing Arena Settings */ "what" is ambiguos

2006-12-04T18:54:02Z

Editing Arena Settings: "what" is ambiguos

← Older revision		Revision as of 18:54, 4 December 2006
Line 156:		Line 156:
	=== Editing Arena Settings ===		=== Editing Arena Settings ===

	To change ~~what~~ default arena (called public in [[Subgame]]) is using, edit /arenas/(default)/[[arena.conf]]. Note that this file may use data from other files using #include statements. To override certain settings without editing them from the original files, you can define them at the end of a file. For example, if you wanted svs settings, but the map to be "mymap.lvl" you could set your arena.conf to be:		To change the settings the default arena (called public in [[Subgame]]) is using, edit /arenas/(default)/[[arena.conf]]. Note that this file may use data from other files using #include statements. To override certain settings without editing them from the original files, you can define them at the end of a file. For example, if you wanted svs settings, but the map to be "mymap.lvl" you could set your arena.conf to be:

	<pre>		<pre>

I88gerbils: /* Building Linux Version */ added note about dependency issues on some asss builds

2006-07-03T20:32:28Z

Building Linux Version: added note about dependency issues on some asss builds

← Older revision		Revision as of 20:32, 3 July 2006
Line 9:		Line 9:
	* edit [[system.mk]] (in your favorite text editor)		* edit [[system.mk]] (in your favorite text editor)
	* make deps		* make deps
			** If you're running into mysql, db, python, and other dependency errors check build/[[deps.mk]].
	* make		* make

Smong: /* Building Linux Version */ oops added make deps

2006-06-30T22:53:34Z

Building Linux Version: oops added make deps

← Older revision		Revision as of 22:53, 30 June 2006
Line 8:		Line 8:
	* cd asss-1.x.y/src		* cd asss-1.x.y/src
	* edit [[system.mk]] (in your favorite text editor)		* edit [[system.mk]] (in your favorite text editor)
			* make deps
	* make		* make

Smong: /* Building Linux Version */ update Makefile -> system.mk

2006-06-30T17:33:44Z

Building Linux Version: update Makefile -> system.mk

← Older revision		Revision as of 17:33, 30 June 2006
Line 7:		Line 7:
	* tar zxvf asss-1.x.y.tar.gz		* tar zxvf asss-1.x.y.tar.gz
	* cd asss-1.x.y/src		* cd asss-1.x.y/src
	* edit [[~~Makefile~~]] (in your favorite text editor)		* edit [[system.mk]] (in your favorite text editor)
	* make		* make


	== Configuring ASSS ==		== Configuring ASSS ==