Development:Network:Todo - Revision history

Eye~r: /* Vegaserver: */

2015-06-12T16:14:48Z

‎Vegaserver:

Eye~r: /* Vegaserver: */

2015-06-12T16:13:18Z

‎Vegaserver:

Eye~r: /* Website: */

2015-06-12T16:01:37Z

‎Website:

Eye~r: /* User control interface */

2015-06-12T15:54:07Z

‎User control interface

Eye~r: /* User control interface */

2015-06-12T15:51:44Z

‎User control interface

Eye~r: /* DataBase: */

2015-06-12T15:50:05Z

‎DataBase:

Eye~r: /* Markets: */

2015-06-12T15:47:40Z

‎Markets:

Eye~r: /* Markets: */

2015-06-12T15:46:39Z

‎Markets:

Eye~r: /* NEW : DATABASE FOR ACCOUNT SERVER */

2015-06-12T15:44:06Z

‎NEW : DATABASE FOR ACCOUNT SERVER

Eye~r: /* NEW : DATABASE FOR ACCOUNT SERVER */

2015-06-12T15:40:41Z

‎NEW : DATABASE FOR ACCOUNT SERVER

@@ Line 27: / Line 27: @@
 * Fix owning >1 ship = player dies (workaround via PHP implemented)
-* Parse user input for sanity in httpserver.py ( as workaround .py isolated from public, signup offered via PHP)
+* Parse user input for sanity in httpserver.py ( as workaround .py isolated from public, [http://vegastrike.armed.me.uk/signup.php signup offered via PHP])
 ** Currently when a 'tard tries to use it as a proxy server it crashes it.

@@ Line 32: / Line 32: @@
 * Needs admin commands:
 ** lacking ability for systems administration or faction/clan administration. see below.
 * Needs Communications:

@@ Line 57: / Line 57: @@
 **
 * Buy ship workaround
-** fully functional
+** fully functional [http://vegastrike.armed.me.uk/test/usership4.php User Ship Adjustment Form]
 == Admin control interface ==

@@ Line 81: / Line 81: @@
 *Ability to maintain friends/contacts.
 **Considered to implement in here as a workaround to being unable to add functionality to vegaserver(At this time):
-***Ability to adjust current ship. '''Implemented'''
+***Ability to adjust current ship. '''Implemented.'''[http://vegastrike.armed.me.uk/test/usership4.php Ship Adjustment Form]
 ***Ability to adjust faction aligence.

@@ Line 81: / Line 81: @@
 *Ability to maintain friends/contacts.
 **Considered to implement in here as a workaround to being unable to add functionality to vegaserver(At this time):
-***Ability to adjust current ship.
+***Ability to adjust current ship. '''Implemented'''
 ***Ability to adjust faction aligence.

@@ Line 88: / Line 88: @@
 *Bases table
+** to provide for what factions/individuals hold what resources and their production queues
 *account table

@@ Line 107: / Line 107: @@
 *Create sensible "production Tree"
 ** Work started. Multiplayer editing possible via: [http://morrigan.armed.me.uk:9001/p/Vegastrike Parts list in etherpad]
 == NEW : DATABASE FOR ACCOUNT SERVER ==

@@ Line 110: / Line 110: @@
 == NEW : DATABASE FOR ACCOUNT SERVER ==
-Current:
+Current:<br />
 To setup a working vegastrike server with SQL backend you will require two tables in the database, user_table and account_table - formatted thusly:<br />
 *user_table
 +---------------+-------------+------+-----+---------+----------------+<br />
-| Field         | Type        | Null | Key | Default | Extra          |<br />
+<nowiki>| Field         | Type        | Null | Key | Default | Extra          |</nowiki><br />
 +---------------+-------------+------+-----+---------+----------------+<br />
 | username      | varchar(20) | YES  | UNI | NULL    |                |<br />

@@ Line 111: / Line 111: @@
 == NEW : DATABASE FOR ACCOUNT SERVER ==
 Current:
-* To setup a working vegastrike server with SQL backend you will require two tables in the database, user_table and account_table - formatted thusly:
+To setup a working vegastrike server with SQL backend you will require two tables in the database, user_table and account_table - formatted thusly:<br />
+*user_table
++---------------+-------------+------+-----+---------+----------------+<br />
-<nowiki>+---------------+-----------------+------+-----+-----------+-------+
+| Field         | Type        | Null | Key | Default | Extra          |<br />
-| Field | Type | Null | Key | Default | Extra |
++---------------+-------------+------+-----+---------+----------------+<br />
-+---------------+-----------------+------+-----+-----------+-------+
+| username      | varchar(20) | YES  | UNI | NULL    |                |<br />
-| username | varchar(20) | YES | | NULL | |
+| user_id       | int(10)     | NO   | PRI | NULL    | auto_increment |<br />
-| user_id | varchar(20) | YES | PRI | NULL | Auto-Increment |
+| user_password | varchar(50) | YES  |     | NULL    |                |<br />
-| user_password | varchar(50)| YES | | NULL | |
++---------------+-------------+------+-----+---------+----------------+<br />
-+---------------+-------------+------+-----+---------+-------+</nowiki>
+*account_table
++------------------+-------------+------+-----+---------+-------+<br />
-<nowiki>+------------------+-------------+------+-----+---------+-------+
+| Field            | Type        | Null | Key | Default | Extra |<br />
-| Field            | Type        | Null | Key | Default | Extra |
++------------------+-------------+------+-----+---------+-------+<br />
-+------------------+-------------+------+-----+---------+-------+
+| username         | varchar(20) | YES  |     | NULL    |       |<br />
-| username         | varchar(20) | YES  |     | NULL    |       |
+| modname          | varchar(20) | YES  |     | NULL    |       |<br />
-| modname          | varchar(20) | YES  |     | NULL    |       |
+| csv              | mediumtext  | YES  |     | NULL    |       |<br />
-| csv              | mediumtext  | YES  |     | NULL    |       |
+| savegame         | mediumtext  | YES  |     | NULL    |       |<br />
-| savegame         | mediumtext  | YES  |     | NULL    |       |
++------------------+-------------+------+-----+---------+-------+<br />
-+------------------+-------------+------+-----+---------+-------+</nowiki>
+<br />
 Proposed: