alwayssitting

joined 2 weeks ago
[–] [email protected] 18 points 11 hours ago

Previous Gitea user and now Forgejo, and yeah it's a great git server. Simple, lightweight but still very capable.

[–] [email protected] 2 points 1 day ago

Manyfold is great for this usecase.

[–] [email protected] 1 points 3 days ago

Yeah that would be the best way to solve this problem.

[–] [email protected] 2 points 5 days ago* (last edited 5 days ago) (1 children)

Well you keep saying monitor a domain, in that case a DNS monitor would make more sense than HTTP(s) since that's for monitoring a service. That's why I was a bit confused. But yeah try to enable the ignore SSL option and see if that changes anything. You didn't include a screenshot of the settings which makes a bit difficult to diagnose the problem so I will leave it here.

[–] [email protected] 1 points 5 days ago* (last edited 5 days ago) (3 children)

Which one of those. You pick one when adding something new to monitor. Actually just send a screenshot of the uptime-kuma settings of one of the services that are giving you problems.

[–] [email protected] 1 points 5 days ago (5 children)

Sorry I'm a bit confused. What kind of tracker are you using in uptime-kuma and what address is it pointing to?

[–] [email protected] 1 points 5 days ago (13 children)

If you ping the domain from inside the container, does it succeed?

[–] [email protected] 3 points 1 week ago* (last edited 1 week ago)

It's extremely simple. Although I prefer ZFS I will give you an example with BTRFS since it's easier to get going. RAID1 in BTRFS is considered stable (RAID5/6 is not).

sudo mkfs.btrfs -m raid1 -d raid1 /dev/sdx /dev/sdy # Create raid array with BTRFS
sudo mkdir /mnt/storage # Create your mount directory
echo "/dev/sdx /mnt/storage btrfs noatime,compress=zstd 0 0" | sudo tee -a /etc/fstab # Set raid array to mount at boot
sudo mount -t btrfs -o noatime,compress=zstd /dev/sdx /mnt/storage # Manually mount the first time

You would also probably wanna set up a btrfs scrub once per month, either with systemd-timers or cron, whatever you prefer.

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago) (1 children)

If OP can find a V3 KE for a decent price then you get filament runout sensor and network connectivity, among with some other nice stuff. And for the failed print detection you can add a Nebula camera which isn't too expensive if you order it from Aliexpress. It also supports rooting so you can add some really nice stuff to it, like Mainsail. I have a KE and I'm pretty happy with it since I got it for a really good price. I don't think I would recommend it at full retail price though.

[–] [email protected] 6 points 1 week ago

It will yeah, although with modern SSDs it really isn't a big problem. I've used an Samsung 840 EVO as L2ARC for 8 years now.

[–] [email protected] 2 points 1 week ago

Try running a flow rate calibration in Orca slicer and adjust settings accordingly

view more: next ›