ensure releases don't collide

This commit is contained in:
FloatingGhost 2022-06-11 18:32:10 +01:00
parent 6ee32cbdc9
commit 2d3c10e4ff
2 changed files with 33 additions and 1 deletions

View file

@ -21,7 +21,6 @@ pipeline:
- SCW_ACCESS_KEY
- SCW_SECRET_KEY
- SCW_DEFAULT_ORGANIZATION_ID
group: release
image: ${docker_prefix}elixir:1.13
environment:
MIX_ENV: prod
@ -34,6 +33,7 @@ pipeline:
- echo "import Mix.Config" > config/prod.secret.exs
- mix local.hex --force
- mix local.rebar --force
- mix deps.clean --all
- mix deps.get --only prod
- mkdir release
- export PLEROMA_BUILD_BRANCH=$CI_COMMIT_BRANCH
@ -62,6 +62,7 @@ pipeline:
- echo "import Mix.Config" > config/prod.secret.exs
- mix local.hex --force
- mix local.rebar --force
- mix deps.clean --all
- mix deps.get --only prod
- mkdir release
- export PLEROMA_BUILD_BRANCH=${CI_COMMIT_BRANCH}

View file

@ -1,3 +1,34 @@
## Upgrading to Akkoma
### From source
```bash
git remote set-url origin https://akkoma.dev/AkkomaGang/akkoma.git/
git fetch origin
git pull -r
```
Then compile, migrate and restart as usual.
Then if you've done anything fancy to the frontend, you'll want to get the
updates for that as well. This won't be the same for any two instances,
so `https://akkoma.dev/AkkomaGang/pleroma-fe` is the repo you need.
### From OTP
```bash
./bin/pleroma_ctl update --zip-url https://akkoma-updates.s3-website.fr-par.scw.cloud/develop/akkoma-amd64.zip
./bin/pleroma_ctl migrate
```
Then restart. When updating in the future, can just use
```bash
./bin/pleroma_ctl update --branch develop
```
### Old readme follows
<img src="https://git.pleroma.social/pleroma/pleroma/uploads/8cec84f5a084d887339f57deeb8a293e/pleroma-banner-vector-nopad-notext.svg" width="300px" />
## About