Studio back-office - Sejarah semakan

Sourisdudesert pada 08:54, 16 Oktober 2013

2013-10-16T08:54:43Z

← Semakan terdahulu		Semakan pada 10:54, 16 Oktober 2013
Baris 1:		Baris 1:
			'''IMPORTANT''': the Studio back-office is now '''DEPRECATED'''. Most of its functionalities are now accessible from "Control Panel / Manage Games / Your games".




	You will find the URL to the Studio back-office in the 'resources.html' file at the root of your SFTP access.		You will find the URL to the Studio back-office in the 'resources.html' file at the root of your SFTP access.

Baris 14:		Baris 19:

	Your login / password for this tool is the same as for your SFTP access.		Your login / password for this tool is the same as for your SFTP access.

			('''DEPRECATED''': now you can access to your game database with the link "Game Database" at the bottom of your game page).

	=== Sources ===		=== Sources ===
Baris 22:		Baris 29:

	You should commit from time to time when you hit some landmarks in your development. This is an extra assurance not to lose your code, and to have the possibility (by asking BGA administrators) to get a previous version of your code if you need to backtrack.		You should commit from time to time when you hit some landmarks in your development. This is an extra assurance not to lose your code, and to have the possibility (by asking BGA administrators) to get a previous version of your code if you need to backtrack.

			('''DEPRECATED''': now this function is available from your Control Panel).

	=== Logs ===		=== Logs ===
Baris 29:		Baris 38:
	; Current table error log		; Current table error log
	: main log of interest to you while developing, it contains the error happening at the table you are currently playing at.		: main log of interest to you while developing, it contains the error happening at the table you are currently playing at.
			('''DEPRECATED''': now you can access this log with the coreesponding link at the bottom of your game page).
	; Current table request logs		; Current table request logs
	: this log traces all the actions happening at the table you are currently playing at.		: this log traces all the actions happening at the table you are currently playing at.
			('''DEPRECATED''': now you can access this log with the coreesponding link at the bottom of your game page).
	; Javascript error log		; Javascript error log
	: this log traces all the Javascript errors happening on the client side. Errors are also briefly displayed in your browser, but in this log it's better formatted and you can look a it quietly.		: this log traces all the Javascript errors happening on the client side. Errors are also briefly displayed in your browser, but in this log it's better formatted and you can look a it quietly.
			('''DEPRECATED''': you should use your Javascript console / Firebug plugin to do this).
	; Gameserver error log		; Gameserver error log
	: this log traces all errors happening on the gameserver. It should mainly be useful if your game setup crashes (ie before your table is ready, so before errors are collected in the current table error log), for example if there is a syntax error in your 'dbmodel.sql' file.		: this log traces all errors happening on the gameserver. It should mainly be useful if your game setup crashes (ie before your table is ready, so before errors are collected in the current table error log), for example if there is a syntax error in your 'dbmodel.sql' file.
			('''DEPRECATED''': errors during the game setup appears now directly in a red error message during your "Express start").
	; HTTP error log		; HTTP error log
	: this log traces the web server errors. This is useful to look at PHP syntax errors and warnings.		: this log traces the web server errors. This is useful to look at PHP syntax errors and warnings.
			('''DEPRECATED''': errors now appear directly in a red message during the game).

	Please note that the three last logs are common to all games being developed on the platform, so there may be some noise in the data you are interested in.		Please note that the three last logs are common to all games being developed on the platform, so there may be some noise in the data you are interested in.

	You can open the log links in a different tab and just hit F5 when you need to refresh. The URL you will get for the new tab has a "?n=100" parameter that gives the number of lines to display: you can modify it in the URL if you need more.		You can open the log links in a different tab and just hit F5 when you need to refresh. The URL you will get for the new tab has a "?n=100" parameter that gives the number of lines to display: you can modify it in the URL if you need more.

Een: /* Sources */

2012-12-06T21:43:49Z

Sources

← Semakan terdahulu		Semakan pada 23:43, 6 Disember 2012
Baris 18:		Baris 18:

	Contains a form for committing your sources to the BGA repository.		Contains a form for committing your sources to the BGA repository.
	* Game name field should contain the name of your game (lower case, no space).		* Game name field should contain the name of your game (lower case, no space). Ex: puertorico
	* Comment field should contain your commit comment describing changes to the code since your last commit.		* Comment field should contain your commit comment describing changes to the code since your last commit.

Een pada 20:51, 27 November 2012

2012-11-27T20:51:22Z

← Semakan terdahulu		Semakan pada 22:51, 27 November 2012
Baris 20:		Baris 20:
	* Game name field should contain the name of your game (lower case, no space).		* Game name field should contain the name of your game (lower case, no space).
	* Comment field should contain your commit comment describing changes to the code since your last commit.		* Comment field should contain your commit comment describing changes to the code since your last commit.


	You should commit from time to time when you hit some landmarks in your development. This is an extra assurance not to lose your code, and to have the possibility (by asking BGA administrators) to get a previous version of your code if you need to backtrack.		You should commit from time to time when you hit some landmarks in your development. This is an extra assurance not to lose your code, and to have the possibility (by asking BGA administrators) to get a previous version of your code if you need to backtrack.
Baris 27:		Baris 26:

	Gives you a web based access to the studio server logs.		Gives you a web based access to the studio server logs.


	; Current table error log		; Current table error log
