Thanks to @SeaGL for the opportunity to present and thanks to @TheyOfHIShirts for the nice recap. Here's the video from today: https://content.haacksnetworking.org/w/nsMwnJhLnfMrs17W5cAdWg #sysadmin #selfhost #selfhosting #gnulinux #linux #freesoftware #floss #opensource 🙏🏼
Thanks to @SeaGL for the opportunity to present and thanks to @TheyOfHIShirts for the nice recap. Here's the video from today: https://content.haacksnetworking.org/w/nsMwnJhLnfMrs17W5cAdWg #sysadmin #selfhost #selfhosting #gnulinux #linux #freesoftware #floss #opensource 🙏🏼
Today I discovered iCloud downloader - a CLI tool that can sync photos from iCloud to a local folder: https://github.com/icloud-photos-downloader/icloud_photos_downloader
I’m now willing to set up #Immich and duplicate my photos there to know it better and see if it fits my needs.
#HomeLab #SelfHost #SelfHosted#SelfHosting #iCloud
Today I discovered iCloud downloader - a CLI tool that can sync photos from iCloud to a local folder: https://github.com/icloud-photos-downloader/icloud_photos_downloader
I’m now willing to set up #Immich and duplicate my photos there to know it better and see if it fits my needs.
#HomeLab #SelfHost #SelfHosted#SelfHosting #iCloud
Hello fediverse!
I'm a small yet powerful git forge. Download one binary, launch it and you have a forge that can :
- create git repositories
- manage who can access to what repositories
Nothing more, nothing less.
Install plugins and you will be able to:
- create issues, roadmap, sprint, milestone…
- represent them in boards
- review/merge branches (called grafts in gitroot)
- represent them all and many more in a web interface
I am young, very young (version 0.3.0) but i will grow, especially if you help me. Follow me to keep in touch.
#introduction #git #SelfHost #foss
Why gitroot is different? Why the need to build another forge? Just 2 concepts I have not found in all other forges:
- no database + no api == no vendor locking, your data is just aside your code. By data I mean: users, branches rights but also issues, boards and pipelines... Clone your repo all your data is on your computer, mirror to another forge (preferably @Codeberg 😍) and you have a backup.
- simple at start, grow only if needed == plugin based, you want to do a simple static blog: use only apex plugin. You want a full forge install ladybug, silo, grafter, pollen plugins and many more. Don't waste your server resources with unused features.
This 2 concepts drive the code every day. It's not simple (to code) but at the end of every day I'm happy with a simple (to use) forge.
This 2 concepts permit to do more with less and that is exactly what I want for my forge.
Something not clear here or in https://gitroot.dev please ask here, in DM, at contact@gitroot.dev, or in issues and I will try to explain.
Edit: added missing hashtags
#git #forge #selfhost #foss
so, some random thoughts on #selfhosting decisions I've made as a technically-homeless semi-nomadic digital serf:
it would benefit me to be "dogfooding" Nextcloud more than I do, because my partner in Wordpress crime and I are learning it in order to be able to sell services installing & maintaining it for people who don't want to use MS365 or G Suite.
I do use Nextcloud for purposes related to our business together, but I don't yet have a personal install.
for calendar, todo, and contacts I use an install of Baikal on a penny webhost, with aCalendar and Tasks.org on my Android device (a desktop frontend is an unsolved problem)
for notes & documentation, I use Tiddlywiki
for file sync, I use Syncthing.
Nextcloud could do all of this in one fell swoop, so why don't I use that instead?
the answer, in short, has to do with *resilience* - specifically in the context of life instability which leads to an occasional inability to pay bills.
now one could observe that I have my own servers, and can and do host a bunch of stuff reverse-proxied thru a $1/mo VPS. so why not #selfhost Nextcloud that way?
well... I do. that's how I host our business Nextcloud, which we use for file sync, wiki documentation, and maybe kanban in the future.
but that isn't the right choice for my personal setup.
when it comes to calendar+todo+contacts, wiki for note keeping, and personal file sync - I need these services to remain viable for as long as possible even if life renders me incapacitated for months. these are core services. they must work properly and be available, or I have got big problems. my limitations in my current life situation are cognitive, and if I lose access to those services, I might not be able to come back from it.
Decentralisation is the biggest enemy of authoritarianism. So #SelfHost. Buy solar and batteries. Heat pumps. Get an electric car. Electric bicycles. Use #OpenSource and #FreeSoftware. Store your data at home. Get a Canon Selphy to print the pictures you take. Buy books. Vinyl or CDs. Join your local library. Do. Don’t discuss. And help your neighbours to do the same things. Sharing is caring. Avoid getting lost in discussions about what’s best. Do. Fail. Share. Learn. Repeat. 1/4
AWS was down — I didn't notice because I #Selfhost
Azure is down — I didn't notice because I #Selfhost
When my #Selfhost stuff is down, YOU will not notice, because I'm just a very small part of the enormous internet ;)
(I did manage to "buy" a new domain name, make the correct DNS entries and put a landing page on it, have working email with DMARC/DKIM/SPF etc in less than 20 minutes today — https://fedihouse.eu ;)
AWS was down — I didn't notice because I #Selfhost
Azure is down — I didn't notice because I #Selfhost
When my #Selfhost stuff is down, YOU will not notice, because I'm just a very small part of the enormous internet ;)
(I did manage to "buy" a new domain name, make the correct DNS entries and put a landing page on it, have working email with DMARC/DKIM/SPF etc in less than 20 minutes today — https://fedihouse.eu ;)
The case (Fractal Design Define R5) is here..time to load up the drives ... #NAS #HomeLab #selfhosting #selfhosted #selfhost
The case (Fractal Design Define R5) is here..time to load up the drives ... #NAS #HomeLab #selfhosting #selfhosted #selfhost
Any #ZFS folks want to offer me an opinion on the following? I have 2 ZFS pool of raidz2 with 7 2TB SAS drives each (about 11.5T). I want to add a LOG drive. I have a single SAS SSD that's 300G. When I suggested using a 1TB LOG drive earlier, someone said that was way too much. (which is why I picked up a used 300G SSD)
My question is whether it makes sense (is possible) to partition that drive into 2 partitions and have one pool use 1 partition as a log drive (e.g., 150G) and the other pool use the other partition as a log drive on the same physical device.
Is this going to be worse because it's just too much IO on one device? Is it reasonable? Any other ideas?
Why gitroot is different? Why the need to build another forge? Just 2 concepts I have not found in all other forges:
- no database + no api == no vendor locking, your data is just aside your code. By data I mean: users, branches rights but also issues, boards and pipelines... Clone your repo all your data is on your computer, mirror to another forge (preferably @Codeberg 😍) and you have a backup.
- simple at start, grow only if needed == plugin based, you want to do a simple static blog: use only apex plugin. You want a full forge install ladybug, silo, grafter, pollen plugins and many more. Don't waste your server resources with unused features.
This 2 concepts drive the code every day. It's not simple (to code) but at the end of every day I'm happy with a simple (to use) forge.
This 2 concepts permit to do more with less and that is exactly what I want for my forge.
Something not clear here or in https://gitroot.dev please ask here, in DM, at contact@gitroot.dev, or in issues and I will try to explain.
Edit: added missing hashtags
#git #forge #selfhost #foss
Mattermost deciding to go full corporate removes yet another option for #selfhost chat.
I’m so tired.