Baby pineapple! How long did that take to sprout? I don't know if I can grow them in 8a, but I might give it a shot.
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
Nice! I did the same, but I did it on my resin printer so the full 1:1 wouldn't fit. I ended up doing a 1/4th scale...I call him mini me 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.
True, in that case CF tunnels may be easier to manage due to fewer moving parts to configure. Good point!
Cloudflare tunnels are great but OP may not want to have to authenticate each user to their services.
Cloudflare free tier + a reverse proxy will set you straight. You can add subdomains for your services as A records in Cloudflare off of your root domain, i.e. lemmy.yourdomain.tld, personalsite.yourdomain.tld, images.yourdomain.tld.
When doing this, enable the Cloudflare DNS proxy which will route DNS requests to your origin service through Cloudflares's CDN. This essentially "hides" your public IP as anyone doing a nslookup lemmy.yourdomain.tld will get Cloudflares's IPs back as a response.
Once you've done this, you can break everything back out to it's respective backend via a reverse proxy. For example, lemmy.yourdomain.tld gets passed to 192.168.0.10, personalsite.yourdomain.tld gets passed to 192.168.0.20, etc.
I like it so far. The web interface is pretty solid and Jerboa is serviceable, though missing some features that I would call crucial to the experience. I can't fault the developers at all though, as it's like two dude to my knowledge. The reddit API thing convinced me to run my own instance for friends.
I'm hopeful lemmy takes off and sees a larger adoption as well, I think that putting the internet back in the hands of individuals is super important as there has been way too much aggregation of services for like the past decade IMO.
Same. Projects like Lemmy are pretty slick, I just hope that the perceived barrier to entry due to the decentralized nature of the Fediverse won't keep people from joining. There needs to be a "critical mass" of users to make a platform successful and engaging. Hopefully that happens to Lemmy due to the Reddit API fiasco.
One of the best camping experiences I've had was when we took our bicycles to a state park.
To be fair, we drove there because it was about 4 hours away from us, but we thoroughly enjoyed the multi-use trail available at the park. It was so much fun with plenty of hills and wildlife to get the blood pumping.
I definitely want to go back and explore bike camping (or motor-bike camping) further.
Great photo, and I'd love to hear more about your adventure!