2
Migration Guide
Wise edited this page 2022-07-29 11:54:08 +02:00
Migration Guide (to v2)
Turn to your bot. Send /export
to back up your subscriptions.
Docker / Docker Compose / Dirty run
- *
Turn to your bot. Send/export
to back up your subscriptions. - (Optional) Back up your
/path/to/bot/config/
. - Delete
/path/to/bot/config/
. - Redeploy your bot cleanly. Configure other variables on Advanced Settings as you need.
- Turn to your bot. Send
/import
to import your subscriptions again.
Railway.app
- *
Turn to your bot. Send/export
to back up your subscriptions. - Turn to your Railway project.
- (Optional) Back up your Redis database if you know how to do it.
- Turn to the
Settings
page, switch to theDanger
tab.Remove
the Redis plugin. - Click the
Add Plugin
button on the bottom left, selectAdd PostgreSQL
. - Turn to the
Variables
page.Delete
theCHATID
andDELAY
variables. Configure other variables on Advanced Settings as you need. - Turn to your forked GitHub repository. Switch to the branch you've deployed, then click
Fetch upstream
andFetch and merge
. - Wait for your Railway project to be updated.
- Turn to your bot. Send
/import
to import your subscriptions again.
If you're using the multiuser
branch...
Make sure you switch to the master
or dev
branch. For Railway, you can do this by switching the deployment triggers (Deployments
-> Triggers
-> Branches
-> add a new trigger and delete the old one) BEFORE START MIGRATING ACCORDING TO THE GUIDE.
If you still would like to limit the bot to serve you only...
Please read the FAQ General and FAQ Operational
Channels Using RSStT
You can also add content here! Open a Pull Request or join our discussion group and tell us about it!
If you use the public bot in your Channel, consider mentioning the bot (or this project) in your channel description (or pinned message) to let more people know about it. That's not a compulsion.