I have about 10 years of data on my RPi4 and all the data is about 1.7gb, 
I'm using a 1 minute archive interval (total used on the card is about 
6.4gb). I use mysql and it might be different with sqllite as there is a 
lot less overhead. Good SD cards are cheap now and there are other storage 
options as well. I stay after the replication logs however.

I was sftping the pages to an external web hosting site every 5 minutes. 
But installed Apache2 on the pi to serve it instead. Then used dynDNS on 
the router, no-ip.com type. Created a subdomain http://weather.duanek.name 
at my domain provider to redirect that url to the dynDNS and now serve it 
off the pi. My ISP blocks port 80 so I just used port 8888 and set my 
router to forward that port to port 80 on the pi.

I really only have neighbors looking at this. So this results in less 
traffic even though the traffic from the sftp'ed pages was trivial.

On Sunday, October 4, 2020 at 8:28:03 PM UTC-4 [email protected] 
wrote:

> Ok, Thanks!
>
> On Sunday, October 4, 2020 at 8:15:27 PM UTC-4 vince wrote:
>
>> On Sunday, October 4, 2020 at 5:09:39 PM UTC-7, Luke Marcum wrote:
>>>
>>> I've finally got Weewx working on my Pi FTPing to my website how I want. 
>>>  I was just wondering if weewx takes up a lot of storage on my PI and what 
>>> I can do to backup and store this data differently so my Pi doesn't run out 
>>> of space!
>>
>>
>> I have 12 years of data and it's under 400 MB for my archive directory, 
>> so filling up your disk is about the last thing you need to worry about.
>>
>> You definitely want to back up your archive directory to keep all your 
>> data.  There are 'many' threads here for how to do that.   Do a little 
>> searching in the group archive. 
>>
>

-- 
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/94c41083-2b35-4a5f-a19c-ea267e001a1en%40googlegroups.com.

Reply via email to