Can be done without mysql or any sql too. Prism is both the insim controller and the webserver (or data provider for some external script or application), so you don't need any storage in between.

Might be worth adding /reinit to the admin flags.

Quote from franky500 :

Is that the imput you were looking for? bear in mode that none of this is of any use to a hoster unless the end user can access the setting changes either via a program on their own PC (which i assume is where you are going based on it being an insim app) or via a web page.

There is currently in game access via prefix chat commands, via the "/i" interface, and via the "/o" options command. Outside of the game remote console rights are given to admins who have the ADMIN_RCON flag, and can then telnet into the server, and issue commands directly. And we lastly have the Web Interface that Vics working on. This is of course besides the PRISM console itselfs that allows for keyboard input directly into the program (only on linux, windows user have to back telnet into their own console).

Quote from franky500 :

Assuming it was released under terms that would allow it, i would probably go as far as modifying it to contain a file management system of some kind and make it a main host setup page.

Quote from Victor :

the license atm is the MIT one, so you can pretty much do whatever with it.

Picked by the community, MIT came out on top. Could not be happier with that result as I voted for it as well and I said all along thats what I had hoped for. So yes, you can do anything you want with the PRISM source code.

Quote from franky500 :

The one thing that i would like to be added to such a program would be the ability for users to send (and ideally read) messages and commands to the system from the web-admin page.

Quote from Victor :

As for the admin pages part - I'm thinking of a way to have (almost) regular php files for the admin pages, thereby making it fairly easy for anyone to adjust the admin pages to their needs. So you could easily add additional functionality.

Yes, you can do that four ways. Add the user to the users.ini file, and issue the "!prism admin reload" command or restart the server. In server "!prism add admin <username> <accessflags>" (doing "!prism add admin" will bring up a button interface for adding admins based on the current players in the server and your admin level.), adding them via the web interface. Adding them by the PRISM / remote telnet console. Some of this has be implemented some of this has not. All of what's needed should be there by the time we get to 0.6.0 (pretty far into the future.)

Quote from franky500 :

/me subscribes to thread, Let me know if you need any imput or testing.

Great, I can't wait for more input.

Quote from Victor :

First let's get the actual functionality in prism I think it'll be a while before that's there.

Yeah, so much to do, so little time!

Quote from Fire_optikz001 :

i think this could be done, where when it puts a message in the console it also adds it to a MYSQL database -> then output it on a web page which also has a form that you can enter what you want into the console(and mysql) :P just a thought ... dont know if it would fully work though

Quote from Victor :

Can be done without mysql or any sql too. Prism is both the insim controller and the webserver (or data provider for some external script or application), so you don't need any storage in between.

As long as JavaScript can listen, we can just push the updated information into the client's page. Every time we get a message packet, we forward that to the admins page.

Quote from the_angry_angel :

Might be worth adding /reinit to the admin flags.

Yeah, that's a reallly good idea. Along with a flag for allowing one admin to make another. (But can only grant up to the powers that he has.)

• ADMIN_ACCESS; Flag "a" - Allows you to issue commands from the remote console or web admin area.
  
• ADMIN_BAN; Flag "b" - Allows you to ban and unban clients.
  • /ban X Y ban user X for Y days (0 = 12 hours)
    
  • /unban X remove ban on user X
    
• ADMIN_CFG; Flag "c" - Allows you to change the, runtime, configuration of LFS.
  • /host= set the host name of the server
    
  • /pass= if required - password
    
  • /admin= if required - admin password
    
    
  • /ip= if required - local specified ip address
    
  • /port= a high number below 65536
    
  • /mode= demo / s1 / s2
    
  • /usemaster= no / yes / hidden
    
    
  • /maxguests max number of guests that can join host
    
  • /adminslots slots reserved for admins (0 to 8)
    
  • /carsmax max number of cars in a race
    
  • /carshost max number of cars (real+ai) on host pc
    
  • /carsguest max number of cars (real+ai) per guest pc
    
  • /pps smoothness (3-6) number of car updates per second
    
    
  • /dedicated= no / yes / nogfx / invisible
    
    
  • /select no / yes (guests select track)
    
  • /rstmin no restart for X seconds after race start
    
  • /rstend no restart for X seconds after race finish
    
  • /autokick no / kick / ban / spec (wrong way drivers)
    
    
  • /insim= listen for InSim (PORT is between 1 and 65535)
    
  • /windowed= no / yes - overrides the cfg.txt setting
    
  • /welcome= set welcome text file
    
    
  • /midrace no / yes (join during race)
    
  • /mustpit no / yes (pit stop required)
    
  • /canreset no / yes (allow car reset)
    
  • /fcv no / yes (force cockpit view)
    
  • /cruise no / yes (allow wrong way)
    
  • /start fixed/finish/reverse/random (default race start)
    
  • /pass set new password (BLANK = no password)
    
  • /cars see below : "Car Strings"
    
  • /welcome set welcome text file
    
  • /tracks set list of allowed tracks
    
  • /log= set message log file
    
  • /hlog set message log file on host
    
  • /ndebug no / yes (network debug)
    
  • /autosave MPR autosave (0-no / 1-manual / 2-auto)
    
  • /mprdir= set the data folder for mpr saving
    
  • /save_mpr save MPR with name X (autosave must be 1 or 2)
    
  • /lytdir= set the data folder for layouts
    
