* Show How To Become Root
I just realized I could not do certain things from a sudo. I needed to be root via "sudo /bin/bash". I know this is a trival issue, but I am intermediate at handling the terminal and needed to know this.
* Revise Command Used To Become Root
Revised 'sudo /bin/bash' to 'sudo -i' to become root
* Fix sidekiq queues ordering in production guide
The ordering defines the priority, and the code expects default > push > pull > mailers
* Swap mailers and pull queues
The `mailers` queue contains all kinds of notifications, it's probably more important than `pull` jobs.
Making clear that this document is used to update a Mastodon instance that is not containerized with Docker, and shows a reader where to find Docker specific updating instructions, since those are not present in this document.
* Update Resources-needed.md
Add masto.donte.com.br resources, put each instance in it's own table
* Update Resources-needed.md
Revert putting each instance on it's own table
Just tested running `vagrant up --provider virtualbox` and it did not download the Ubuntu 14.04 base image, it downloaded xenial64, which is 16.04. Hopefully you will edit this :)
* Adding copy config step
As discussed in #591, docker will refuse to run the `mastodon:setup` step without some configuration file present.
* The secret generation part of docker installation process
As noticed in #6883, you need to generate the keys manually.
* Setting correct file owner is important even in the prebuilt-image case
... as evidenced by issue #6911
* This step should not be necessary -- let's fix the installation instead
As Mastodon temporaliry saves uploaded content to memory and disk (if
/tmp is a disk), unlimiting client max body size makes the server
vulnerable to DoS attack.
Without headless a lot of (for a server) unneeded dependencies needs be installed (on Debian stretch), like icon sets and x11-utils. Elasticsearch works without problems when you only install openjdk-8-jre-headless (that has much less dependencies).
Consolidated all basic configuration steps for the ideal case to top of document, moved all memory-related and "advanced" configuration to bottom. Removed remote Elasticsearch config from document entirely and replaced it with a link to ES documentation on the topic instead.
db:setup is used in all guides except Docker Guide, which uses db:migrate
to create the database. db:setup is actually superior over db:migrate for
the purpose in terms of performance and compatibility.
db:setup is performant because it does not perform redundant migrations.
db:migrate, on the other hand, executes migration code which will be
dismissed by later migrations. db:migrate also waits for seconds to allow
to interrupt migrations if it is not favorable to run them on a running
server, but db:setup is obviously executed on a instance which is not
running yet, and the wait is unnecessary.
db:migrate has a compatibility issue. It requires a compatibility layer
to keep it working, and such one may be broken, or not provided by
dependencies such as Paperclip.
This commit replaces db:migrate with db:setup in the building guide. The
procedure cannot be applied to migration from an older release, where
the old procedure could, but it is not problematic because it has
dedicated Updating section.
Stanislas