Updated Initial migration (markdown)
parent
efa3adec99
commit
69d232f25f
|
@ -1,10 +1,10 @@
|
|||
Hello! This is a guide to help you migrate from Mastodon to Hometown. This guide shows you how to migrate from Mastodon `v3.5.5` to Hometown `v3.5.5+hometown-1.08`. Right now we are up to date with Mastodon 3.5.5, so __make sure you are running Mastodon 3.5.5 before trying this__. There are [Mastodon installation instructions here](https://docs.joinmastodon.org/user/run-your-own/). And please test in a local development environment or a test server first if at all possible.
|
||||
Hello! This is a guide to help you migrate from Mastodon to Hometown. This guide shows you how to migrate from Mastodon `v4.0.2` to Hometown `v4.0.2+hometown-1.1.0`. Right now we are up to date with Mastodon 4.0.2, so __make sure you are running Mastodon 4.0.2 before trying this__. There are [Mastodon installation instructions here](https://docs.joinmastodon.org/user/run-your-own/). And please test in a local development environment or a test server first if at all possible.
|
||||
|
||||
__THIS IS NOT FOR BEGINNERS__. You should be comfortable maintaining Mastodon and updating from one version of Mastodon to another. If you are an instance admin who has upgraded your instance from, say, 2.9.5 up to 3.5.5 over time, you should be familiar with every step of this process.
|
||||
|
||||
Assuming you are running Mastodon 3.5.5 (aka you have the `v3.5.5` tag checked out in git and a `git log` shows your most recent commit is `696f7b360882e71ff45b6ddafc8eea17184a0f31`), the following should work.
|
||||
Assuming you are running Mastodon 4.0.2 (aka you have the `v4.0.2` tag checked out in git and a `git log` shows your most recent commit is `03b0f3ac83edfc46d304bfca1539ca6000e36fc3`), the following should work.
|
||||
|
||||
First, triple-check you're on the v3.5.5 tag:
|
||||
First, triple-check you're on the `v4.0.2` tag:
|
||||
|
||||
```bash
|
||||
git describe --tags
|
||||
|
@ -12,23 +12,23 @@ git describe --tags
|
|||
|
||||
The output should be:
|
||||
|
||||
`v3.5.5`
|
||||
`v4.0.2`
|
||||
|
||||
> If you get an error instead, Mastodon probably isn't installed as a Git repo. This can happen if you install Mastodon via downloading a ZIP of the source, or you use something that does that, like Yunohost. Hometown only supports a git-based Mastodon installation.
|
||||
|
||||
Next, add the Hometown Github repo as a remote called `hometown` and make a branch off of `v3.5.5` for your new modified installation. Then, switch to that new branch, which right now is identical to 3.5.5.
|
||||
Next, add the Hometown Github repo as a remote called `hometown` and make a branch off of `v4.0.2` for your new modified installation. Then, switch to that new branch, which right now is identical to 4.0.2.
|
||||
|
||||
```bash
|
||||
git remote add hometown https://github.com/hometown-fork/hometown.git
|
||||
git branch hometown-v1.0.8
|
||||
git checkout hometown-v1.0.8
|
||||
git branch hometown-v1.1.0
|
||||
git checkout hometown-v1.1.0
|
||||
```
|
||||
|
||||
The next thing we do is fetch and merge the `v3.5.5+hometown-1.0.8` tag from the Hometown Github repo and merge it into our current branch.
|
||||
The next thing we do is fetch and merge the `v4.0.2+hometown-1.1.0` tag from the Hometown Github repo and merge it into our current branch.
|
||||
|
||||
```bash
|
||||
git fetch hometown
|
||||
git merge v3.5.5+hometown-1.0.8
|
||||
git merge v4.0.2+hometown-1.1.0
|
||||
```
|
||||
|
||||
Now we need to run `bundle install` again, and then a database migration (replace "production" with your appropriate environment variable):
|
||||
|
|
Loading…
Reference in New Issue