Skip to main content
Version: 3.x

Useage Questions

Use nohup to start the background process, the page keeps turning and will not end?​

Execute the script in Batch Execution or Deployment Configuration in the background with nohup or &, the standard output of the command needs to be redirected to /dev/null, for example, the following command to start Tomcat:

cd web/WEB-INF/
nohup ./startup.sh &

Change the above command to:

cd web/WEB-INF/
nohup ./startup.sh > /dev/null &

Can I use my own key pair?​

Of course, you can upload your own key pair since v2.3.0, you can upload your key pair in System Management \ System Settings \ Key Settings.

Add general release application git clone error​

Spug The ability to interactively enter the account password to log in to the git repository is not provided. If it is a public repository, http/https/ssh any one of the protocols can be used, but if it is a private repository, it is recommended to use the ssh protocol to configure the key to access. The http/https protocol needs to be accompanied by a user name and password, for example, https://yourname:password@gitee.com/openspug/spug.git If the account name contains the @ symbol, it needs to be replaced with %40. It is especially important to note that if you are deployed by docker, you need to make sure that the repository can be accessed in the container, not on the host.

Host Console or Execution Release Page No Content​

The most common reason for this is that the Websocket connection failed to establish. Most of the time, this is caused by adding a layer of proxy tools such as nginx when deploying. These proxy tools cannot handle Weboscket requests by default. This requires you to configure it to support forwarding Websocket requests. The following is an example of Nginx, here it is assumed that you use docker to deploy Spug, and the 8000 port of the host is mapped:

server {
  listen 80;
  server_name xxx.xxx.xxx;

  location / {
    proxy_pass http://127.0.0.1:8000;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  }

  location ^~ /api/ws/ {
    proxy_pass http://127.0.0.1:8000;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  }

  error_page 404 /index.html;
}

File Manager Upload File Error 413 Request Entity Too Large​

Uploading files is affected by the client_max_body_size of Nginx, please change the value to a suitable size, refer to the following configuration:

warning

docker container path: /etc/nginx/nginx.conf, you can edit it outside the container and copy it to the container through docker cp, or you can execute vi in the container to modify it directly, don't forget to restart the container.

server {
  listen 80;
  server_name xxx.xxx.xxx;
  client_max_body_size 100m;

  ...
}

DingTalk does not receive notification?​

DingTalk robot security settings add the public network address of the server where Spug is deployed to IP Address, or use Custom Keyword to fill in Notification, as shown in the figure below

about