Nowadays SvarDOS is entirely kept within an svn tree: all documentation, packets, build scripts, internal projects, web site, etc.
It is hosted on a VPS "in the cloud". Works well and all, but one never knows if some cosmic ray won't flush the content of the hard disk in the datacenter. Or, more prosaically, if the hoster won't loose data because of a fire, like it was the case for OVH in March 2021.
It would be good to have some svn mirror somewhere else, that would replicate all project's commits through an automated svnsync. Sadly it is not possible to use a "forge" hoster like SourceForge or OSDN, because of the many non-OSI packages included within the SvarDOS repository.
As of today (rev 857), the svn repository takes 523 MiB.
Nowadays SvarDOS is entirely kept within an svn tree: all documentation, packets, build scripts, internal projects, web site, etc. It is hosted on a VPS "in the cloud". Works well and all, but one never knows if some cosmic ray won't flush the content of the hard disk in the datacenter. Or, more prosaically, if the hoster won't loose data because of a fire, like it was the case for OVH in March 2021.
It would be good to have some svn mirror somewhere else, that would replicate all project's commits through an automated svnsync. Sadly it is not possible to use a "forge" hoster like SourceForge or OSDN, because of the many non-OSI packages included within the SvarDOS repository.
As of today (rev 857), the svn repository takes 523 MiB.