Users who have successfully gotten a Lemmy instance setup, you may want to consider helping update the installation documentation if you're able to
Quite a few people have had issues trying to get a Lemmy instance setup, and in a lot of cases it seems to be an issue with the documentation missing something or not being super clear (not blaming the devs btw, they have a LOT on their plate these days).
With the influx of users that are going to be coming to Lemmy over the next while, being able to get new instances setup is going to be critical, so anything that could improve the installation documentation, the Docker and Ansible examples, etc., which in turn will also reduce the number of installation support requests the Lemmy devs get, would be a huge help.
If I can eventually get it to work, I'll be hosting my personal Lemmy instance on a Hetzner CX21 VPS (2 CPU, 4GB RAM). Unfortunately after about a dozen attempts, with many variables tweaked to try to narrow down the issue, I still get nothing but a spinning button when I try to login after installation. I find it so odd that some people have no problem getting it up-and-running, and it simply won't work for others.
I gave up on setting up my own instance today for these exact reasons. Brand new install, multiple browsers, no matter the username, no matter the length of the password, all I get is a spinning circle when I try to login with my brand new admin account. No response whatsoever from the forgot password link either.
I absolutely would have if things were handled differently, but at this point my only goal is to see spez get his ass fired.
I've already investigated using a subdomain, and it may have to be the way I go for now, but it's not really ideal. @[email protected] is much nicer and easier to remember and give out than @[email protected] or @[email protected].
Plus I'm (hopefully) foreseeing a future of running multiple federated apps that allow delegation, so if I wanted to have a Lemmy instance, a Matrix instance, and a Mastadon instance, if they all eventually allow delegation I can give everyone @[email protected] for literally any of my federated services, instead of @[email protected], @[email protected], etc.
Allow delegation of a Lemmy instance to a different URL?
Is it possible, or will it be possible eventually, to delegate your Lemmy instance to a different URL?
For example, if I wanted to setup my own self-hosted instance at example.com, so that my username would be @[email protected], would it then be possible to host the actual Lemmy installation at example.com/lemmy/, leaving the main domain example.com available for me to host whatever I want?
I would love to setup my own instance with a nice short domain, instead of something like @[email protected], but without being able to delegate you essentially have to sacrifice the whole domain to the Lemmy installation, which is something I don't really want to do with a short domain.
What came to mind is OpenID, where using the example above, you could use example.com to sign-in to any site that supported OpenID, and then on example.com you would have a link to the actual OpenID provider in the code somewhere, and everything just worked.
After searching the first time, wait a few minutes and search again, it will probably show up. I had the same issue yesterday and apparently you need to do this the first time a remote community is accessed from a local instance.
Ah, it seems as though my issue is indeed an existing username and a lack of error message.
There seems to be an issue with the signup process on lemmy.ca. I've been trying to signup for a while today but the Sign Up button just keeps spinning when I click it. I've tried numerous things to try to fix it and nothing seems to work. Signed up on a different server so I could report the issue.