mozilla-services / syncserver

Run-Your-Own Firefox Sync Server
Mozilla Public License 2.0
1.87k stars 145 forks source link

history keep period #286

Open mezoology opened 3 years ago

mezoology commented 3 years ago

Hello, and Excuse me if this is the wrong place to ask.

Is this self-hosted project have the same Firefox Cloud limits 👍

Synced tabs expire in 7 days. Synced history expires in 60 days. New history is only uploaded for the last 30 days.

and if so, is there any way to make it permanent.

Thanks in Advance.

jrconlin commented 3 years ago

This repo is just a wrapper for two other services. Tokenserver and Sync Server. It's absolutely possible to run both of these on their own, or go in to the code or settings and change them however you see fit.

Although, a word of caution: If you don't expire data, you're going to need a lot of disk space. Things will accumulate very quickly (even for a single user). Plus, some really don't make a lot of sense to retain. Once a tab or history is sync'd (for instance) it appears in both browser instances's history, so retaining that info doesn't really help anything, and since it's never referred to afterwards, it's just extra junk in your database. Plus, pages tend to "rot" faster than you expect.

jackyzy823 commented 2 years ago

Expired data in db will not be deleted unless manual operation. https://github.com/mozilla-services/server-syncstorage/blob/master/syncstorage/scripts/purgettl.py

If you want data not to expire. You can make a database schedule job like CREATE EVENT ON SCHEDULE in mysql to execute SQL like UPDATE sync.bso set ttl=2147483647.

New history is only uploaded for the last 30 days.

this is a client side behavior . server can do nothing to help.

Another point is that client side have download and upload size limit too. see https://searchfox.org/mozilla-central/source/services/sync/modules/constants.js#76