vince <[email protected]> writes: > Personally I wouldn't bother doing ramdisk on a pi3, pi3+ or pi4, and I'd > instead just shoot a backup of your /home/weewx tree once (to baseline it) > and then occasionally grab your archive and NOAA directories via cron or > something to another computer or dropbox or something. > > When you get down to it, all that is important is the archive and your > weewx.conf file - you can rebuild anything else in just a few minutes if it > ever becomes necessary.
While I see your point, I've done something in between, avoiding writes while not going to the trouble of a sytem image that runs out of RAM entirely after boot. My setup is a RPI3 running NetBSD, with weewx installed in /usr/weewx, on the uSD. However, I have in /usr/weewx two symlinks lrwxr-xr-x 1 gdt wheel 16 May 22 2020 public_html -> /tmp/public_html lrwxr-xr-x 1 gdt wheel 23 May 22 2020 public_metric_html -> /tmp/public_metric_html which means that while my software and my weewx database is on the uSD, my generated html pages are in /tmp which is a RAM-type fs. The html pages are then rsynced to another machine for web access. I also do backups every week. Perhaps should be more often of the database. Whether this is extending the life of my uSD card is a good question. But it was easy and avoids a lot of writes every 5m cycle. Certainly I do not need to retain the gnerated html and graph files. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/rmi5yoid555.fsf%40s1.lexort.com.
signature.asc
Description: PGP signature
