The AUR package maintained by @devome uses the stable version of GCopy for building.
Since the GCopy frontend and backend can be installed separately, the AUR package splits them into two packages: the backend gcopy and the frontend gcopy-web. You can install them on different hosts, or you can install them on the same host.
## Install the backend, you can also use yay to install
paru -Sy gcopy
## Install the frontend, you can also use yay to install
paru -Sy gcopy-web
For the backend, the configuration file is located at /etc/gcopy/gcopy.env
. Edit it according to the comments, for example:
APPEND_ARGS="-app-key='rqMrHprILwYintES4UeQc0wM/252SLy59y7LMYKXJE0=' -smtp-host='smtp.example.com' -smtp-password='your_password' -smtp-username='[email protected]'"
For the app-key
, you can generate a random string using the following command:
openssl rand -base64 32
For the frontend, the configuration file is located at /etc/gcopy/gcopy-web.env
. Edit it according to the comments. If the backend and frontend are on different hosts, be sure to modify the SERVER_URL
.
After configuration, you can start the services:
## Start the backend
sudo systemctl enable --now gcopy.service
## Start the frontend
sudo systemctl enable --now gcopy-web.service
In production mode, it is recommended to deploy behind a reverse proxy, such as Nginx or Apisix. This makes it easier to manage certificates and configure the proxy. You will need to prepare a domain name and the corresponding certificate. For Nginx, refer to /usr/share/gcopy-web/nginx-example.conf
.