Server management settings
Last updated
Was this helpful?
Last updated
Was this helpful?
Bitcart has a few server management settings available.
They are accessible only by the superusers.
Superusers are the users of the instance with admin privilege.
The first registered user is the super user, then they can add new ones from server management settings.
The server management settings don't leak the privacy of other users, super users can't view other users stores or wallets.
If you are the super user, you will be able to enter the settings by clicking on the profile icon->server management settings
From the user management page, you will be able to view all users registered on your instance, create new users or delete existing ones. Also, you can change a user's password and optionally make someone a superuser.
Note that, when editing user, it is not possible to view their existing password.
It is because, Bitcart is secure and doesn't store plain text passwords. Only hashed passwords are stored.
You can click on the switch to make someone a superuser or make someone a regular user instead.
IMPORTANT: do NOT switch your own user, it will make you loose the superuser rights. The only way to recover will be via the database. It will be disallowed in the future versions of admin panel to avoid confusion.
From the server logs page, you will be able to check server logs.
The logs are ordered by their date-the latest log displayed the first.
Logs are aggregated by day.
It is possible to delete logs (except for the today's log, as it is used by the instance).
You can also download the log, to send it for troubleshooting purposes for example.
From the maintenance commands page, you can execute common actions-upgrade your server or clean up it.
It will start the update process. During it your instance might be unavailable, and the page won't automatically reload after the update.
The update process will upgrade the cloned bitcart-docker repository, upgrade the docker-compose generator image, generate new configuration file from saved settings (from .env file), upgrade all the used docker images, recreate the modified containers and clean up the now unused images
It will start the restart process. During restart your instance might be unavailable. Use restart feature to fix some possible bugs, if you met some.
See more below
This process does the same as after upgrade-cleans up all unused bitcart images from previous upgrades
This command deletes all logs except for the currently used one.
The policies allow you to control some server-wide important settings.
If you check this on, users will not be able to register on your instance. Register link will be removed from the login page, register page will not be accessible and the API will discard any register attempts. Turn it off to enable registration back.
By enabling this setting, your instance will tell the search engines to stop indexing your site. It should disappear from search results. Note that it might not work with some search engines.
When enabled, your instance will check github for new Bitcart releases, and display a notification in the admin panel that a new update is available.
Enter the id of the store that will be displayed by the store POS. It will display this store's products and use this store's settings.
By default it is on. When enabled, users must enter their email on store POS to continue to checkout, otherwise they can continue without email.
This page is purely informational. You will see a list of connected daemons and some of their settings.
The cleanup process will do two actions: and .
By default it is on. When enabled, users can access https://admin.yourbitcart.ai/configurator, and deploy their instance from there via the .
On the store policies page, you are able to configure some settings related to all the stores on the server or the
