x86_64
CPU architecture/var/www/builder-collab
).8033
).www-data
for both user and group).my-builder.com
)./var/www/builder
).localhost
, user: builder
, password: secret-db-password
, database: builder
).builder-collab-linux
and has owner execute permission;config.json
;bashmkdir /var/www/builder-collab
cd /var/www/builder-collab
wget https://update.site.pro/assets/installer/builder-collab/builder-collab-linux -O /var/www/builder-collab/builder-collab-linux
chmod u+x /var/www/builder-collab/builder-collab-linux
echo '{}' > /var/www/builder-collab/config.json
chown -R www-data:www-data /var/www/builder-collab
config.json
file and set configuration in JSON format./var/www/builder-collab/cert-bundle.pem
and private key to file /var/www/builder-collab/private-key.pem
). In configuration paths to certificate bundle and private key must be absolute. Also make sure that those files are readable by builder user and group configuration.json{
"host": "my-builder.com",
"port": 8033,
"user": "www-data",
"group": "www-data",
"certBundlePath": "/var/www/builder-collab/cert-bundle.pem",
"privateKeyPath": "/var/www/builder-collab/private-key.pem",
"builderPath": "/var/www/builder",
"db": [
{
"id": "local",
"driver": "mysql",
"host": "localhost",
"user": "builder",
"password": "secret-db-password",
"database": "builder"
}
]
}
/var/www/builder-collab/builder-collab-linux run
(and stop it by clicking Ctrl+c
), it's inconvenient, since if you restart a server you will also need to remember to go and run this executable. It would be more convenient if this happened automatically and for this we will need to setup it to run as system service.systemd
systemd
, rsyslog
and logrotate
then system service can be setup in automatically by running command:bash/var/www/builder-collab/builder-collab-linux register
this command will set it up as systemd
service (service name will be sitepro-builder-collab
), enable that service and start it. It will also setup logging through syslog
and log rotation through logrotate
.systemd
commands:bash# to stop service run
systemctl stop sitepro-builder-collab
# to start service run
systemctl start sitepro-builder-collab
# to restart service run
systemctl restart sitepro-builder-collab
# to get status of the service run
systemctl status sitepro-builder-collab
systemd
then you will have to figure out how to configure your specific system on your own./var/www/builder/config.json
.collaboration
in builder configuration.json"collaboration": {
"ws": "wss://my-builder.com:8033"
}
the ws
field of the option collaboration
must have a string value that starts with ws://
(or wss://
if builder installation uses HTTPS) followed by host name (in this example my-builder.com
) colon :
and port (in this example 8033
).bash/var/www/builder-collab/builder-collab-linux update
this command will check for updates and if there is new version it will try to download it and restart the service.systemd
) then you can alternatively run command:bash/var/www/builder-collab/builder-collab-linux update-no-restart
You can (and should) also setup CRON
job to run this command regularly (ex. once a day), so that it could update it self whenever new version becomes available.root
for service restart to work.