<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.multitheftauto.com/wiki/Server_admin_proposal?action=history&amp;feed=atom</id>
	<title>Server admin proposal - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.multitheftauto.com/wiki/Server_admin_proposal?action=history&amp;feed=atom"/>
	<link rel="alternate" type="text/html" href="https://wiki.multitheftauto.com/index.php?title=Server_admin_proposal&amp;action=history"/>
	<updated>2026-04-13T13:33:48Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.3</generator>
	<entry>
		<id>https://wiki.multitheftauto.com/index.php?title=Server_admin_proposal&amp;diff=21810&amp;oldid=prev</id>
		<title>EAi: Created page with 'The current system for server administration - mtaserver.conf, acl.xml and the webadmin is confusing. We need a simple, unified interface that suits both normal server owners and…'</title>
		<link rel="alternate" type="text/html" href="https://wiki.multitheftauto.com/index.php?title=Server_admin_proposal&amp;diff=21810&amp;oldid=prev"/>
		<updated>2009-10-27T22:28:48Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;#039;The current system for server administration - mtaserver.conf, acl.xml and the webadmin is confusing. We need a simple, unified interface that suits both normal server owners and…&amp;#039;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;The current system for server administration - mtaserver.conf, acl.xml and the webadmin is confusing. We need a simple, unified interface that suits both normal server owners and those who rent servers.&lt;br /&gt;
&lt;br /&gt;
The key aim of this proposal is to allow servers to be configured via the HTTP server and to make this the default route that new users use.&lt;br /&gt;
&lt;br /&gt;
==Tasks==&lt;br /&gt;
* Allow mtaserver.conf can be reloaded at runtime.&lt;br /&gt;
* Allow multiple mtaserver.conf files to be loaded, perhaps with each .conf file specifying the one to load _before_ it.&lt;br /&gt;
* Allow acl.xml to be reloaded at runtime.&lt;br /&gt;
* Allow multiple acl.xml to be loaded, specifying the file in the .conf file. Subsequent ACLs should overwrite existing ones - rights that previously were given should be denied. This will require some further thinking - if, say, banning was denied in the Everyone group in file 1, it shouldn't allow it to be granted to the Admin group in file 2.&lt;br /&gt;
* Provide script functions for setting conf file settings in a particular file (presumably limited to those that are currently loaded), and a function for reloading a particular conf file. These should be ACL'd per config file.&lt;br /&gt;
&lt;br /&gt;
==Result==&lt;br /&gt;
For most uses:&lt;br /&gt;
* mtaserver.conf: references acl.xml as the xml to load&lt;br /&gt;
* acl.xml&lt;br /&gt;
&lt;br /&gt;
For server renters:&lt;br /&gt;
* owner.conf: references owneracl.xml, sets player limit/name etc, specifies that mtaserver.conf should be loaded &lt;br /&gt;
* owneracl.xml: prevents access to owner.conf&lt;br /&gt;
* mtaserver.conf: specifies user settings, may specify a player limit, but this will be overwritten by the contents of owner.conf&lt;br /&gt;
* acl.xml&lt;br /&gt;
&lt;br /&gt;
==Other tangental issues==&lt;br /&gt;
A better interface for setting resource settings would be convenient. Many resources are now using them.&lt;/div&gt;</summary>
		<author><name>EAi</name></author>
	</entry>
</feed>