

My repo is fine, because its not online. Keeping them online is just silly.
My repo is fine, because its not online. Keeping them online is just silly.
What is openwebzine? Can’t find any info on it.
256gb of ram seems well beyond standard self-hosting, what are you planning on running?!
I did create a fork and MR, and neither used your runner (sorry if that is what spooked you).
Develop local and push remote also let’s you sanitize what is public and what isnt. Keep your half-backed personal projects local, push the good stuff to github for job opportunities.
I think it was when you create a merge request back, that the original repo would then run the forked branch on the original runners.
From what I can tell, its now been much more locked down, so its better, but still worth being careful about.
More discussion: https://www.reddit.com/r/github/comments/1eslk2d/forks_and_selfhosted_action_runners/
The other potential risk is that the github action author maliciously modifies their code in a later version, but that is solved with version pinning the actions.
I can’t find it right now, but there used to be a warning about not self-hosting runners for public repos. Anyone could fork your repo, and the fork would inherit your runners, and then they could change the pipeline to RCE on your runner.
Has that been fixed?
I went to a completely private gitlab instead, with mirroring up to github for anything that needed to be public.
Edit: seems to maybe not be an issue anymore, at the very least it doesn’t seem to affect that repo. Still, for anyone else, make sure forks and MRs can’t cause action to run automatically on your runner, because that would be very bad.
This is my personal opinion, but you should add :
Unless there is a really good reason, don’t rename your project. It only adds confusion, and users will get lost during the transition. It also makes them hesitant to try the new one - “What if they do it again and i get left behind”.
Pihole isnt pi specific either, it still kept the name.
It could be that the process forked and crashed, which is why you got the notification, but that it kept working. It might also be a delayed notification?
I saw something similar happen on my partners Ubuntu with Zoom “crashing” multiple times while working. Didn’t dig to the bottom of it, the notifications eventually stopped after some reboots.
Are you running zfs on multiple slow spinning disks? Might just be that they are taking too long to spin up?
The kernel boot time is very slow, that is probably worth investigating first, but I dont have any theories there :(
For a similar tool for windows, there is: https://www.grc.com/wizmo/wizmo.htm
And make your chisel blunt and chipped? You monster
Remove the HDMI port with pliers :D
Container overhead is near zero. They are not virtualized or anything like that, they are just processes on your host system that are isolated. Its functionally not much more different to chroot.
Its networking is a bit hard to tweak, but I also dont find I need to most of the time. And when I do, its usually just setting the network to host and calling it done.
Are you using docker compose scripts? Backup should be easy, you have your compose scripts to configure the containers, then the scripts can easily be commited somewhere or backed up.
Data should be volume mounted into the container, and then the host disk can be backed up.
The only app that I’ve had to fight docker on is Seafile, and even that works quite well now.
There are android clients, probably one for iOS as well. If you are getting OOM killed, you need to work out what is using all your memory. The OOM killer is pretty indiscriminate, and will murder processes randomly.
Maybe keep system monitor up and keep an eye on memory usage?
Can you enable SSH, and then try SSH into the box once it hangs?
Any OOMKiller messages in dmesg/journalctl? Do you have swap space?
Nothing in the logs jumped out at me, hopefully someone else can help you.
Looks like you need to use [
on friendica? ]
~~Take a photo of the output? First few lines are most important, but ideally all would be good. ~~
Edit: actually, dont want to crowd the kitchen, good luck!
Same. Super easy to do, easy to mirror repos, easy to keep offline…