server setup compatible with bitrix and other strange frameworks requiring long execution time and big request size limits. It automatically configures ssl certs.

name df99a27c64 fix for wrap script 1 rok pred
archives 9b691c79c1 init 1 rok pred
backups 9b691c79c1 init 1 rok pred
configs b272fed40d fixed backupper config; ignition2qemu can generate qemu from butane now 1 rok pred
deploy-addons 18e7bcc983 service stop before reinstall 1 rok pred
docker 999f940fa5 deleted unused cron.d; we use the one from configs 1 rok pred
scripts df99a27c64 fix for wrap script 1 rok pred
ssh 18e7bcc983 service stop before reinstall 1 rok pred
volumes 9b691c79c1 init 1 rok pred
.env e0aec57474 add localhost to default config 1 rok pred
.gitignore dab1283ac1 nixos now can be accessed via ssh and starts docker-compose successfully 1 rok pred
docker-compose.yml 9b691c79c1 init 1 rok pred
down.sh 6cc9f3428f enhance vm production; forward ports 443,80,udp:443 to vm; use down.sh/up.sh for docker 1 rok pred
flake.lock 58afb57f9c progressing nixos vm build 1 rok pred
flake.nix fb47bf371c size down vm to 30gb 1 rok pred
readme.md 7844feb9a5 chmod /data in nixos before docker-compose start 1 rok pred
run.sh 6cc9f3428f enhance vm production; forward ports 443,80,udp:443 to vm; use down.sh/up.sh for docker 1 rok pred

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.