Baris 39:		Baris 37:
	; HTTP error log		; HTTP error log
	: this log traces the web server errors. This is useful to look at PHP syntax errors and warnings.		: this log traces the web server errors. This is useful to look at PHP syntax errors and warnings.


	Please note that the three last logs are common to all games being developed on the platform, so there may be some noise in the data you are interested in.		Please note that the three last logs are common to all games being developed on the platform, so there may be some noise in the data you are interested in.

	You can open the log links in a different tab and just hit F5 when you need to refresh. The URL you will get for the new tab has a "?n=100" parameter that gives the number of lines to display: you can modify it in the URL if you need more.		You can open the log links in a different tab and just hit F5 when you need to refresh. The URL you will get for the new tab has a "?n=100" parameter that gives the number of lines to display: you can modify it in the URL if you need more.

Een pada 20:50, 27 November 2012

2012-11-27T20:50:47Z

← Semakan terdahulu		Semakan pada 22:50, 27 November 2012
Baris 27:		Baris 27:

	Gives you a web based access to the studio server logs.		Gives you a web based access to the studio server logs.


	; Current table error log		; Current table error log
Baris 38:		Baris 39:
	; HTTP error log		; HTTP error log
	: this log traces the web server errors. This is useful to look at PHP syntax errors and warnings.		: this log traces the web server errors. This is useful to look at PHP syntax errors and warnings.


	Please note that the three last logs are common to all games being developed on the platform, so there may be some noise in the data you are interested in.		Please note that the three last logs are common to all games being developed on the platform, so there may be some noise in the data you are interested in.

	You can open the log links in a different tab and just hit F5 when you need to refresh. The URL you will get for the new tab has a "?n=100" parameter that gives the number of lines to display: you can modify it in the URL if you need more.		You can open the log links in a different tab and just hit F5 when you need to refresh. The URL you will get for the new tab has a "?n=100" parameter that gives the number of lines to display: you can modify it in the URL if you need more.

Een pada 11:41, 24 November 2012

2012-11-24T11:41:09Z

← Semakan terdahulu		Semakan pada 13:41, 24 November 2012
Baris 12:		Baris 12:

	Contains a link to the Studio database administration tool (PHPMyAdmin).		Contains a link to the Studio database administration tool (PHPMyAdmin).

	Your login / password for this tool is the same as for your SFTP access.		Your login / password for this tool is the same as for your SFTP access.

Baris 17:		Baris 18:

	Contains a form for committing your sources to the BGA repository.		Contains a form for committing your sources to the BGA repository.
	Game name field should contain the name of your game (lower case, no space).		* Game name field should contain the name of your game (lower case, no space).
	Comment should contain your commit comment describing changes to the code since your last commit.		* Comment field should contain your commit comment describing changes to the code since your last commit.


	You should commit from time to time when you hit some landmarks in your development. This is an extra assurance not to lose your code, and to have the possibility (by asking us) to get a previous version of your code if you need to backtrack.		You should commit from time to time when you hit some landmarks in your development. This is an extra assurance not to lose your code, and to have the possibility (by asking BGA administrators) to get a previous version of your code if you need to backtrack.

	=== Logs ===		=== Logs ===
Baris 27:		Baris 29:

	; Current table error log		; Current table error log
	: main log of interest to you while developing, it contains the error ~~logs~~ happening at the table you are currently playing at		: main log of interest to you while developing, it contains the error happening at the table you are currently playing at.
	; Current table request logs		; Current table request logs
	: this log traces all the actions happening at the table you are currently playing at		: this log traces all the actions happening at the table you are currently playing at.
	; Javascript error log		; Javascript error log
	: this log traces all the Javascript errors happening on the client side. Errors are also briefly displayed in your browser, but in this log it's better formatted and you can look a it quietly.		: this log traces all the Javascript errors happening on the client side. Errors are also briefly displayed in your browser, but in this log it's better formatted and you can look a it quietly.

Een: Created page with "You will find the URL to the Studio back-office in the 'resources.html' file at the root of your SFTP access. Here is a list and description of the links and functions in thi..."

2012-11-24T11:38:02Z

Created page with "You will find the URL to the Studio back-office in the 'resources.html' file at the root of your SFTP access. Here is a list and description of the links and functions in thi..."

Laman baru

You will find the URL to the Studio back-office in the 'resources.html' file at the root of your SFTP access.

Here is a list and description of the links and functions in this back-office.

Click on a menu to display its content.

=== Documentation ===

Contains links to this wiki, the development forum and the bugs forum.

=== Database ===

Contains a link to the Studio database administration tool (PHPMyAdmin).
Your login / password for this tool is the same as for your SFTP access.

=== Sources ===

Contains a form for committing your sources to the BGA repository.
Game name field should contain the name of your game (lower case, no space).
Comment should contain your commit comment describing changes to the code since your last commit.

You should commit from time to time when you hit some landmarks in your development. This is an extra assurance not to lose your code, and to have the possibility (by asking us) to get a previous version of your code if you need to backtrack.

=== Logs ===

Gives you a web based access to the studio server logs.

; Current table error log
: main log of interest to you while developing, it contains the error logs happening at the table you are currently playing at
; Current table request logs
: this log traces all the actions happening at the table you are currently playing at
; Javascript error log
: this log traces all the Javascript errors happening on the client side. Errors are also briefly displayed in your browser, but in this log it's better formatted and you can look a it quietly.
; Gameserver error log
: this log traces all errors happening on the gameserver. It should mainly be useful if your game setup crashes (ie before your table is ready, so before errors are collected in the current table error log), for example if there is a syntax error in your 'dbmodel.sql' file.
; HTTP error log
: this log traces the web server errors. This is useful to look at PHP syntax errors and warnings.

Please note that the three last logs are common to all games being developed on the platform, so there may be some noise in the data you are interested in.

You can open the log links in a different tab and just hit F5 when you need to refresh. The URL you will get for the new tab has a "?n=100" parameter that gives the number of lines to display: you can modify it in the URL if you need more.