• ADMIN_CVAR; Flag "d" - Allows you to change the, runtime, configuration of PRISM.
  
• ADMIN_LEVEL_E; Flag "e" -
  
• ADMIN_LEVEL_F; Flag "f" -
  
• ADMIN_GAME; Flag "g" - Allows you to change the way the game is played.
  • /qual= qualifying minutes, 0 for no qualifying
    
  • /laps= number of lap, 0 for practice
    
  • /wind= 0 no wind / 1 low wind / 2 high wind
    
  • /midrace= no / yes (join during race)
    
  • /mustpit= no / yes (pit stop required)
    
  • /canreset= no / yes (allow car reset)
    
  • /fcv= no / yes (force cockpit view)
    
  • /cruise= no / yes (allow wrong way)
    
  • /start= fixed/finish/reverse/random (default race start)
    
  • /wind= no / yes : can guests vote to kick or ban
    Autocross layout commands :
    • /axlist get list of layouts for track X - e.g. AU1
      
    • /axload load layout X on host
      
    • /axsave save layout X on host
      
    • /axlaps set autocross number of laps
      
    • /axclear clear layout
      
• ADMIN_HOST; Flag "h" - Allows you to change the way the host runs.
  • Simple commands with no parameter :
    • /restart start a race
      
    • /qualify start qualifying
      
    • /end return to game setup screen
      
    • /reinit total restart (removes all connections)
      
    • /clear clear all racers from list
      
  • /weather= weather : 1,2,3 in Blackwood
    
  • /cars= see below : "Car Strings"
    
• ADMIN_IMMUNITY; Flag "i" - Immunity (can't be kicked/baned/speced/pited and affected by other commmands)
  
• ADMIN_LEVEL_J; Flag "j" -
  
• ADMIN_KICK; Flag "k" - Allows admin to kick clients from server.
  • /kick disconnect user
    
• ADMIN_LEVEL_L; Flag "l" -
  
• ADMIN_MAP; Flag "m" - Allows you to change the map (track) on the server.
  • /track= track and config (e.g. BL1 / SO3R / FE4)
    
  • /tracks= set list of allowed tracks
    
• ADMIN_LEVEL_N; Flag "n" -
  
• ADMIN_LEVEL_O; Flag "o" -
  
• ADMIN_PENALTIES; Flag "p" - Allows you to set a penalty on any client.
  • /p_dt give drive through penalty
    
  • /p_sg give stop-go penalty
    
  • /p_30 give 30 second time penalty
    
  • /p_45 give 45 second time penalty
    
  • /p_clear clear a time or pit penalty
    
• ADMIN_RESERVATION; Flag "q" - Allows you to join in a reserved slot.
  
• ADMIN_RCM; Flag "r" - Allows you to send Race Control Messages.
  • /rcm set a Race Control Message to be sent
    
  • /rcm_ply send the RCM to USERNAME
    
  • /rcm_all send the RCM to all
    
  • /rcc_ply clear USERNAME's RCM
    
  • /rcc_all clear all RCMs
    
• ADMIN_SPECTATE; Flag "s" - Allows you to spectate and pit a client or all clients.
  • /spec make user X join the spectators
    
  • /pitlane send user X to the pit lane
    
  • /pit_all send all cars to the pit lane
    
• ADMIN_CHAT; Flag "t" - Allows you to send messages to clients in their chat area.
  • /msg send system message
    
• ADMIN_UNIMMUNIZE; Flag "u" - Allows you to run commands on immune admins also.
  
• ADMIN_VOTE; Flag "v" - Allows you to start votes for anything.
  • /vote= no / yes : can guests vote to kick or ban
    
• ADMIN_LEVEL_W; Flag "w" -
  
• ADMIN_LEVEL_X; Flag "x" -
  
• ADMIN_LEVEL_Y; Flag "y" -
  
• ADMIN_LEVEL_Z; Flag "z" -
  

Take a look over the list and let me know what commands should be moved into other levels, or what should be moved into their own levels. I'm thinking of putting track into it's own level and anything to do with tracks. Also thinking about setting cars with it's own admin level. What do you think?

Quote from Dygear :

I'm thinking of putting track into it's own level and anything to do with tracks. Also thinking about setting cars with it's own admin level. What do you think?

that sounds good