Detached mode and logs about zoraxy HOT 3 CLOSED

Okay now it is running with systemd. Did not think about systemd :D I needed to modify your scripts and now it runs just fine. For quick testing a "-d" would still be great :)
Please add one of the solutions to the docs.

Here are my steps:

1. Create start.sh in the zoraxy folder with:

nano start.sh

Put in those lines

#!/bin/bash
./zoraxy -port=:8000

2. make executable with

chmod +x start.sh

3. Now create systemd-service with

sudo nano /etc/systemd/system/zoraxy.service

Put in following lines:

[Unit]
Description=Zoraxy Reverse Proxy Server
After=network-online.target #waits for network to be online
Wants=network-online.target

[Service]
Type=simple

User=root   #no sudo required in start.sh
Group=root
WorkingDirectory=/zoraxy/src/    #folder where zoraxy is
ExecStart=/bin/bash /zoraxy/src/start.sh     #absolute path for start.sh

[Install]
WantedBy=multi-user.target

4. Start and enable autostart with:

sudo systemctl enable --now zoraxy.service

Now status and logs can be displayed with:

sudo systemctl status zoraxy

Logs-files would still be great, but thanks for the help with autostart
A sidenote for LXC-Users: After login as root the working directory is not /zoraxy/src but /root/zoraxy/src
(/root/ is the home of root user) Tested with LXC Ubuntu 22.04

from zoraxy.

Thanks for that grate tool! 👍🏻

A little fix. :)

Description=Zoraxy Reverse Proxy Server
#waits for network to be online
After=network-online.target
Wants=network-online.target

[Service]
Type=simple

#no sudo required in start.sh
User=root   
Group=root

#folder where zoraxy is
WorkingDirectory=/zoraxy/src/    
#absolute path for start.sh
ExecStart=/bin/bash /zoraxy/src/start.sh     

[Install]
WantedBy=multi-user.target

from zoraxy.

"-d" argument seems like an interesting idea. However, adding this might bring some issue with Windows compatibility.
For my linux setups, I am using systemd for this purpose. Here is how I did it.

First, you would like to create a start.sh file next to your zoraxy binary. Assuming your binary file is located at /home/user/zoraxy/src/zoraxy

cd /home/user/zoraxy/src/zoraxy
nano start.sh

Put the following lines into start.sh, save and exit

#!/bin/bash
sudo ./zoraxy

Then assign the correct permission to the start script

sudo chmod 775 ./start.sh 

Next, you can add it to systemd service with the following commands

cd /etc/systemd/system/
sudo systemctl enable systemd-networkd.service systemd-networkd-wait-online.service
sudo nano zoraxy.service

In the service file, fill in the following info

[Unit]
Description=Zoraxy Reverse Proxy Server
After=systemd-networkd-wait-online.service
Wants=systemd-networkd-wait-online.service

[Service]
Type=simple
ExecStartPre=/bin/sleep 10
WorkingDirectory=/home/user/zoraxy/src/
ExecStart=/bin/bash /home/user/zoraxy/src/start.sh

Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

Lastly, enable and start the systemd service

sudo systemctl enable zoraxy
sudo systemctl start zoraxy

Then it should be running as a valid daemon which will start following your server (or container) startup. As I am no expert in LXC, I can only provide you answer under normal Linux (Debian) based installation. If you have issues using systemd in your container, I guess you might need to seek help from the developer who provided the container / docker configs.

from zoraxy.