Discord Bot - Revision history

Lucash at 09:05, 14 February 2026

2026-02-14T09:05:47Z

@@ Line 39: / Line 39: @@
 [[File:offline_bot.png]]
-== Write the Bot Script in Python ==
+== Setup the Discord Bot Intents and Token ==
 Go back to the Discord bot page and click bot on the left navigation again.
@@ Line 117: / Line 48: @@
 [[File:discord_intents.png]]
-On the same page click the 'Reset Token' button, and then copy/paste the token.
+On the same page click the 'Reset Token' button, and then copy/paste the token. Keep this token somewhere for now, we will use it later when writing the bot code.
 [[File:copy_token.png]]
-If you ever think someone has gotten your token, for instance if you posted it on a public wiki like I just did, be sure to come back to this page and reset it. Anyone who has your token can do whatever permissions you granted your bot to your server. Now you need to paste this token into your '.env' file that you created. So go back to the Plesk file manager and click the '.env' file to edit it. Paste the token into the file like this:
+If you ever think someone has gotten your token, for instance if you posted it on a public wiki like I just did, be sure to come back to this page and reset it. Anyone who has your token can do whatever permissions you granted your bot to your server.
-Make sure the line starts with 'DISCORD_TOKEN=' like that. Then click 'Save Changes' and close the tab. Saving your token separate from your Python code is good practice because this way you can share the code on GitHub or something like that without worrying about people getting access to your bot.
+== Write your Bot Code ==
 == Starting and Stopping Your Bot ==
@@ Line 220: / Line 153: @@
 == Test It Out ==
-Now everything should be ready to be tested. Open your browser and go to 'yourdomain.helioho.st/bot_control/' and when you click Start it should start the bot. You can check if the bot is running by going to Discord and seeing if HelioBot is showing up as online now. If it is, test it out by typing the command:
+Now everything should be ready to be tested. Open your browser and go to 'yourdomain.helioho.st/bot_control/' and when you click Start it should start the bot. You can check if the bot is running by going to Discord and seeing if HelioBot is showing up as online now. If it is, test it out by typing the command if you have been following the Python tutorial:
 <pre>
@@ Line 248: / Line 181: @@
 [[File:bot_dashboard.png]]
-If you followed the guide exactly your bot will use about 50 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty|Morty]].
+If you followed the Python guide exactly your bot will use about 50 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty|Morty]].
 If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit. You could also move to a VPS where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. {{Template:VPSInfo}}

KazVee: Use {{Template:VPSInfo}} for VPS Info

2025-08-31T19:02:41Z

Use {{Template:VPSInfo}} for VPS Info

← Older revision		Revision as of 19:02, 31 August 2025
Line 250:		Line 250:
	If you followed the guide exactly your bot will use about 50 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage\|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty\|Morty]].		If you followed the guide exactly your bot will use about 50 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage\|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty\|Morty]].

	If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit~~, or moving~~ to a VPS where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. {{Template:VPSInfo}}		If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit. You could also move to a VPS where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. {{Template:VPSInfo}}

	== Automatically Restarting the Bot ==		== Automatically Restarting the Bot ==

KazVee: Use {{Template:VPSInfo}} for VPS Info

2025-08-31T17:50:44Z

Use {{Template:VPSInfo}} for VPS Info

