Good start to the long weekend, had a choc-caramel hot cross bun with maple syrup & a coffee for breakfast, while installing mastodon on a raspberry pi (not for serious use, just a handy computer to test things out on).

Later I need to grocery shop, since we totally forgot to do so on the way home yesterday.

Hmmm, whole process was going swimmingly until the part where you install ruby 2.4.1 with rbenv. Here's where the Pi's performance really shows it doesn't really have what it takes.
Right, that bit is done (approx 15 mins later). On to the next bit. #mastodon #instance #raspberrypi

Ah, that's a snag (why is it trying to install to /var/lib/gems):

mastodon@pi3:~/live$ gem install bundler
Fetching: bundler-1.14.6.gem (100%)
ERROR: While executing gem ... (Errno::EACCES)
Permission denied @ dir_s_mkdir - /var/lib/gems

Progress made.

When installing the bundle gem, you need to edit the #! line to reflect the rbenv enabled ruby instance.

Next problem, uncaught exception in node-gyp:

gyp ERR! node-gyp -v v3.4.0
gyp ERR! This is a bug in `node-gyp`.
gyp ERR! Try to update node-gyp and file an Issue if it does not help:
gyp ERR! <https://github.com/nodejs/node-gyp/issues>
Build failed with error code: 7

Resolved that issue with an: npm update node-gyp

and then re-running the yarn install.

Seem to now have most of the mastodon setup complete.

Current challenge is trying to get the letsencrypt client to give me a cert on an ipv6 only domain, without first having a working https server on the host (nginx obviously can't start in ssl mode without a cert, I can't get a cert 'cause letsencrypt wants to connect to the https server).

Fixed my issues with letsencrypt, now have valid certs (ended up creating a self-signed cert to get nginx running, then ran:

letsencrypt --nginx

which happily installed the cert.)

@dadegroot This is neat, that you're trying to put @Mastodon on a Pi 3, are you going to post to git or no?
@sinja @Mastodon If I can get it running and remember what I did (notes! what a great idea, shame I didn't think of it earlier), then I might post an how-to.
@dadegroot @Mastodon Assuming memory is at fault I offer this article about overclocking a Pi 3, hoping, that it may give you some insight into how you can move forward successfully [ see link ]
.
http://www.jackenhack.com/raspberry-pi-3-overclocking/