Testserver with shared database: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Hendrik Brummermann |
imported>Hendrik Brummermann configure marauroa |
||
| Line 10: | Line 10: | ||
The complex way allows players to test with their own account and characters, while doing smart things with the logs. The login events will be logged to the original database so that the number of wrong password tries sums up both databases. The Stendhal website displays a login history covering all sources: website, main server and test server. The gameEvents and itemlog tables will be kept for the analysis of bugs. |
The complex way allows players to test with their own account and characters, while doing smart things with the logs. The login events will be logged to the original database so that the number of wrong password tries sums up both databases. The Stendhal website displays a login history covering all sources: website, main server and test server. The gameEvents and itemlog tables will be kept for the analysis of bugs. |
||
| ⚫ | |||
Configure the test server just like a normal server with its own database. |
|||
Then you need to change disable account and character creations. It is essential that those are only created on the main server in order to ensure a consistent database. And you may want to add a big hint, telling players that this is a test server: |
|||
allow_account_creation=false |
|||
allow_character_creation=false |
|||
server_welcome=Please note: The test database will be reset every day and all PROGRESS WILL BE LOST. |
|||
=== Setup test database === |
=== Setup test database === |
||
| Line 29: | Line 40: | ||
CREATE VIEW loginEvent AS SELECT * FROM marauroa.loginEvent; |
CREATE VIEW loginEvent AS SELECT * FROM marauroa.loginEvent; |
||
</source> |
</source> |
||
| ⚫ | |||
{{TODO|describe marauroa setup}} |
|||
=== Nightly update script === |
=== Nightly update script === |
||