Clarify commands use to deploy to testing instances

Changes

1 changed files (+3/-3)

• Development.md
  • @@ -2,11 +2,11 @@ ## @Ta180m workflow
    The [repository](https://gitea.com/Ta180m/gitea) has several branches: - * [main](https://gitea.com/Ta180m/gitea/src/branch/main) corresponds to (insert future Gitea PR). Development mainly happens on this branch. + * [main](https://gitea.com/Ta180m/gitea/src/branch/main) corresponds to [PR #20391]. Development mainly happens on this branch. * [feature-activitypub](https://gitea.com/Ta180m/gitea/src/branch/feature-activitypub) corresponds to [PR #19133](https://github.com/go-gitea/gitea/pull/19133) which has been merged. All the other branches mostly contain some experimental or old code and aren't important. - For testing, I run `TAGS="bindata sqlite sqlite_unlock_notify" make && sudo systemctl stop gitea && sudo cp gitea /usr/bin/gitea && sudo systemctl start gitea` to deploy to https://git.exozy.me/ It's not the cleanest or fastest solution but it works. + To deploy to my testing instance at https://test.exozy.me, I run `TAGS="sqlite sqlite_unlock_notify" make watch`. - I also have a testing instance at https://test.exozy.me. + For my other testing instance at https://git.exozy.me/, I run `TAGS="bindata" make && sudo systemctl stop gitea && sudo cp gitea /usr/bin/gitea && sudo systemctl start gitea`.