View source for Mastodon

Setting up a Masotdon server on [[Debian]] is somewhat annoying, due to the node- and ruby-based implementation. Most guides involve downloading and installing a large number of sources outside of [[APT]]. There's little need for such vulgarisms.

My [https://jsm.qemfd.net running install] uses the 3.2 branch of Mastodon atop Debian Unstable.

First, determine your domain name. You'll likely be serving Mastodon as a virtual host in your main nginx/apache config, so give it its own, distinct FQDN. It is not trivial to change your server's name later (it will, at a minimum, break existing federations), so choose wisely.

==System work==
* Via [[APT]], install <tt>nodejs</tt>, <tt>redis-server</tt>, <tt>ruby-redis</tt>, <tt>rake</tt>, <tt>rbenv</tt>, <tt>ruby-bundler</tt>, <tt>postgresql-contrib</tt>, <tt>libpq-dev</tt>, <tt>libprotobuf-dev</tt>, <tt>protobuf-compiler</tt>, <tt>libidn11-dev</tt>, and <tt>yarnpkg</tt> ("[https://classic.yarnpkg.com/en/ yarn]").
** You will now have a PostgreSQL instance running on localhost:tcp/5432, if you didn't before.
** You will now have a Redis instance running on localhost:tcp/6379, if you didn't before.
* Restrict Redis to 127.0.0.1 by ensuring the following line is in <tt>/etc/redis/redis.conf</tt>:
** <tt>bind 127.0.0.1 ::1</tt>
** If necessary, run <tt>sudo systemctl restart redis</tt>
* So far as I can tell, you must now symlink <tt>/usr/bin/yarnpkg</tt> to <tt>yarn</tt> in some PATH directory 🤮:
** <tt>ln -s /usr/bin/yarnpkg /usr/local/bin/yarn</tt>
* Prep the database:
** <tt>echo "CREATE USER mastodon CREATEDB;" | sudo -u postgres psql</tt>
* Create <tt>mastodon</tt> user (salt to taste):
** <tt>sudo adduser --disabled-login --gecos "Mastodon service account" mastodon</tt>

==User work==
Remaining work will be done as the <tt>mastodon</tt> user, in its home directory.
* <tt>git clone https://github.com/tootsuite/mastodon.git ~/live</tt>
* <tt>cd live</tt>
* <tt>RAILS_ENV=production bundle config set --local deployment true</tt>
* <tt>RAILS_ENV=production bundle config set --local without development:test</tt>
* <tt>RAILS_ENV=production bundle install</tt>
* <tt>RAILS_ENV=production bundle exec rake mastodon:setup</tt>
** Use the same PostgreSQL user name you created earlier.
** So far as I can tell, use a blank password for PostgresQDL and Redis.
** I do (n)ot upload files to the "cloud", whatever that even means
** You are (n)ot running in a Docker (presumably)

==Webserver work==
Most guides assume you're running <tt>nginx</tt>. My directions assume Apache.

* Set up LetsEncrypt: <tt>certbot certonly --apache -d FQDN</tt>
* Prepare non-TLS upgrade config: try [https://gist.github.com/dankamongmen/529de45dc4dff3835f272ca5d3fd430e something like this]
* Prepare TLS proxy config: try [https://gist.github.com/dankamongmen/3bd66ec624a683f2c2be9ce7ab86a63b something like this]
* <tt>sudo a2ensite mastodon-ssl</tt>
* <tt>sudo a2ensite mastodon</tt>
* <tt>sudo a2enmod proxy_http</tt> (if not already enabled)
* <tt>sudo systemctl restart apache2</tt>

==Start it==
* <tt>sudo cp ~mastodon/live/dist/*service /etc/systemd/system</tt>
* <tt>for in in web sidekiq streaming ; do sudo systemctl start mastodon-$i ; done</tt>
* Check the status of all three units with <tt>systemctl status</tt> and, if necessary, <tt>journalctl</tt>
** You ought have a <tt>puma</tt> process listening on port 3000
** You ought have a <tt>node</tt> process listening on port 4000
* If good, <tt>for in in web sidekiq streaming ; do sudo systemctl enable mastodon-$i ; done</tt>
** The units are now persistent, and ought start at system boot

==Full text search==
If you're willing to run Java and a potentially-dodgy elasticsearch package (or build it from [https://github.com/elastic/elasticsearch source]), you can have full text search. Building from source is normally a pleasant endeavor, but who wants to fuck with gradle and all it implies?

* <tt>sudo apt-get install default-jre-headless</tt>
** You might ask, "But [[User:Dank|dank]], surely <tt>elasticsearch</tt> Depends on <tt>default-jre-headless</tt>?"
** '''Narrator:''' It does not Depend on <tt>default-jre-headless</tt>.
* <tt>apt-key adv --fetch-keys https://artifacts.elastic.co/GPG-KEY-elasticsearch</tt>
* <tt>echo "deb https://artifacts.elastic.co/packages/7.x/apt stable main" | sudo tee /etc/apt/sources.list.d/elastic-7.x.list</tt>
* <tt>sudo apt-get update && sudo apt-get install elasticsearch</tt>
* <tt>sudoedit /etc/elasticsearch/elasticsearch.yml</tt> and change <tt>network.host</tt> to 127.0.0.1
** unless you love Romanian botnets all up in your shit
* <tt>systemctl start elasticsearch</tt>
** You ought now have a <tt>java</tt> process listening on tcp/9200 ''shudder''
* Add the following to <tt>.env.production</tt>:
<pre>
ES_ENABLED=true
ES_HOST=localhost
ES_PORT=9200
</pre>
* Restart <tt>mastodon-sidekiq</tt> and <tt>mastodon-web</tt> units
* <tt>RAILS_ENV=production bin/tootctl search deploy</tt>
* <tt>sudo systemctl enable elasticsearch</tt> for persistence