I used to be able to use rsync to get copies of various repos and sites. This worked even after changing the site pages to foo.common-lisp.dev. However, my rsync urls are no longer working. (It's been several months and I'm not sure when it stopped working).
Can someone look into that? Or let me know what the right incantation of rsync would be to get the site pages?
Thanks,
I believe that is related with gitlab taking over project pages - they are no longer stored in the filesystem as individual files.
I think we should revert that and return to the old state, where the projects were served from filesystem trees - that was easier to understand, debug, and better performances wise (fewer internal indirections).
No idea how long that will be supported by gitlab, though...
On Sat, Nov 5, 2022 at 1:15 AM Philipp Marek philipp@marek.priv.at wrote:
I believe that is related with gitlab taking over project pages - they are no longer stored in the filesystem as individual files.
I think we should revert that and return to the old state, where the projects were served from filesystem trees - that was easier to understand, debug, and better performances wise (fewer internal indirections).
No idea how long that will be supported by gitlab, though...
I don't want to go down that path if gitlab could remove this ability in the future.
That raises the question on how people backup their repos? I started rsync'ing many years ago when c-l.net had some kind of failure back when c-l.net didn't provide any backups for users. So I still want to be able to do some kind of backup, just in case.
At least for the gitlab pages on common-lisp.dev, I can get the artifacts from a build. I can grab those or maybe have gitlab CI automatically copy the files to some host. (Have to figure out how to do that, though.)
On Sat, Nov 5, 2022 at 2:35 PM Raymond Toy toy.raymond@gmail.com wrote:
On Sat, Nov 5, 2022 at 1:15 AM Philipp Marek philipp@marek.priv.at wrote:
I believe that is related with gitlab taking over project pages - they are no longer stored in the filesystem as individual files.
I think we should revert that and return to the old state, where the projects were served from filesystem trees - that was easier to understand, debug, and better performances wise (fewer internal indirections).
No idea how long that will be supported by gitlab, though...
I don't want to go down that path if gitlab could remove this ability in the future.
Since I have a directory /project/cmucl that I can use with rsync, I'm wondering if I could get my site CI to copy all of the site files to some place in /project/cmucl.
I know gitlab CI can do some kind of deploy, but I'm not sure what directories are reachable from CI or how to set up CI to be able to copy the files.
A friend has already set up a script to pull the build archive from the latest pipeline to get the site pages, so it's not necessary to have this.
-
Philipp Marek -
Raymond Toy