Restore Docker guide from the 'archive' branch #775
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Add docker guide from main repo readme * Add maintenance tasks doc to running section * Clean up markdown in prod guide * Move guidance to use tagged releases to docs * Move local domain and host config to docs repo * Title of page * Update Production-guide.md
Fix typo
Updates Docker Update Instructions for git
* Prerequisites and cronjobs * We probably we don't even support Windows and Mac
This change will help users avoid unnecessary procedure to complete `bundle install` outside the container. The explanation > To generate the PAPERCLIP_SECRET, SECRET_KEY_BASE, and > OTP_SECRET, you may use: > > ``` > rake secret > ``` gives users a false impression that secrets have to be filled in before the image can be built. Here, with introduction of CLD3, completion of `bundle install` became more involved procedure to prepare tools and libraries as well as higher version of Ruby.
* Mention that we can use prebuilt images. Instead of building our own. * Mention that we need to comment out `build`. If we want to use prebuilt.
this has been out of date for a few months now
* Add how to create VAPID_PRIVATE_KEY and VAPID_PUBLIC_KEY * fix typo
HTTPS hint added
Removed the ssh port forwarding info
* Clarify Docker instructions for prebuilt images Made clear there are two options for getting the Docker image: pulling the prebuilt image, or building your own. Using a prebuilt image is easier for anyone who hasn't made code changes on their instance. * Fix errors in Docker prebuilt image instructions
…on#560) 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.
* Adding copy config step As discussed in mastodon#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
I've deployed from master and didn't checkout a stable release tag....
|
it seems that the db host issue is fixed -edit: |
|
the networking is rigged, had to remove it from the docker-compose.yml |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP, as the install in docker is currently broken ( https://pastebin.com/raw/trpk4QC5 )
I also didn't try building it because I don't have the right hugo version on my system