← Older revision		Revision as of 17:50, 31 August 2025
Line 241:		Line 241:

	We enforce a memory limit of no more than {{Template:MemoryLimit}} per day and a limit of {{Template:CPULimit}} usage per day on our shared hosting servers.		We enforce a memory limit of no more than {{Template:MemoryLimit}} per day and a limit of {{Template:CPULimit}} usage per day on our shared hosting servers.
	* On the [[:Tommy\|Tommy]] and [[:Johnny\|Johnny]] servers, if you exceed these limits, your account will be suspended.		* On the [[:Tommy\|Tommy]] and [[:Johnny\|Johnny]] servers, if you exceed these limits, your account will be [[:Suspension_Policy#High_Server_Usage\|suspended]].
	* On the [[:Morty\|Morty]] server, if you exceed these limits, we will charge you for overages.		* On the [[:Morty\|Morty]] server, if you exceed these limits, we will charge you for overages.

Line 250:		Line 250:
	If you followed the guide exactly your bot will use about 50 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage\|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty\|Morty]].		If you followed the guide exactly your bot will use about 50 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage\|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty\|Morty]].

	If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or ~~[https://heliohost.org/vps/~~ moving to a VPS] where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. ~~You can get a 10% discount when you pay for 6 months upfront.~~		If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or moving to a VPS where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. {{Template:VPSInfo}}

	== Automatically Restarting the Bot ==		== Automatically Restarting the Bot ==

KazVee: Removed a single letter 's' from a word

2025-04-19T14:47:55Z

Removed a single letter 's' from a word

← Older revision		Revision as of 14:47, 19 April 2025
Line 283:		Line 283:

	{{Danger\|		{{Danger\|
	Running a scheduled task every minute increases your load by quite a bit even if your bot never needs to be restarted. Simply checking if it has crashed causes some load. Worst case scenario: this scheduled ~~tasks~~ starts a new bot process every minute even though you already have a copy of the bot running, and you get suspended on [[:Tommy\|Tommy]] or [[:Johnny\|Johnny]] in record time, or reach the maximum billing on [[:Morty\|Morty]] faster than anyone has ever dreamed possible.		Running a scheduled task every minute increases your load by quite a bit even if your bot never needs to be restarted. Simply checking if it has crashed causes some load. Worst case scenario: this scheduled task starts a new bot process every minute even though you already have a copy of the bot running, and you get suspended on [[:Tommy\|Tommy]] or [[:Johnny\|Johnny]] in record time, or reach the maximum billing on [[:Morty\|Morty]] faster than anyone has ever dreamed possible.
	}}		}}

	[[Category:Tutorials]]		[[Category:Tutorials]]

Krydos: Added section on automatically restarting the bot after a crash

2025-03-23T17:08:29Z

Added section on automatically restarting the bot after a crash

← Older revision		Revision as of 17:08, 23 March 2025
Line 251:		Line 251:

	If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or [https://heliohost.org/vps/ moving to a VPS] where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. You can get a 10% discount when you pay for 6 months upfront.		If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or [https://heliohost.org/vps/ moving to a VPS] where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. You can get a 10% discount when you pay for 6 months upfront.

			== Automatically Restarting the Bot ==

			We've had a lot of people ask us if we intentionally stop their bots after 60 minutes or so. The answer is no. The only time we kill processes automatically is if your account got suspended for high load. In our testing the bots can run for weeks or longer without needing to be restarted. Our servers are stable enough to run for months or years without a reboot as well. The issue is undoubtedly that people write bad code that crashes, but rather than admitting that their code is buggy, it's easier to just blame us.

			If your bot keeps stopping on its own, the best solution is to check the logs and fix the issue. If there is nothing shown in the logs that means you need to add more logging to your code to figure out why it's crashing. If you still can't figure it out you could enable auto-restart, but it's really just a crutch for buggy code rather than a real fix. If your bot code really is stable enough to run for weeks or months without crashing, auto-restart can also benefit you in the rare case of us rebooting the whole server, your bot will automatically start up as soon as the reboot is finished.

			{{Caution\|
			Enabling auto-restart could increase your chance of getting suspended. If you don't currently need your bot online we recommend shutting it down entirely rather than leaving it restarting over and over.
			}}

			To set up auto-restart login to Plesk and navigate to:

			'''Login > Plesk > Websites & Domains > [ domain ] > Scheduled Tasks'''

			[[File:plesk-scheduled-tasks.png]]

			Next, click 'Add Task' and select the 'Fetch a URL' option.

			[[File:Plesk-schedule-a-task.png]]

			In the URL box put the start link from your bot_control page if you would click 'Start'. The easiest way to get this value is to stop your bot, and then right click on the 'Start' link, and 'Copy link address'.

			[[File:Telegram-start-link.png]]

			If you followed this guide without changing too much it should be something like 'yourdomain.helioho.st/bot_control/?action=start'.

			[[File:Telegram-cron-job.png]]

			For those of you who want to minimize the downtime, and maximize your suspension chance you can set the schedule task up to run every minute like this with Cron Style and '* * * * *'. If everything is working correctly it will check if the bot is up every minute. Then if the bot is stopped it will restart it, and if the bot is already running it won't do anything.

			{{Danger\|
			Running a scheduled task every minute increases your load by quite a bit even if your bot never needs to be restarted. Simply checking if it has crashed causes some load. Worst case scenario: this scheduled tasks starts a new bot process every minute even though you already have a copy of the bot running, and you get suspended on [[:Tommy\|Tommy]] or [[:Johnny\|Johnny]] in record time, or reach the maximum billing on [[:Morty\|Morty]] faster than anyone has ever dreamed possible.
			}}

	[[Category:Tutorials]]		[[Category:Tutorials]]

Krydos: /* Starting and Stopping Your Bot */ Updated the bot_control script

2025-03-23T17:02:47Z

Starting and Stopping Your Bot: Updated the bot_control script

← Older revision		Revision as of 17:02, 23 March 2025
Line 160:		Line 160:
	#!/bin/bash		#!/bin/bash

	# edit ~~these~~ to match your ~~username, main domain, and~~ bot filename		# edit this to match your bot filename
	~~username="krydos"~~
	~~main_domain="krydos.heliohost.org"~~
	bot_name="heliobot.py"		bot_name="heliobot.py"

Line 168:		Line 166:

	printf 'Content-Type: text/html\n\n'		printf 'Content-Type: text/html\n\n'
	temp=`ps axo user:16,pid,pcpu,pmem,vsz,rss,tty,stat,start,time,command\|grep -v grep\|grep "^$username"`		username=`whoami`
			pwd=`printenv\|grep '^PWD'\|cut -f2 -d'='`
			main_domain=`echo "$pwd"\|cut -f3 -d'/'`
			control=`echo "$pwd"\|cut -f5 -d'/'`
			temp=`ps axo user:16,pid,pcpu,pmem,vsz,rss,tty,stat,start,time,command\|grep -v grep\|grep "^$username "`
	running=`echo "$temp"\|grep -c "$bot_name"`		running=`echo "$temp"\|grep -c "$bot_name"`
	file_base=`echo $bot_name\|tr -cd "a-zA-Z0-9"`		file_base=`echo $bot_name\|tr -cd "a-zA-Z0-9"`
Line 181:		Line 183:
	echo "$bot_name is not running. <a href='?action=start'>Start</a> - "		echo "$bot_name is not running. <a href='?action=start'>Start</a> - "
	fi		fi
	echo "<a href='https://heliohost.org/dashboard/load/' target='_blank'>Check Load</a><br><br>Logs: <a href='?action=clear'>Clear Logs</a> - <a href='/~~bot_control~~/$log_name'>Full Logs</a><pre>"		echo "<a href='https://heliohost.org/dashboard/load/' target='_blank'>Check Load</a><br><br>Logs: <a href='?action=clear'>Clear Logs</a> - <a href='/$control/$log_name'>Full Logs</a><pre>"
	tail -30 ~~/home/~~$~~main_domain/httpdocs/bot_control~~/$log_name		tail -30 $pwd/$log_name
	echo "</pre>~~<~~script~~>~~reloading = setTimeout('window.location.reload();', 10000);~~<~~/script~~>~~"		echo "</pre><script>reloading = setTimeout('window.location.reload();', 10000);</script>"
	fi		fi
	ts=`date +"%Y-%m-%d %H:%M:%S"`		ts=`date +"%Y-%m-%d %H:%M:%S"`
	if [ "$QUERY_STRING" == "action=stop" ]; then		if [ "$QUERY_STRING" == "action=stop" ]; then
	echo "[$ts] Stopping $bot_name." >> ~~/home/~~$~~main_domain/httpdocs/bot_control~~/$log_name		echo "[$ts] Stopping $bot_name." >> $pwd/$log_name
	pid=`echo "$temp"\|grep "$bot_name"\|tail -1\|awk '{print $2}'`		pid=`echo "$temp"\|grep "$bot_name"\|tail -1\|awk '{print $2}'`
	if [ ${#pid} -ne 0 ]; then		if [ ${#pid} -ne 0 ]; then
	kill $pid		kill $pid
	fi		fi
	echo "Stopping $bot_name...~~<~~script~~>~~window.location.replace('/~~bot_control~~/');~~&lt~~;/script~~>~~"		echo "Stopping $bot_name...<script>setInterval(\"window.location.replace('/$control/');\", 2000);</script>"
	fi		fi
	if [ "$QUERY_STRING" == "action=start" ]; then		if [ "$QUERY_STRING" == "action=start" ]; then
Line 198:		Line 200:
	echo "$bot_name is already running..."		echo "$bot_name is already running..."
	else		else
	echo "[$ts] Starting $bot_name." >> ~~/home/~~$~~main_domain/httpdocs/bot_control~~/$log_name		echo "[$ts] Starting $bot_name." >> $pwd/$log_name
	/usr/bin/python3.12 -u /home/$main_domain/$bot_name >> ~~/home/~~$~~main_domain/httpdocs/bot_control~~/$log_name 2>&1 &		/usr/bin/python3.12 -u /home/$main_domain/$bot_name >> $pwd/$log_name 2>&1 &
	echo "Starting $bot_name...~~<~~script~~>~~window.location.replace('/~~bot_control~~/');~~<~~/script~~>~~"		echo "Starting $bot_name...<script>window.location.replace('/$control/');</script>"
	fi		fi
	fi		fi
	if [ "$QUERY_STRING" == "action=clear" ]; then		if [ "$QUERY_STRING" == "action=clear" ]; then
	cat /dev/null > ~~/home/~~$~~main_domain/httpdocs/bot_control~~/$log_name		cat /dev/null > $pwd/$log_name
	echo "Clearing logs...~~<~~script~~>~~window.location.replace('/~~bot_control~~/');~~<~~/script~~>~~"		echo "Clearing logs...<script>window.location.replace('/$control/');</script>"
	fi		fi
	exit 0		exit 0
	</pre>		</pre>

	Be sure to edit the ~~three variables~~ at the top of the file to match your ~~username, main domain, and~~ bot filename.		Be sure to edit the variable at the top of the file to match your bot filename.

	Now, we need to set the permissions of this 'index.sh' file to be executable. On the file manager click the 'rw- r-- r--' and check all the 'Execute/Search' boxes just like we did the heliobot.py file earlier.		Now, we need to set the permissions of this 'index.sh' file to be executable. On the file manager click the 'rw- r-- r--' and check all the 'Execute/Search' boxes just like we did the heliobot.py file earlier.

Krydos: /* Starting and Stopping Your Bot */ Changed caution box into info box

2025-03-16T02:41:12Z

Starting and Stopping Your Bot: Changed caution box into info box

← Older revision		Revision as of 02:41, 16 March 2025
Line 131:		Line 131:
	You have a functional bot now, but you need a way to start and stop it.		You have a functional bot now, but you need a way to start and stop it.

	{{~~Caution~~\|		{{Info\|
	Side note: Previous versions of this guide used Python scripts to start and stop the Discord bot. Unfortunately, the people who wanted to write their bot in Node.js always complained that they didn't want to use Python for anything. Likewise, if we used Node.js to start and stop the bot, the Python people would inevitably complain about not wanting to use Node.js for anything. Therefore, we wrote the start and stop scripts in Bash CGI to make absolutely sure that no one is happy.		Side note: Previous versions of this guide used Python scripts to start and stop the Discord bot. Unfortunately, the people who wanted to write their bot in Node.js always complained that they didn't want to use Python for anything. Likewise, if we used Node.js to start and stop the bot, the Python people would inevitably complain about not wanting to use Node.js for anything. Therefore, we wrote the start and stop scripts in Bash CGI to make absolutely sure that no one is happy.
	}}		}}

Krydos: /* Starting and Stopping Your Bot */ Updated index.sh code to help prevent multiple bots running at the same time

2025-03-15T21:50:22Z

Starting and Stopping Your Bot: Updated index.sh code to help prevent multiple bots running at the same time

← Older revision		Revision as of 21:50, 15 March 2025
Line 195:		Line 195:
	fi		fi
	if [ "$QUERY_STRING" == "action=start" ]; then		if [ "$QUERY_STRING" == "action=start" ]; then
	echo "[$ts] Starting $bot_name." >> /home/$main_domain/httpdocs/bot_control/$log_name		if [ $running -ne 0 ]; then
	/usr/bin/python3.12 -u /home/$main_domain/$bot_name >> /home/$main_domain/httpdocs/bot_control/$log_name 2>&1 &		echo "$bot_name is already running..."
	echo "Starting $bot_name...<script>window.location.replace('/bot_control/');</script>"		else
			echo "[$ts] Starting $bot_name." >> /home/$main_domain/httpdocs/bot_control/$log_name
			/usr/bin/python3.12 -u /home/$main_domain/$bot_name >> /home/$main_domain/httpdocs/bot_control/$log_name 2>&1 &
			echo "Starting $bot_name...<script>window.location.replace('/bot_control/');</script>"
			fi
	fi		fi
	if [ "$QUERY_STRING" == "action=clear" ]; then		if [ "$QUERY_STRING" == "action=clear" ]; then

Krydos: or = of, removed extra and

2025-03-15T21:48:07Z

or = of, removed extra and

← Older revision		Revision as of 21:48, 15 March 2025
Line 242:		Line 242:
	[[File:bot_dashboard.png]]		[[File:bot_dashboard.png]]

	If you followed the guide exactly your bot will use about 50 GB or memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage\|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty\|Morty]].		If you followed the guide exactly your bot will use about 50 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage\|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty\|Morty]].

	If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or [https://heliohost.org/vps/ moving to a VPS] where you have root SSH access, dedicated memory ~~and~~ CPU, and no load limits. You can get a 10% discount when you pay for 6 months upfront.		If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or [https://heliohost.org/vps/ moving to a VPS] where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. You can get a 10% discount when you pay for 6 months upfront.

	[[Category:Tutorials]]		[[Category:Tutorials]]

KazVee: Add Category tag for testing

2025-03-11T00:06:33Z

Add Category tag for testing

← Older revision		Revision as of 00:06, 11 March 2025
Line 245:		Line 245:

	If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or [https://heliohost.org/vps/ moving to a VPS] where you have root SSH access, dedicated memory and CPU, and no load limits. You can get a 10% discount when you pay for 6 months upfront.		If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or [https://heliohost.org/vps/ moving to a VPS] where you have root SSH access, dedicated memory and CPU, and no load limits. You can get a 10% discount when you pay for 6 months upfront.

			[[Category:Tutorials]]