Welcome to DOFBOT-Ultra repository

Manage The Web Control Backend Process

In the factory image, the web control backend process starts automatically at boot.

1. Web Control Backend Process

The web control backend process and the handle control trial service are set to auto-start at boot in the factory image. During actual development, this may cause interference. If you do not need these services to start automatically at boot, follow the steps below.

1.1. RDK Motherboard Users

1.1.1. Temporarily Stop the Web Control Backend Process

xxxxxxxxxx
sudo systemctl stop dofbot-app.service

Or directly click "Close all processes" to stop the web control backend process.

1.1.2. Permanently Disable the Web Control Backend Process

xxxxxxxxxx
sudo systemctl disable dofbot-app.service

1.2. Raspberry Pi Motherboard Users

Refer to the section [Disable the Auto-Start Web Control Backend Process] in the previous chapter.

2. Start the Web Control Backend Process

If you permanently disabled the web control backend process in the previous step and want to restart it or restore its auto-start at boot, follow the steps below.

2.1. RDK Motherboard Users

2.1.1. Temporarily Start the Web Control Backend Process

xxxxxxxxxx
bash /home/sunrise/dofbot_ultra_ws/src/app/APP_DOFBOT_ULTRA/start_app.sh

2.1.2. Enable Auto-Start for the Web Control Backend Process

xxxxxxxxxx
sudo systemctl enable dofbot-app.service

2.2. Raspberry Pi Motherboard Users

2.2.1. Temporarily Start the Web Control Backend Process

Enter the APP_DOFBOT_ULTRA directory in Docker:

xxxxxxxxxx
cd /home/yahboom/dofbot_ultra/app/APP_DOFBOT_ULTRA
sh start_app.sh

2.2.2. Enable Auto-Start for the Web Control Backend Process

Refer to the section [Disable the Auto-Start Web Control Backend Process] in the previous chapter.

Modify the docker-compose.yaml file on the host and set ENABLE_APP to true.

Save and exit, then run these two commands in sequence:

xxxxxxxxxx
docker compose down
docker compose up -d

If the web interface cannot connect to the arm, Dify may be occupying resources. Close Dify before reconnecting. The command to close Dify is:

RDK:

xxxxxxxxxx
cd /home/sunrise/dify-1.9.2/docker
./docker-compose-linux-aarch64 down -d

Raspberry Pi:

# Run on the host
shut_dify