Frequently Asked Questions
Q: Is there a super administrator account in the system?
Aļ¼There is no super administrator account, but the creator of the space station can manage the space station
Q: The default is a single table API call 5 qps, how to adjust the configuration?
A: Configure the global environment variable LIMIT_POINTS=50 and adjust it to 50qps. Restart room-server for standalone and fusion-server for cluster
Q: How to white-labelling APITable?
Q: How to fix the error when publishing a self-built widget?
When publishing a widget, the error message is as shown in the figure:
A: Solution:
Install apitable/widget-cli
npm install @apitable/widget-cli@1.0.3-alpha.0 -gReplace all dependencies of vikadata in the code project with APItable
Execute in the terminal
Windows: execute in git bash terminal
yarn release --uploadHost https://xxxMac:
yarn release --uploadHost https://xxxQ: How to use self-hostd fusion-sdk?
A: Python version example
from apitable import Apitable
apitable = Apitable("_Paste_Your_API_Token_")
#Replace with your private cloud address, such as https://test.apitble.com
apitable.set_api_base("replace_with_your_environment_address")
datasheet = apitable.datasheet("dstxxxx", field_key="name")Q: Unable to pull init-settings image in k8s mode
The default path for init-settings is
apitable/apitable-ee, such asdocker.vika.ltd/vikadata/apitable-ee/init-settings:v0.20.0-alpha_build1363.
A: There are two methods to change the init-settings image path, such as docker.vika.ltd/vikadata/apitable-ee-example/init-settings:v0.20.0-alpha_build1000.
Method 1: Change the image namespace to apitable-ee and then upload it.
docker tag docker.vika.ltd/apitable/apitable-ee-example/init-settings:v0.20.0-alpha_build1000 docker.vika.ltd/vikadata/vika-ee/init-settings:v0.20.0-alpha_build1000
docker push docker.vika.ltd/apitable/apitable-ee/init-settings:v0.20.0-alpha_build1000Method 2: Set the init-settings image namespace path in config.yaml.
image:
namespace:
app:
custom:
init_settings: apitable/apitable-ee-exampleQ: How to configure GM administrators?
After logging in, obtain the user's uuid through /api/v1/user/me.
A: Configure the global environment variable SUPER_ADMINISTRATORS=uuid1,uuid2,uuid3.... Then restart the backend-server.
Q: How to configure external databases, Redis, and other services?
MySQL configuration parameters:
innodb_buffer_pool_size = 4096M
innodb_log_buffer_size = 2048M
max_allowed_packet = 1024M
sql_mode = NO_ENGINE_SUBSTITUTION
sort_buffer_size = 2M
max_connections=1000
A: The configuration involves the following environment variables. For Docker Compose, configure the .env.local file. For the Kubernetes version, configure the config.yaml/config/common file.
MYSQL_HOST: "mysql"
MYSQL_USERNAME: "root"
MYSQL_PASSWORD: "xxxx"
MYSQL_DATABASE: "vikadata"
REDIS_HOST: "redis"
REDIS_PASSWORD: "xxxx"
REDIS_DB: 0Execute the update command to take effect.
Q: How to configure email notification service and integrate with a private SMTP Server?
A: By default, private instances do not provide any third-party services, including email notification services, which means you cannot invite users as it requires email sending functionality.
Alternatively, you can configure an SMTP server by modifying environment variables and restarting the backend server.
MAIL_ENABLED=true
MAIL_HOST=smtp.xxx.com
MAIL_PASSWORD=your_email_password
MAIL_PORT=465
MAIL_SSL_ENABLE=true
MAIL_STARTTLS_ENABLE=true
MAIL_STARTTLS_REQUIRED=true
MAIL_TYPE=smtp
MAIL_USERNAME=your_emailExecute the update command to take effect.
Q: Create a record API interface, a single request can create up to 10 records, how to adjust the configuration
A: fusion-server environment variable configuration API_MAX_MODIFY_RECORD_COUNTS=20, adjust to a maximum of 20 records created in a single request. Restart room-server for the stand-alone version and restart fusion-server for the cluster version.
For more configuration instructions, please check "Environment Variables"
