What is it?

The database is the main area where you will be able to change settings on your server easily and nicely. It also has authentication so only certain people can change certain settings. This wiki page will have certain things you should know about how to do stuff on the database. It'll be populated as something important comes up.

User Permissions

User permissions is an important way to prevent certain users from modifying stuff you don't want them to. The default permissions that come with the database are: "all" gives access to everything on the database "dev.*" gives access to all features marked under dev. "dev.usermanagement" lets you add/delete users and modify permissions of users (Dangerous to give to someone as they can theoretically give themselves all permissions) "dev.systemmanagement" lets you add/delete modules.

As well as being able to perform these features, you can also deny certain users permissions using "~". For instance, if you want to give someone all permissions except the ability to modify users, you would give them the "all" and the "~dev.usermanagement" permission. Or if you want to let them do anything except developer functions, you would do "all" and "~dev.*"

Modules often get their own prefix and then sub permissions below that. The developer feature's prefix is "dev". The security module and it's addon module the Sector module operate under the "security" prefix. If you want to give someone access to all of a module's features, you can add a star after the prefix and dot. For instance: "security." gives access to all of the security module's features, but "security.writecard" only lets you write a card on the system. You can also deny the sub permissions to a module, like "security." and "~security.writecard". The possibilities are endless!

Module Installation

You can install modules through the dev tab and clicking manage modules (or something like that) Then, move all the modules you want to the right list by selecting the module you want and clicking the button below the list. # indicates the module has requirements. It will automatically move all required modules to the right list if moved or be moved back to the left if it's required modules are moved back to the left list. % indicates there is database files that will be downloaded. @ indicates there is server files that will be downloaded.

Remember when installing modules, if you already have modules installed, reselect them. The installer wipes all modules saved and reinstalls them.'

When done, click setup modules. This will install all modules on the server and database. You then have to restart the server and database.

If you want to install modules not officially supported, you can go into settings in the dev module and add the raw url to their modules.txt file to the externalModules setting and save. It'll pull that file as well.

Anonymous Bug Reporting

The system has an error handler built in. If the database or a module crashes, by default it will submit the error report to the developer and to myself (creator). If you want to disable this, you have to manually go into the dbsettings.txt file in the database's .app folder and set "anonymousreport" equal to false.

Module Updates

If any updates are detected by the system (assuming you have internet card in) the database will alert you that updates are available. In order to install any updates, you have to do the steps in the Module Installation instructions above completely. If you wish to disable this, you will have to change it manually in the dbsettings.txt config. Soon, it should be a button made available in settings in the dev module, but at the moment its manual.

Updating Servertine

If a new version of Servertine is released and you have an internet card in, you will receive a prompt that a new version of Servertine was released. If you wish to install the new version, you can simply click install (Server and all other components must be updated manually. Only database is automatic) This will install all new files. All settings, modules, and the userlist will all be preserved, so no data is lost. You can always deny the install either temporarily (it'll come up next time the db is started) or select the option which stops version checking. These can all be reverted or changed in bootconfig.txt file.

In OpenOS, you can force a reinstall of all Database files by adding --install after you type the program name with a space before it. Example: if the boot file is named boot.lua, the command to start the program is boot --install

Misc

Nothing yet :P