To achieve the target of reproduction build, the following action should be taken:
- Strip the result, via modification gcc spec file
- Set and export the SOURCE_DATE_EPOCH environment variable, say
SOURCE_DATE_EPOCH=$(git log -1 --pretty=%ct)
To achieve the target of reproduction build, the following action should be taken:
SOURCE_DATE_EPOCH=$(git log -1 --pretty=%ct)
Two TrueNAS (FreeNAS) NAS system are setup for the purpose of data backup, including the resumed blog running on ESXi virtual machine, replaced the Buffalo lS-WXL and WdMycloud.
The benefit of FreeNAS:
The blog data is backup into the 1st FreeNAS, manually after updating the blog.
The 1st FreeNas will generate a snapshot every day, thanks to the Periodic Snapshot Task provided by FreeNAS system, and them replicate the snapshot to the 2nd FreeNas machine, also thanks to the Replication Task of freeNas system.
Hardware spec of 1st NAS:
Cost: without Data Disk:
AMD T610 Plus RMB 185
Power:19V4.74 7.4*5.0mm RMB 30
SATA2 32G SSD RMB 45
DDR3L 8G/1600 X2 RMB 398
———————————————————————–
Total RMB 658
Hardware spec of 2st NAS:
The Raid sub-system is not a best choice.
As Home User, we don’t care about the data lost, or data server down in a short period of time. That’s way we two NAS system / Data replication instead of raid sub-system.
The new wordpress platform is based on Linux Application From Scratch.
The mysql server, php, nginx (openresty), and all dependency, including gcc and C library, any code in User Space, are build from source code, and installed into /opt/local as root directory.
The benefit of LAFS (LFS for wordpress application):
Could be running on any linux platform, as long as same mode (x86-64), and support the selected basic instruction set (Sandy Bridge). The software is binary compatible,to run it on a new linux machine, just the copy the image to the /opt/local.
Thanks to the linux kernel API backword compability, the kernel version have no side impacts for most of application.
With the help of LAFS implementation, we can build blog platform, modification blog contents locally, and push to the remote public vps with easy:
Just the file level sync (rsync):
Dev Machine ==> Local Production Env ==> Remote Public Production Env
( Intel E3 ) ( Vmware ESXi ) (VPS)
Sept 2021