On this page you are able to change some basic server settings. All though these are basic settings you should know a little bit what you are doing.

The most common setting to change are your localization settings. These settings determine for example location between you and mobile devices, sunrise and sunset and specific formatting.

The current amount are quite sparse, more options will be added in the future

Localization settings

Localization settings are used to determine the location of the server. Clients have the possibility to provide their location to the server. To make sure the server can calculate the distance between the server and the client it is wise to set a correct location. This will enable localization functionality like perform actions when a client comes in a close range. Next to this the server does calculations based on time zone which is is used for sunrise and sunset calculations.

To get your positions latitude or longitude (your exact location) you can search this up for example at askgeo.com or let the web interface guess the position by "asking" it your device/browser.
We can assure you that this information will never ever be sent to us or whoever/whatever.

Network settings

By default the server tries to find out the ip address to bind it's services to. On this page you are able to set the primary server behavior when it will bind it's services. To be service specific got to the services tab.

Here you can change the ip address the server binds to when you choose for non auto discovery method.

Server discovery

Enable/Disable the possibility for the server to be automatically found by clients.

Only change this if you want to perform discovery on a different ip address then the server uses or your clients are on a different network but still able to reach the server's ip. This setting is for example useful when clients are in a different VLAN.

This should only be changed if you have clients targeting a different port then usual. You will be able to change this setting in non mobile PiDome clients unless you are using your own Mobile implementation.

Server actions

Below are server actions used for diagnostics. Often when there is an issue asked is to enable debug logging which puts more information in the log file. Be careful with the log file as it can contain sensitive information.

Next to debug logging when stuff really goes bad, or for supporting the log file you can perform a full memory dump of the application. This writes a file to disk. When making a heap dump the server try to clear memory and will pause to create an as clean file possible.

Debug logging

With the below button you enable/disable debug logging. If the server has been started with debug or trace logging on this button turns it off.
The log file is found at "<Installation dir>/logs/system/appLog.txt".

Perform heap dump

This is a dangerous tool, it dumps the complete system to file to be read by a profiling application. When performing a Heap Dump The server will PAUSE until the dump is completed. This is only needed to perform memory analysis. To be able to do memory analizing two memory dumps are needed one taken before and one after a amount of time when excessive memory usage is observed.

Do not press this button twice in a row, wait for the message the system is done!

Security

This part covers security handled in the server.

When SSL mode is enabled all communications are done over a secure connection. This is the default setting.

By default a certificate is regenerated at every server restart. This takes up a couple of seconds.

Remote login

By default the administrator is only able to login at the local network. When remote login is enabled the administrator is able to login in from remote locations. This can cause security holes so be very careful!

Server actions

This is the safest way to shutdown the server.