Open dr0i opened 4 weeks ago
And it was used (just?) for twitter, which we don't need use anymore.
Another original idea for this was to back up content that is only in GitHub and not part of the Git repository, in particular Metafacture issues, see https://github.com/metafacture/metafacture-documentation/issues/1.
Since it's no longer running and we have a different approach for the Metafacture documentation, I'd be OK with archiving it, though I still think it would be a nice way to address the issue of having a lot of our content in GitHub only.
There is no instance running of this AFAIK.
I wonder why and when we decided to shut down this service. Backup issues from Github is still a justifiable use case, isn't it?
Btw, there are still directives in our apache vhost config pointing to lobid.org/events.
I've started it manually now and re-added it to monit.
There is only sparse documentation here and I couldn't find adhoc where the data resides. Folder public/data
on both server are empty.
[edit: There is events/target/universal/stage/logs/application.log
being > 1 GB in size. But that directory has more tmeporary character - a "clean" build will delete these logs. These logs show that the program started to work at 2023-06-05. ]
So is this working at all?
So is this working at all?
Probably not, my guess would be that after 9 years, we'd probably have to update it to work with the GitHub API. Looking at the log (tail target/universal/stage/logs/application.log
), it seem it was still triggered somehow a year ago: Wrote backup to: /home/sol/git/events/target/universal/stage/backup-metafacture.json
, but that file is empty ([]
).
OK then, I will stop it again and comment it out. This saves some resources.
curl https://api.github.com/repos/metafacture/metafacture-core/issues
still works.
However, i'm ok with archiving this repo, too.
There is no instance running of this AFAIK. And it was used (just?) for twitter, which we don't need use anymore.
If so, can we archive this repo and close it?