server setup compatible with bitrix and other strange frameworks requiring long execution time and big request size limits. It automatically configures ssl certs.
|
|
1 年之前 | |
|---|---|---|
| archives | 1 年之前 | |
| backups | 1 年之前 | |
| configs | 1 年之前 | |
| deploy-addons | 1 年之前 | |
| docker | 1 年之前 | |
| scripts | 1 年之前 | |
| ssh | 1 年之前 | |
| volumes | 1 年之前 | |
| .env | 1 年之前 | |
| .gitignore | 1 年之前 | |
| docker-compose.yml | 1 年之前 | |
| down.sh | 1 年之前 | |
| flake.lock | 1 年之前 | |
| flake.nix | 1 年之前 | |
| readme.md | 1 年之前 | |
| run.sh | 1 年之前 |
readme.md
caddy + mariadb + php-fpm
This is server setup compatible with bitrix and other strange frameworks
requiring long execution time and big request size limits.
It automatically configures ssl certs.
It also features 2 backup mechanisms: one is just regular
tar backups (they go inside archives directory), it runs weekly and
only keeps last 5 backup files; other
is using cheap deduplication and runs casync tool. Casync
backups are inside backups directory. They run daily.
Server can be ran as docker-compose (see run.sh) or
you can build vm using ./scripts/build-qemu.sh,
start it with ./scripts/startqemu.sh.
Defaults are ok, but if you want, you can change domains, mysql user and password as well as server timezone by editing .env file. That data is used by both docker and generated virtual images.
requirements
obviously if you need to run docker-compose you need docker-compose for building vm images you need: nix package manager for building the vm openssh (ssh-keygen command) to generate keys openssh (ssh command) to access vm rclone to mount vm using sftp.