Description of server configuration file (after modification, restart the server to take effect without restarting the agent)
1、server/config/application Yml, except for the part marked in red that needs to be modified, other parts can be temporarily defaulted, and can be adjusted according to the actual scenario later
Change the MySQL database connection information marked in red to your own MySQL connection informationPostgreSQL Connection Configuration DescriptionOracle Connection Configuration Description
Note: If MySQL and the server are not on the same host, you need to configure MySQL root users to allow remote access: mysql 5.7 or 5.6 explain , mysql8 explain
The administrator's login account/password is defaulted as follows: admin/111111, you can change it to your favorite account/password
wgToken is the communication key between server and agent. The wgToken values in the server and agent configuration files should be consistent, It can be defaulted temporarily
9999 is the web access port of the server, which can be modified to other ports (it cannot be the same as the port of the daemon wgcloud daemon release. The default daemon port is 9997, which can be modified in server/config/ At the same time, the modified port is also used for access, It can be defaulted temporarily
If you want to use the web ssh function, the default port of the web ssh is 9998. Then the 9998 port of the host running the server should be open and not blocked by the firewall. The web ssh switches and ports are modified in the following configuration files, It can be defaulted temporarily
Note the format rules of yml file. A space should be reserved after the colon of each configuration item . In addition, except for the parts marked in red, others can be defaulted temporarily
Tips: If the firewall or security group of the server host is running, you need to release these two ports: 9999(sever web)、9998(web ssh , The port can not be opened without web ssh)View the Linux firewall port opening instructions
  port: 9999
      timeout: 120m
    context-path: /wgcloud
#Log file output path
    path: ./log
# Database configuration
    name: wgcloud-server
    #If the database is connected to MySQL 8.x, it is recommended to change the driver-class-name to com.mysql.cj.jdbc.Driver . If it is MySQL 5.x, just keep the default
    driver-class-name: com.mysql.jdbc.Driver
    url: jdbc:mysql://localhost:3306/wgcloud?characterEncoding=utf-8&characterSetResults=utf8&autoReconnect=true&useSSL=false&allowMultiQueries=true
    username: root
    password: mysql
      validationTimeout: 3000
      connectionTimeout: 60000
      idleTimeout: 60000
      minimumIdle: 10
      maximumPoolSize: 10
      maxLifeTime: 60000
      connectionTestQuery: select 1
    static-path-pattern: /static/**
    cache: false
  config-location: classpath:mybatis/mybatis-config.xml
  mapper-locations: classpath:mybatis/mapper/*.xml

#Custom configuration parameters
  #Administrator login account
  account: admin
  #Password of administrator
  accountPwd: 111111
  #Read only account (only browse permission, no permission to modify, delete or add, this function takes effect after upgrading to pro-version)
  guestAccount: guest
  #Password of read-only account
  guestAccountPwd: 111111
  #Communication token. The wgToken on the agent side is consistent with this
  wgToken: wgcloud
  #How many pieces of data are displayed on each page? It is recommended that it should not be less than 10
  pageSize: 20
  #Whether to enable the web ssh client, yes enable, no disable
  webSsh: yes
  #Service port of web ssh client
  webSshPort: 9998
  #The daemon accesses the url, the server service uses it, and the agent does not use it (generally the default is enough)
  daemonUrl: http://localhost:9997
  #Whether to open the public screen, yes to open, no to close, and no to login after opening the Kanban page
  dashView: yes
  #Whether the desensitization display is enabled for the host IP on the public signage page, yes is enabled, no is disabled
  dashViewIpHide: yes
  #Whether to open the large screen display board, yes to open, no to close, and the board page does not need to log in after opening
  dapingView: yes
  #Whether to automatically close the left menu, yes Yes, no No
  sidebarCollapse: yes
  #Whether to display alarm times on the list page, yes Yes, no No
  showWarnCount: no
  #Whether to enable the issuance of instructions (if it is closed, no more instructions can be added and issued), yes Yes, no No
  shellToRun: yes
  #Sensitive characters that cannot be included in the Linux command can be lowercase, and multiple characters are separated by commas
  shellToRunLinuxBlock: 'rm ,mkfs, /dev/,:(){:|:&};:,mv ,wget , install '
  #Sensitive characters that cannot be included in Windows instructions can be lowercase, and multiple characters are separated by commas
  shellToRunWinBlock: 'del ,delete ,format ,ren ,rd ,rd/s/q ,rmdir '
  #The SQL statement for data monitoring cannot be used to write sensitive characters (i.e. keywords that may be injected into SQL), which can be lowercase and separated by commas
  sqlInKeys: 'execute ,update ,delete ,insert ,create ,drop ,alter ,rename ,modify '
  #Data table monitoring interval, in seconds, 60 minutes by default
  dbTableTimes: 3600
  #API monitoring interval, in seconds, 10 minutes by default
  heathTimes: 600
  #PING monitoring interval of data communication equipment, unit: second, default: 15 minutes
  dceTimes: 900
  #Snmp monitoring interval of data communication device, unit: second, default: 20 minutes
  snmpTimes: 1200
  #Alarm buffer interval (the same alarm notification will not be sent repeatedly within this period), unit: second, default: 120 minutes
  warnCacheTimes: 7200
  #Monitoring data retention days, 30 days by default
  historyDataOut: 30
  #The node type (only used by the cluster, which is generally the default), master or slave. A cluster can only have one master and N (31 at most) slave, such as: slave1,slave2
  nodeType: master
  #Whether to enable group management, yes enable, no disable
  hostGroup: no
  #Whether to enable member account management (that is, each member can manage its own resources). Yes is enabled and no is closed. After closing,
  #new members cannot log in again (administrators and read-only accounts can log in). This function needs to be upgraded to the pro-version
  userInfoManage: no
  #The icon name of ico under server/logo/, 32 * 32, such as favicon.png, which needs to be upgraded to pro-version
  icoUrl: favicon.png
  #The logo icon name under server/logo/, 120 * 120, such as logo.png, which needs to be upgraded to the pro-version
  logoUrl: logo.png
  #System name, such as wgcloud operation and maintenance monitoring system, which needs to be upgraded to pro-version
  wgName: wgcloud Monitor
  #System abbreviation, such as wgcloud, which needs to be upgraded to the pro-version
  wgShortName: wgcloud
  #Alarm mail title prefix, this function needs to be upgraded to the pro-version
  mailTitlePrefix: '[WGCLOUD]'
  #Suffix of alarm email content, this function needs to be upgraded to pro-version
  mailContentSuffix: 'WGCLOUD'
  #Whether to display the copyright and website information at the bottom of the page. Yes is displayed, no is not displayed.
  #This function needs to be upgraded to the pro-version
  copyRight: yes

The above is only a part of the configuration file. The rest is not shown because the installation and deployment process does not need to be modified. You can customize according to the actual scenario later
Previous step    Next step