Ok mastodon instance admins, I've hit another snag, in the nginx config, there's a @proxy section with the line:
proxy_pass http://[::1]:3000;
(note, I'm running on ipv6)
Anyway, there's nothing listening on port 3000 when I do a `netstat -an | grep LIST`
What is it for, and why doesn't nginx listen on that port ?
Hmmm, yes, both the web and sidekiq services won't start, logs say:
/home/mastodon/.rbenv/versions/2.4.1/lib/ruby/2.4.0/rubygems/dependency.rb:308:in `to_specs': Could not find 'bundler' (>= 0) among 13 total gem(s) (Gem::MissingSpecError)
So it looks like my gem path might be toast or somesuch.
Ok, manual testing shows that rails is firing up on IPv4 localhost (127.0.0.1:3000), but of course, I'm accessing my instance via IPv6, so nginx dutifully forwards the request to [::1]:3000 which is also localhost, but doesn't go anywhere as rails isn't bound to that. Gah!
Now to work out how to make rails bind to [::1] instead of 127.0.0.1
.@dadegroot I'm hanging on your lips while you're doing this on a Raspi, but I recall having read that #Mastodon is going to be very unhappy with anything less an 1.5GB RAM.. I'll shut up now and let you continue. #goodLuck
@jpmens Almost there, it now runs and accepts my request for registration. Have to check my mail server config to make sure it's not bouncing/eating that.
@jpmens @dadegroot it runs fine on 1G of ram. I got to 1.5G when I had 400 users, and I'm at ~2G now with >750 users. The latest update apparently has a few perf improvements too :)