Currently feature development and test is performed on a seperate discord bot, called MrTest, who has his own API client key from the discord dev portal, and is a seperate entity from MrData within the discord program. To keep this level of separation, he has a seperate database (although since the config is a Json, this is easily changed).
However, MrTest does not have his own remote host, and simply runs on a the development PC. This is fine when there is only one person in the project team. I can develop, build and test locally, without requiring a remote host.
Once additional testers or developers join the team, unless we leave the development PC online 24/7, we will need to host MrTest remotely too.
Options can be explored, but since the port numbers are easily changed, we could use the same VM as MrData. This would increase the running costs, and the additonal processing cycles may increase the billing band we are occupying
Currently feature development and test is performed on a seperate discord bot, called MrTest, who has his own API client key from the discord dev portal, and is a seperate entity from MrData within the discord program. To keep this level of separation, he has a seperate database (although since the config is a Json, this is easily changed).
However, MrTest does not have his own remote host, and simply runs on a the development PC. This is fine when there is only one person in the project team. I can develop, build and test locally, without requiring a remote host.
Once additional testers or developers join the team, unless we leave the development PC online 24/7, we will need to host MrTest remotely too.
Options can be explored, but since the port numbers are easily changed, we could use the same VM as MrData. This would increase the running costs, and the additonal processing cycles may increase the billing band we are occupying