@prologic (#6wgtdyq) Ahh! I didn't even think of that problem. I was planning to. I did even have my feed copied over, but deleted it because I realised anyone following both would have doubled up posts. What's the best course here you reckon?
matched #3c4c43a score:11.53
Search by:
Search by 1 mentions:
@prologic (#6wgtdyq) Yeah agreed. ๐ Well I must admit that wasn't too difficult. Raspbian (or Raspberry Pi OS as they call it now...), even upgraded to _Bullseye_, only had golang 1.15, which doesn't have _embed_ which yarn needed, but once I pulled golang 1.17 from the Go site, no prob
matched #catnd5a score:11.53
Search by:
Search by 1 mentions:
@prologic (#6wgtdyq) Just realised I replied to you my hosted pod, which you can't see. Should be working now, if you try follow me on there.https://yarn.andrewjvpowell.com/user/eldersnake/twtxt.txt
matched #fibwfxq score:11.53
Search by:
Search by 1 mentions:
@eldersnake (#6wgtdyq) Ahh awesome! ๐ The _only_ problem of course is I can't follow a person by the same "nick" with two different feed sources ๐ So... Are you planning on migrating/moving your feed to your pod? I wonder if I should build a feature for this? ๐ค
matched #horgtzq score:11.53
Search by:
Search by 1 mentions:
(#6wgtdyq) `yarnd` itself has no builtin support for listening on a TLS port, I _coudl_ add it but it's not usually how I run things myself, I normally put a load balancer in front of things and terminate TLS there, it's far easier to manage.
matched #jukm2gq score:11.53
Search by:
Search by 1 tags:
@prologic (#6wgtdyq) All good, a quick NGINX reverse proxy did the job (that side of things is still new to me, but remarkably simple to configure it seems). In _theory_, it's working fine now.
matched #nxpn2wq score:11.53
Search by:
Search by 1 mentions: