A fork of JJMumblebot which is a complete mess
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
JJMumbleBot/docs/wiki/new/update_guide.html

36 lines
2.2 KiB

3 weeks ago
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>JJMumbleBot - Update Guide</title>
<link rel="stylesheet" href="https://bootswatch.com/4/darkly/bootstrap.css" crossorigin="anonymous">
<link rel="stylesheet" href="https://duckboss.github.io/JJMumbleBot/css/content-pages.css" crossorigin="anonymous">
<noscript>Please enable JavaScript in your browser!</noscript>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>
<script src="https://duckboss.github.io/JJMumbleBot/js/insert_html.js"></script>
</head>
<body>
<nav id="table_of_contents"></nav>
<div class="main-content">
<h2 id="page-title">Updating To New Versions</h2>
<p>If you want to update the bot to the latest version and you already have a previous version set up and running, follow these steps:</p>
<hr>
<h4>Please note, updating to v5.0 from v4.0 or below requires you to configure the bot from scratch like a new user.</h4>
<ul>
<li>If you are updating from pre-v5.0, refer to the quick start guide to setup from scratch instead: <a href="https://duckboss.github.io/JJMumbleBot/wiki/quick_start.html">Quick Start</a></li>
</ul>
<h3 id="update-guide">Update Guide:</h3>
<ul>
<li>Check the update notes to make sure this update won&#39;t require a new setup process</li>
<li>Back up your jjmumblebot.db and your config.ini files (both found in JJMumbleBot/cfg/ directory)</li>
<li>Back up your global_aliases.csv file if you have custom aliases registered</li>
<li>(Optional) Back up any custom plugins</li>
<li>(Optional) Back up any stored permanent media if it is stored in the root directory (this is customizable in the config.ini)</li>
<li>Download the latest version of the bot and use your previous config.ini, jjmumblebot.db and global_aliases.csv (unless the config.ini has changed)</li>
<li>Update custom plugins to work with any possible changes in the latest update</li>
<li>Update your config.ini file as required (you can use the config_template.ini file to see what&#39;s new)</li>
</ul>
</div>
<footer></footer>
</body>
</html>