Crashing and burning (in a non-production environment) is an excellent motivator to develop necessary skills; being unafraid to break things and fix them when they inevitably break helps you get a deeper understanding of how the systems work, for what it’s worth.
I think this may more for acute vertigo, but have you tried the Epley maneuver?
This appears to be a variation of the “standwich.” Please see the attached for an example.
I loved that book growing up and was so excited when the movie was coming out (on my birthday!)
To this day, that movie is the only one I legitimately walked out of. It was such a terrible adaptation.
Running an RKE cluster as VMs on my ceph+proxmox cluster. Using Rook and external ceph as my storage backend and loving it. I haven’t fully migrated all of my services, but thus far it’s working well enough for me!
I want to try and create discussion about videos that may be less main stream. Video (specifically medium- to long-form) is my preferred type of content to consume, however I don’t have the ability to create my own content. !Videos@lemmy.world is great but as @kersploosh@sh.itjust.works mentioned below:
Posts that invite comments tend to get comments.
!Videos@lemmy.world doesn’t directly ask for discussion on the videos posted. I created a community, !whatareyouwatching@lemmy.onlylans.io, to try to bridge this gap. The idea is that you find an interesting video, you watch it, and then you post it with your main take-away or a question you had to try and foster a discussion.
Not sure if it is working, but that’s my own methodology to trying to increase engagement with content that I don’t personally produce.
Also, I am running a small self-hosted instance for friends, so my name may not be as “out there” as the larger instances, but I’m pretty sure that anyone can post to this community.
This video is a must watch for explaining the fundamental problems of crypto/NFTs.
Warning: it long, like feature movie long, but really informative.
Yeah, the whole article feels like it is both pandering and condescending at the same time. No thanks lol.
This article is so cringey.
Fajitas or Mexican food in general. So flavorful and just hits a certain way.
Hello fellow domain hoarder 🤣
Hello from onlylans.io
Absolutely. As much as I loved Reddit, I always felt drowned out due to the large user base and was hesitant to share my opinion. Thanks to Lemmy and its (currently) smaller communities, I feel like my voice has wider reach or, at the very least, less aggressive competition.
I’ve used the PWA, Jerboa, Liftoff, and Connect.
Jerboa is probably my favorite of the bunch. I prefer how compact everything is and the 0.0.33 version was working well. I upgraded to 0.0.36 and performance took a bit of a hit so I figured I would explore alternatives. Also when I looked at other options 2FA support had not been added (it’s working as of this post)
The PWA is more than functional,and I like it quite a bit. Don’t like that backing out of a post navigates to the top of the page though.
Connect is good too, just personally not a fan of the larger interface, even in list/compact mode.
Currently using liftoff. Performance is good, 2FA support is available, and in list/compact mode it’s tolerable. I still do prefer the compactness of Jerboa though.
We use wiki.js at work and it is great. A nice benefit is you can track your articles in a git repository for granular change tracking.
Oh weird, that sucks lol
I actually setup SES for my Lemmy instance. I was evaluating SendGrid but less than 24 hours after signing up they closed my account with zero explanation so…yeah lol.
I was sandboxed in SES initially but I created a support ticket asking for production access and I was good to go. No issues with SES thus far.
Cloudflare tunnels or a reverse proxy with Cloudflare DNS would be much easier to manage IMO. What you’re doing will work but it seems like you have a lot of moving parts in your setup which can lead to errors creeping in.
With both proposed setups you should be able to pass non web-based traffic to their respective backends. In nginx that would look something like the following:
server {
listen 443 ssl http2;
server_name service.yoursite.tld;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host:$proxy_port;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://<IP of your service>:<port>;
}
}
With Cloudflare tunnels you can setup a VM as your tunnel termination point and configure ingress rules to pass traffic where it needs to go, similar to this:
tunnel: <Tunnel UUID>
credentials-file: /root/.cloudflared/<Tunnel credentials>.json
ingress:
- hostname: service1.yourdomain.tld
service: http://192.168.0.10:80
- hostname: service2.yourdomain.tld
service: ssh://192.168.0.20:22
- service: http_status:404 # This is a catch-all rule to handle unmatched ingress traffic
One thing you can do for your public IP is use something like inadyn to update cloudflare with your public IP when it changes. Inadyn is super lightweight and will make sure, +/- 5 minutes, that your public IP is up-to-date with Cloudflare.
Check out Mealie