(Grav GitSync) Automatic Commit from grav
This commit is contained in:
parent
30dc7c33c7
commit
ae202cb8ad
|
@ -1,13 +1,16 @@
|
||||||
---
|
---
|
||||||
title: Migrating to Raspberry Pi servers
|
title: 'Migrating to Raspberry Pi servers'
|
||||||
taxonomy:
|
taxonomy:
|
||||||
tag:
|
tag:
|
||||||
- NixOS
|
- NixOS
|
||||||
- Raspberry Pi
|
- 'Raspberry Pi'
|
||||||
- ARM
|
- ARM
|
||||||
date: '2022-11-28 00:00'
|
date: '2022-11-28 00:00'
|
||||||
summary:
|
summary:
|
||||||
size: 200
|
size: 200
|
||||||
|
process:
|
||||||
|
markdown: true
|
||||||
|
twig: false
|
||||||
---
|
---
|
||||||
|
|
||||||
# Migrating from x86 to ARM (Raspberry Pi)
|
# Migrating from x86 to ARM (Raspberry Pi)
|
||||||
|
@ -182,7 +185,7 @@ lock file which doesn’t work with my NFS setup. Luckily it isn’t that much
|
||||||
data.
|
data.
|
||||||
|
|
||||||
All the relevant on device data gets backed up with Restic and stored on my NAS,
|
All the relevant on device data gets backed up with Restic and stored on my NAS,
|
||||||
an external harddrive and in an offsite OpenSwift bucket.
|
an external harddrive and in an offsite OpenStack Swift bucket.
|
||||||
|
|
||||||
I noticed that the clock in the Raspberry Pis doesn’t keep its time after a
|
I noticed that the clock in the Raspberry Pis doesn’t keep its time after a
|
||||||
reboot. Therefore I point them all to my firewall which acts as the local NTP
|
reboot. Therefore I point them all to my firewall which acts as the local NTP
|
||||||
|
|
Loading…
Reference in New Issue