BTW, is there any way to run [email protected] as my mastodon handle, but have the web interface be something like social.rx14.co.uk?

@Gargron

Sorry to ping you, but do you have any pointers on this? What i'd love is the handle [email protected], but still be able to run a blog or something else on rx14.co.uk, with the mastodon web interface being on a subdomain or rx14.co.uk/mastodon/.

Any pointers?

@RX14 Mastodon must be in the root path due to some special URLs that are important for discovery (/.well-known). You'll need a subdomain
@Gargron Are those special URLs contained in .well-known? If that's the case I could just proxy the endpoints in nginx.
@Gargron I could always set up a HTTP redirect rx14.co.uk -> blog.rx14.co.uk. That would probably be the easiest, though I like channelenges!
@RX14 @Gargron I want a similar thing, I was planning on proxying the endpoints mastodon needs to a subdomain. When I was looking at the api docs it looked like just sending everything under /api/v1 would work.
@RX14 @Gargron In theory you only need to proxy rx14.co.uk/api to Mastodon for the federation to work. You'd set `LOCAL_DOMAIN=rx14.co.uk` in your .env.production, but that may cause the web server to redirect you to rx14.co.uk/about when you visit social.rx14.co.uk. YMMV, testing is required (and you may need to modify the Mastodon code to support your use case).
@RX14 (and .well_known as @Gargron points out). It's probably going to be a PITA, let us know if you get somewhere with this.
@jdiez @Gargron In the interests of getting up and running quickly, I think i'll just do the quick nginx 404-redirect to blog.rx14.co.uk. I think that it's something i'd love to try out sooner or later though. Thanks for the pointers!