User:Gajop - Revision history

Gajop: /* Launcher Distribution System (WIP) */

2017-12-26T03:50:50Z

Launcher Distribution System (WIP)

← Older revision		Revision as of 04:50, 26 December 2017
Line 17:		Line 17:

	To use it, developers need to do two things:		To use it, developers need to do two things:

	1. Register at $SITE and submit a link to their Git repository (e.g. https://github.com/Spring-SpringBoard/SpringBoard-Core.git). The Git repository can be the same as the game repository, but can also be separate.		1. Register at $SITE and submit a link to their Git repository (e.g. https://github.com/Spring-SpringBoard/SpringBoard-Core.git). The Git repository can be the same as the game repository, but can also be separate.

	2. Put distribution files in the <code>dist</code> folder of the repository. This includes configuration, launcher media files and additional custom scripts.		2. Put distribution files in the <code>dist</code> folder of the repository. This includes configuration, launcher media files and additional custom scripts.

	How it works:		How it works:

	1. Users first submit Git repositories, which might need approval. (Approval could only be necessary if launchers require custom scripts).		1. Users first submit Git repositories, which might need approval. (Approval could only be necessary if launchers require custom scripts).

	2. A script will update all Git repositories, similar how it does for Rapid. It will only extract the <code>dist</code> subfolder.		2. A script will update all Git repositories, similar how it does for Rapid. It will only extract the <code>dist</code> subfolder.

	3. It will send the dist subfolder to buildbots (or they might poll it), which will create launchers from it. Each buildbot runs a specific setup (e.g. Linux64, Windows32, etc.)		3. It will send the dist subfolder to buildbots (or they might poll it), which will create launchers from it. Each buildbot runs a specific setup (e.g. Linux64, Windows32, etc.)

	4. Buildbots will take the dist subfolder, and put it in the latest version of the launcher (which will be periodically cloned), and start the build. They will then send the built files and patches (?) to the server for distribution.		4. Buildbots will take the dist subfolder, and put it in the latest version of the launcher (which will be periodically cloned), and start the build. They will then send the built files and patches (?) to the server for distribution.

	5. Once the server receives the built files, it will put it in a folder specific to the game. Each game will have its own launcher, with a versioning scheme similar to Rapid and/or the engine (Git names + custom names for tags like stable).		5. Once the server receives the built files, it will put it in a folder specific to the game. Each game will have its own launcher, with a versioning scheme similar to Rapid and/or the engine (Git names + custom names for tags like stable).

	6. The launcher program will update using pyupdater.		6. The launcher program will update using pyupdater.

	7. To get the latest version of the launcher, devs will need to update their Git repositories. Optionally allow devs to specify custom launcher versions (but seems unnecessary as we don't want to overcomplicate things).		7. To get the latest version of the launcher, devs will need to update their Git repositories. Optionally allow devs to specify custom launcher versions (but seems unnecessary as we don't want to overcomplicate things).


	WIP: Better term than buildbot?		WIP: Better term than buildbot?

Gajop: outline of the launcher distribution system (wip)

2017-12-26T03:50:25Z

outline of the launcher distribution system (wip)

← Older revision		Revision as of 04:50, 26 December 2017
Line 1:		Line 1:
	https://github.com/gajop		https://github.com/gajop

			= Gamedev:Distribution =

			Explain Rapid
			[[Rapid]]

			Explain Launcher distribution

			= Launcher Distribution System (WIP) =

			In SpringRTS it is currently difficult to distribute your games. Developers normally need to create their own tools that will auto-update and launch the lobby, game and all additional assets. They also need to host it on their own site, which usually inflicts an initial cost.

			This is quite unfortunate as we already have [[Rapid]], which is a powerful system for distributing games on an existing Spring installation. However, this system lacks a way to distribute the game installation, and it doesn't allow games to provide customized launchers.

			This is why we have created the launcher distribution system. It is based on simple distribution system similar to how Rapid works, where the distribution setup is contained within a Git repository.

			To use it, developers need to do two things:
			1. Register at $SITE and submit a link to their Git repository (e.g. https://github.com/Spring-SpringBoard/SpringBoard-Core.git). The Git repository can be the same as the game repository, but can also be separate.
			2. Put distribution files in the <code>dist</code> folder of the repository. This includes configuration, launcher media files and additional custom scripts.

			How it works:
			1. Users first submit Git repositories, which might need approval. (Approval could only be necessary if launchers require custom scripts).
			2. A script will update all Git repositories, similar how it does for Rapid. It will only extract the <code>dist</code> subfolder.
			3. It will send the dist subfolder to buildbots (or they might poll it), which will create launchers from it. Each buildbot runs a specific setup (e.g. Linux64, Windows32, etc.)
			4. Buildbots will take the dist subfolder, and put it in the latest version of the launcher (which will be periodically cloned), and start the build. They will then send the built files and patches (?) to the server for distribution.
			5. Once the server receives the built files, it will put it in a folder specific to the game. Each game will have its own launcher, with a versioning scheme similar to Rapid and/or the engine (Git names + custom names for tags like stable).
			6. The launcher program will update using pyupdater.
			7. To get the latest version of the launcher, devs will need to update their Git repositories. Optionally allow devs to specify custom launcher versions (but seems unnecessary as we don't want to overcomplicate things).

			WIP: Better term than buildbot?

Gajop: Created page with "https://github.com/gajop"

2016-03-04T08:22:41Z

Created page with "https://github.com/gajop"

New page

https://github.com/gajop