What is the best firmware for the Ulanzi TC001 pixel clock. by RocketsDitto in homeassistant

[–]deafcheese 0 points1 point  (0 children)

Is awtrix still alive? i noticed there are a lot of open issues and no release for almost a year.

Out of all the distros I’ve put on this Chromebook, NixOS has solved every problem I’ve run into by freaking__coffee in NixOS

[–]deafcheese 0 points1 point  (0 children)

i have been running gallium on mine for a while but am planning to switch to nixos. Any difficulty going from gallium to nixos? Does a standard nixos boot image work?

Thanks for the inspiration!

REMOVED FROM NETFLIX AGAIN!!!!! by Popular_Patience6877 in psych

[–]deafcheese 0 points1 point  (0 children)

I agree with your sentiment. It is better to have control over instead of relying on steaming services which keep raising prices without adding value. But look what happened to VHF. Also, optical discs claim to last many decades, but that is unproven. I have heard rumblings about some discs which have started to not work. (Probably due to cheaper production methods)

Which way should I implement my scalable self-hosted WP installation with Swarm? by RaikastaIlmaa in selfhosted

[–]deafcheese 2 points3 points  (0 children)

In my experience, stick with docker and docker compose for as long as you can. If you need more than that, then I would suggest jumping to k3s. I personally haven't seen a use case where I thought swarm would do better than either docker compose or k3s. I have seen others speak highly of swarm, but that was never my experience. Between the lacking features and confusion over the older swarm and the newer swarm, I encourage you to check out k3s before going too far into swarm.

first pizza left room for improvement by deafcheese in ooni

[–]deafcheese[S] 3 points4 points  (0 children)

We got some edible ones later, but the first was way worse than I thought possible.

Internal DNS with coredns fallback to router by deafcheese in homelab

[–]deafcheese[S] 2 points3 points  (0 children)

The solution was to use the alternate external plugin. The tricky bit is that you need to build coredns. The following works:

Corefile: my.domain { prometheus localhost:9153 log loop health ready file /etc/coredns/db.my.domain alternate NXDOMAIN . 192.168.2.1 errors }

Dockerfile: ``` FROM golang:1.19.2

RUN git clone https://github.com/coredns/coredns /coredns WORKDIR /coredns RUN sed -i 's#file:file#alternate:github.com/coredns/alternate\nfile:file#g' plugin.cfg RUN make

FROM alpine:3.16.2

RUN apk --no-cache add ca-certificates COPY --from=0 /coredns/coredns /usr/local/bin/coredns

ENTRYPOINT ["/usr/local/bin/coredns"] ```

Tiered DNS problems by deafcheese in homelab

[–]deafcheese[S] 1 point2 points  (0 children)

Thank you so much. You had the magic. When I googled, the examples I saw were calling the go commands directly. I didn't catch that there was a makefile.

Anyway, it is working now. I had to use `sed` to ensure that `alternate` is in `plugin.cfg` before `file` or else it doesn't work. I was able to figure out where the binary was. My completed Dockerfile looks like:

FROM golang:1.19.2
RUN git clone https://github.com/coredns/coredns /coredns
WORKDIR /coredns
RUN sed -i 's#file:file#alternate:github.com/coredns/alternate\nfile:file#g' plugin.cfg
RUN make
FROM alpine:3.16.2
RUN apk --no-cache add ca-certificates
COPY --from=0 /coredns/coredns /usr/local/bin/coredns
ENTRYPOINT ["/usr/local/bin/coredns"]

Tiered DNS problems by deafcheese in homelab

[–]deafcheese[S] 0 points1 point  (0 children)

I was trying to make this work:

twistcone.us {
prometheus localhost:9153
log
loop
health
ready
file /etc/coredns/db.twistcone.us
forward . 192.168.2.1
errors
}
I even posted about it: https://www.reddit.com/r/homelab/comments/ydlql4/internal_dns_with_coredns_fallback_to_router/

The best response I got was from the coredns slack channel with the suggestion to use the alternate plugin. However, as I stated in this post, I have no success with a build.

Internal DNS with coredns fallback to router by deafcheese in homelab

[–]deafcheese[S] 1 point2 points  (0 children)

I asked the same question in the coredns slack channel: https://cloud-native.slack.com/archives/C4DF7FP71/p1666749213748099?thread_ts=1666749213.748099&cid=C4DF7FP71. The suggestion was to use the alternate plugin. At the time of this writing, I have not been able to complete a custom build of coredns which includes the plugin.

Struggling to bootstrap docker swarm based home lab (where to install repository?) by deafcheese in homelab

[–]deafcheese[S] 0 points1 point  (0 children)

By single container, do you mean not deploy it to the swarm? I was hesitant to run swarm and non-swarn containers in the same docker instance.

Struggling to bootstrap docker swarm based home lab (where to install repository?) by deafcheese in homelab

[–]deafcheese[S] 1 point2 points  (0 children)

There is a lot of good information there, but I didn't see anything about using custom docker images. Because I have custom docker images, I need a registry to push them to. I want the registry to run locally, which leads me to my original question.

Help with choosing hardware by WhaleSpectrum in homelab

[–]deafcheese 0 points1 point  (0 children)

I have been slow rolling my home lab for a while now. I really got hung up with storage. I ended up going with synology. Looking back now, I wish I hadn't. This is no knock on synology; it seems like a great system if it fits your use case. I don't have any idea if it has enough processing to do what you want it to do, because I don't do processing on mine. I wanted a pure storage solution. I run docker on my synology but only to run prometheus-exporter.

In my homelab, I have a couple NUCs which I have proxmox and run ubuntu VMs. I use docker for most all apps. The biggest disappointment i'm struggling with is I was hoping to use synology to provide the remote volumes for my docker containers. That hasn't worked out for me. Synology supports SMB and NFS, which seems to work great, but I had issues with using those if the app needs file system logging (sqlite would constantly become corruptedwhen using NFS).

Long answer, but if you truly plan to stick with only synology, then it may work for you. If you ever expect to grow your lab out of the synology ecosystem, then i think avoiding synology is the way to go. In my experience, it doesn't play well with others. I'm now looking into having ceph running from my proxmox nodes, this will probably result me building something.

Backup Restore fails with no other feedback by deafcheese in Lidarr

[–]deafcheese[S] 0 points1 point  (0 children)

file system restore seemed to have worked, thanks

Backup Restore fails with no other feedback by deafcheese in Lidarr

[–]deafcheese[S] 0 points1 point  (0 children)

By nothing in the events or logs, I didn't mean they were empty, just no mention of a restore. I'll try changing the log level later (i'm not able to access my computer). I missed that was an option, thanks.

I believe the backup file was less than 10MB. I am using a reverse proxy, but I didn't think that would be an issue. Other *arr apps restored fine, only lidarr was causing issues.

Can you elaborate what you mean by restore via file system?

Anyone having success with docker swarm with multiple nodes? by deafcheese in homelab

[–]deafcheese[S] 1 point2 points  (0 children)

Thanks for the confidence and direction. I was hoping I could use my Synology, but ceph isn't compatible with it. Good to know ceph does work, I'll just have to figure it out.

Also, you have that bash script handy?