Well, I host my bot on GitHub Actions! Yes, that’s right, I’m freeloading on the GitHub action servers! There’s pretty much no downtime, but it has to be restarted every six hours at least.
Open up one of the test files and IntelliJ will show you green arrows. When you click those, the test will run and the test configuration will be added
To try out the JVM REPL, go to the jvm's Main.scala and IntelliJ will again show you a button to run it
[error] 1647 | case a: VNum => VNum(scala.math.round(a.toDouble))
[error] | ^^^^^^^^^^
[error] |value toDouble is not a member of vyxal.VNum, but could be made available as an extension method.
Hey @Ginger, how possible would it be to make it so that changes could be pulled to Vyxal Bot without killing uptime? Something like having two instances (a main and backup) could work. When pulling, switch to the backup, update the main, switch back to main, update the backup
Just an idea to keep both functionality updated and uptime ticking up
Not something to commit to at all
And the backup wouldn't need to be hosted elsewhere too. It could just be hosted on the same server
It'd only be a backup instance for switching
In fact, it could even just be a spawned process created when pulling and destroyed after the updating is done
which reminds me, there's a little bug with the online interpreter where if you type a letter that isn't a built-in, it errors and closes the code window