Hi Dave,

I don't believe I ever had my own SVN credentials on the server nor do we have a generic SVN. I could be wrong but I'm not sure we let scripts update SVN.

I think you might find that things like scripts are in SVN but not the data. So much of that data you are seeing as large isn't repo'd.

It might be better if we looked at specific dirs/issues 1 by 1 and decide case by case.

Regards,
KAM
On 5/12/2017 7:58 PM, Dave Jones wrote:
I need to know if I should put my own SVN creds on the server or if we have a generic SVN ID for automated updates from scripts in cron.

I was trying to have a central SVN area under /usr/local/spamassassin/svn since it's sooooo large. Do we need to have separate repos to keep things in smaller directories? I guess it depends on if we have general users like automc or bbmass that can commit to SVN in cron'd scripts.

Dave

On 05/10/2017 08:32 PM, Kevin A. McGrail wrote:
On 5/10/2017 8:49 PM, Dave Jones wrote:
Kevin,
I was wanting to setup /usr/local/spamassassin/svn as a check out area and a general update area. Do you normally set it up with your own creds or is there a generic user that was used on the previous server for cron jobs to do commits?

Looking at https://svn.apache.org/viewvc/spamassassin/dns/, it doesn't appear that the automated entries are stored in SVN.

Regards,

KAM


Reply via email to