Nope no errors or anything, this question has to do with design.
Apologies if I'm in the incorrect forum, looks ok to me.
Background: I'm planning on joining in on starting a company soon and another one of my many roles is the programmer
I'm creating a program for game server booking and hosting which will be the third tier of our future company. Look at GriffinRUN for an example of what some of our company's focus will be on. The main focus of my program will be automation. When a customer orders a server, my program will determine what machine to set the server up on and then install, setup, configure, and start without human intervention. Also included for automation will be deletions of past customers (hopefully not very often), changes to the servers, and upkeep/upgrades--each customer having the ability to perform these tasks (think ensim or cpanel for web servers).
Where my problem starts is whether or not to install "automation scripting" on every machine which servers will be setup on or store the automation scripting on the web server and use SSH/telnet and FTP to setup the game servers. Both ideas have goods and bads and hopefully I can inlist some help from the Macrumors elite! Hopefully what I'm askin' makes sense.
Good vs. bad for remote installations:
Good: I wont have to keep uploading the latest versions of ALL the games/mods/addons we plan to host to EVERY machine. This includes an installation file for the game, installation files for every mod the game has, and installation files for every addon. This can add up to be alot of files, each game has on average 2 mods and 2 or 3 addons.
Bad: Not so easy to program... This can prove to be slow and sort of clunky. By that I mean, to do "remote installations" I will need to use SSH to add a new user to the system and untar the installation packages from the web server. The last task will be to build the configuration files (e.g. server.cfg, maplist.txt, motd.txt, autoexec.bat) based on the customer's order and upload the files via FTP -OR- changes made after their order in their "user panel" and upload the files. Because all the installation packages for the various things to install are in the 100Mb's I'm worried this process will take too long considering there's 4 to 6 installations to be done for each customer.
Good vs. bad for local installations:
Good: Easy to program and fast as can be.
Bad: Will need to keep ALOT of packages current on EVERY machine... makes automation less helpful. Will need to do some redirection. That is, from the log-in to each customer's user panel and from there redirect them to the machine their server is located on so the customer can make changes to his/her server. Also, when ordering I will need to have scripting that will determine which machine to setup on and redirect from there. So the redirection can happen I will need to install and keep updated Apache on every machine, also a big pain considering we plan to have over 20 machines at some point.
Apologies if I'm in the incorrect forum, looks ok to me.
Background: I'm planning on joining in on starting a company soon and another one of my many roles is the programmer
I'm creating a program for game server booking and hosting which will be the third tier of our future company. Look at GriffinRUN for an example of what some of our company's focus will be on. The main focus of my program will be automation. When a customer orders a server, my program will determine what machine to set the server up on and then install, setup, configure, and start without human intervention. Also included for automation will be deletions of past customers (hopefully not very often), changes to the servers, and upkeep/upgrades--each customer having the ability to perform these tasks (think ensim or cpanel for web servers).Where my problem starts is whether or not to install "automation scripting" on every machine which servers will be setup on or store the automation scripting on the web server and use SSH/telnet and FTP to setup the game servers. Both ideas have goods and bads and hopefully I can inlist some help from the Macrumors elite! Hopefully what I'm askin' makes sense.
Good vs. bad for remote installations:
Good: I wont have to keep uploading the latest versions of ALL the games/mods/addons we plan to host to EVERY machine. This includes an installation file for the game, installation files for every mod the game has, and installation files for every addon. This can add up to be alot of files, each game has on average 2 mods and 2 or 3 addons.
Bad: Not so easy to program... This can prove to be slow and sort of clunky. By that I mean, to do "remote installations" I will need to use SSH to add a new user to the system and untar the installation packages from the web server. The last task will be to build the configuration files (e.g. server.cfg, maplist.txt, motd.txt, autoexec.bat) based on the customer's order and upload the files via FTP -OR- changes made after their order in their "user panel" and upload the files. Because all the installation packages for the various things to install are in the 100Mb's I'm worried this process will take too long considering there's 4 to 6 installations to be done for each customer.
Good vs. bad for local installations:
Good: Easy to program and fast as can be.
Bad: Will need to keep ALOT of packages current on EVERY machine... makes automation less helpful. Will need to do some redirection. That is, from the log-in to each customer's user panel and from there redirect them to the machine their server is located on so the customer can make changes to his/her server. Also, when ordering I will need to have scripting that will determine which machine to setup on and redirect from there. So the redirection can happen I will need to install and keep updated Apache on every machine, also a big pain considering we plan to have over 20 machines at some point.