The current comment says that you need to cheese to create a new cert. However, certbot gives you the following options:
What would you like to do?
-------------------------------------------------------------------------------
1: Keep the existing certificate for now
2: Renew & replace the cert (limit ~5 per 7 days)
-------------------------------------------------------------------------------
It's not clear that renewing & replacing means to create a new one
* Added the content of .well-known/host-meta file
Spent quite a lot of time today figuring out what should the webfinger file contain when the simple redirect can't be easily configured. Hopefully this clears thing up.
* Edits from comments
Disclaimer: I'm new to Github, hopefully I'm doing it right.
* 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.
Yuriy Tymchuk