QEMU GameZIP Server - Revision history

Coldice2: deprecated

2025-12-28T03:00:09Z

deprecated

← Older revision		Revision as of 05:00, 28 December 2025
Line 1:		Line 1:
			This is a deprecated technology used by Flashpoint 11. In newer version we have replaced this with [[Game Server\|Flashpoint Game Server]].

	The server allows accessing zipped game contents, also known as GameZIPs, as well as merged htdocs.		The server allows accessing zipped game contents, also known as GameZIPs, as well as merged htdocs.
	This page aims to cover the details of the Flashpoint implementation.		This page aims to cover the details of the Flashpoint implementation.
Line 149:		Line 151:
	Your <code>alpine.qcow2</code> image is ready!		Your <code>alpine.qcow2</code> image is ready!

	<noinclude>[[Category:Technologies]]</noinclude>		<noinclude>
			[[Category:Technologies]]
			</noinclude>

Nosamu: Nosamu moved page GameZIP Server to QEMU GameZIP Server: Disambiguating with the new Flashpoint Game Server

2023-10-20T11:10:28Z

Nosamu moved page GameZIP Server to QEMU GameZIP Server: Disambiguating with the new Flashpoint Game Server

← Older revision	Revision as of 13:10, 20 October 2023
(No difference)

Nosamu at 23:16, 29 January 2022

2022-01-29T23:16:26Z

← Older revision		Revision as of 01:16, 30 January 2022
Line 25:		Line 25:
	Here is a high-level overview of how files are served:		Here is a high-level overview of how files are served:

	[[File:Qemu.png]]		[[File:Qemu.png\|800px]]

	And here is a more detailed look at how the GameZip server works:		And here is a more detailed look at how the GameZip server works:

Nosamu: Added new diagram from XXLM

2022-01-29T23:15:26Z

Added new diagram from XXLM

← Older revision		Revision as of 01:15, 30 January 2022
Line 22:		Line 22:

	== How does it work? ==		== How does it work? ==

			Here is a high-level overview of how files are served:

			[[File:Qemu.png]]

			And here is a more detailed look at how the GameZip server works:

	[[File:QEMU-FP.png]]		[[File:QEMU-FP.png]]

XXLuigiMario at 14:08, 18 May 2021

2021-05-18T14:08:48Z

← Older revision		Revision as of 16:08, 18 May 2021
Line 137:		Line 137:
	qemu-system-i386 -m 512 -net nic,model=e1000 -net user -hda alpine.qcow2		qemu-system-i386 -m 512 -net nic,model=e1000 -net user -hda alpine.qcow2
	* Run the following commands (on the guest)		* Run the following commands (on the guest)
	~~modprobe fuse~~
	~~unionfs /root/base /var/www/localhost/htdocs -o allow_other~~
	clear		clear
	tail -f /var/log/apache2/access.log >/dev/ttyS0		tail -f /var/log/apache2/access.log >/dev/ttyS0

XXLuigiMario at 14:07, 18 May 2021

2021-05-18T14:07:53Z

← Older revision		Revision as of 16:07, 18 May 2021
Line 53:		Line 53:

	1. Finds the attached block device with the specified serial.		1. Finds the attached block device with the specified serial.

	If no device was found with this serial, it checks again once every 100 ms.		If no device was found with this serial, it checks again once every 100 ms.
	If no matching device was found after 10 seconds, "NO_SUCH_FILE" is returned.		If no matching device was found after 10 seconds, "NO_SUCH_FILE" is returned.

	2. A symbolic link is created from <code>/dev/[device]</code> to <code>/tmp/[device].zip</code>		2. A symbolic link is created from <code>/dev/[device]</code> to <code>/tmp/[device].zip</code>

	This is done in order to trick AVFS into thinking that the block device is a regular ZIP file.		This is done in order to trick AVFS into thinking that the block device is a regular ZIP file.
	AVFS can transparently access ZIP files as a folder by appending a pound sign after the filename.		AVFS can transparently access ZIP files as a folder by appending a pound sign after the filename.
Line 62:		Line 64:

	3. Mounts <code>/root/.avfs/tmp/[device].zip#</code> to <code>/tmp/[device]</code> as a case-insensitive mirror using fuzzyfs		3. Mounts <code>/root/.avfs/tmp/[device].zip#</code> to <code>/tmp/[device]</code> as a case-insensitive mirror using fuzzyfs

	fuzzyfs is a read-only filesystem that allows case-insensitive access to files.		fuzzyfs is a read-only filesystem that allows case-insensitive access to files.

	4. Adds <code>/tmp/[device]/content</code> to the union mount.		4. Adds <code>/tmp/[device]/content</code> to the union mount.

	This is done by unmounting <code>/var/www/localhost/htdocs</code> then re-mounting with a new set of settings.		This is done by unmounting <code>/var/www/localhost/htdocs</code> then re-mounting with a new set of settings.

XXLuigiMario at 14:05, 18 May 2021

2021-05-18T14:05:31Z

← Older revision		Revision as of 16:05, 18 May 2021
Line 14:		Line 14:
	The GameZIP implementation still uses Apache but it runs on Alpine Linux instead. This allows the use of FUSE file systems to achieve a simulated view of "merged htdocs" without the extraction of GameZIPs.		The GameZIP implementation still uses Apache but it runs on Alpine Linux instead. This allows the use of FUSE file systems to achieve a simulated view of "merged htdocs" without the extraction of GameZIPs.
	This instance of Alpine Linux is emulated under QEMU. QEMU was chosen because it requires no driver installation or special privileges and Alpine Linux because of its low file size and overhead.		This instance of Alpine Linux is emulated under QEMU. QEMU was chosen because it requires no driver installation or special privileges and Alpine Linux because of its low file size and overhead.
	The Linux guest cannot directly access files on the host file system, ~~so an FTP~~ server ~~runs on the host~~ to ~~share needed~~ files.		The Linux guest cannot directly access files on the host file system, instead, when a file lookup fails, the request is proxied to a fallback server to allow loading files for Legacy games. This is the Legacy Apache server in the case of Flashpoint Ultimate or the PHP router in the case of Flashpoint Infinity.

	=== Why emulate Linux? ===		=== Why emulate Linux? ===
Line 28:		Line 28:
	This path is the target of a union mount, which merges the following paths:		This path is the target of a union mount, which merges the following paths:
	* /root/base: Contains the PHP scripts required for mounting game ZIPs and the <code>.htaccess</code> that rewrites the HTTP Host header into a subfolder.		* /root/base: Contains the PHP scripts required for mounting game ZIPs and the <code>.htaccess</code> that rewrites the HTTP Host header into a subfolder.
	* /tmp/~~htdocs: (Initially unmounted) Contains the contents of the existing merged htdocs, for non-GameZIP games.~~		* /tmp/<code>[device]</code>: (Initially unmounted) Contains the contents of a single GameZIP.
	* /tmp/_<code>[~~game~~]</code>~~.zip~~: (Initially unmounted) Contains the contents of a single GameZIP.

	When the emulated Alpine Linux instance starts, only <code>/root/base</code> is part of the union.		When the emulated Alpine Linux instance starts, only <code>/root/base</code> is part of the union.
Line 37:		Line 36:
	The scripts found in <code>/root/base</code> make up the API used for controlling the union mount.		The scripts found in <code>/root/base</code> make up the API used for controlling the union mount.

	* [GET] <code>http://127.0.0.1:22500/~~wake~~.php</code>		* [GET] <code>http://127.0.0.1:22500/mount.php?file=[device_serial_code]</code>

	~~This endpoint must receive a request at least once before games in the old htdocs folder can be played. The launcher should send a request to it on startup.~~		This endpoint allows mounting a game ZIP from an attached block device into the virtual htdocs.

	~~This performs the following actions:~~

	~~1. Mounts <code>Server\htdocs</code> from Flashpoint into <code>/mnt/htdocs</code> via FTP (using curlftpfs)~~

	~~2. Mounts <code>Games</code> from Flashpoint into <code>/mnt/games</code> via FTP (using curlftpfs)~~

	~~3. Mounts <code>/mnt/htdocs</code> into <code>/tmp/htdocs</code> as a case-insensitive mirror (using fuzzyfs)~~

	~~4. Adds <code>/tmp/htdocs</code> to the union mount.~~

	* [GET] <code>http://127.0.0.1:22500/mount.php?file=[filename]</code>

	This endpoint allows mounting a game ZIP ~~file~~ into the virtual htdocs~~. The specified file must be located in the Games folder under the Flashpoint directory~~.
	It has a few possible outcomes which it will print in plain text:		It has a few possible outcomes which it will print in plain text:
	“OK” (200): The file was mounted successfully.		“OK” (200): The file was mounted successfully.
Line 67:		Line 52:
	This performs the following actions:		This performs the following actions:

	1. If ~~<code>wake~~.~~php</code> has not run yet. It will run first~~.		1. Finds the attached block device with the specified serial.
			If no device was found with this serial, it checks again once every 100 ms.
			If no matching device was found after 10 seconds, "NO_SUCH_FILE" is returned.

	2. ~~Mounts~~ <code>/~~mnt/games~~/[~~filename~~]</code> to <code>/tmp/[~~filename~~]</code> as a ZIP file ~~(using fuse-zip)~~		2. A symbolic link is created from <code>/dev/[device]</code> to <code>/tmp/[device].zip</code>
			This is done in order to trick AVFS into thinking that the block device is a regular ZIP file.
			AVFS can transparently access ZIP files as a folder by appending a pound sign after the filename.
			An AVFS mount of the root directory exists in <code>/root/.avfs</code>

	3. Mounts <code>/tmp/[~~filename~~]</code> to <code>/tmp/_[~~filename~~]</code> as a case-insensitive mirror (using fuzzyfs)		3. Mounts <code>/root/.avfs/tmp/[device].zip#</code> to <code>/tmp/[device]</code> as a case-insensitive mirror using fuzzyfs
			fuzzyfs is a read-only filesystem that allows case-insensitive access to files.

	4. Adds <code>/tmp/_[~~filename~~]</code> to the union mount.		4. Adds <code>/tmp/[device]/content</code> to the union mount.
			This is done by unmounting <code>/var/www/localhost/htdocs</code> then re-mounting with a new set of settings.

	=== Shell access ===		=== Shell access ===

Prostagma: category

2021-01-22T02:06:10Z

XXLuigiMario at 13:31, 21 September 2020

2020-09-21T13:31:31Z

← Older revision		Revision as of 15:31, 21 September 2020
Line 121:		Line 121:

	* Boot the machine		* Boot the machine
	qemu-system-i386 -m 512 -net nic,model=e1000 -net user~~,hostfwd=tcp::22500-:80~~ -hda alpine.qcow2		qemu-system-i386 -m 512 -net nic,model=e1000 -net user -hda alpine.qcow2
	* Run the setup script (on the guest)		* Run the setup script (on the guest)
	cd /tmp		cd /tmp
Line 139:		Line 139:
	Finally, we need to set up our special save state to resume execution from.		Finally, we need to set up our special save state to resume execution from.
	* Boot the machine		* Boot the machine
	qemu-system-i386 -m 512 -net nic,model=e1000 -net user~~,hostfwd=tcp::22500-:80~~ -hda alpine.qcow2		qemu-system-i386 -m 512 -net nic,model=e1000 -net user -hda alpine.qcow2
	* Run the following commands (on the guest)		* Run the following commands (on the guest)
	modprobe fuse		modprobe fuse

XXLuigiMario at 13:29, 21 September 2020

2020-09-21T13:29:59Z

← Older revision		Revision as of 15:29, 21 September 2020
Line 120:		Line 120:
	=== Setting up the Flashpoint toolchain ===		=== Setting up the Flashpoint toolchain ===

	* Copy the PHP scripts/.htaccess that will be placed in <code>/root/base</code> to <code>Server\htdocs\base</code>
	* Run Flashpoint Launcher (this will start the FTP server which allows access to the PHP scripts)
	* Boot the machine		* Boot the machine
	qemu-system-i386 -m 512 -net nic,model=e1000 -net user,hostfwd=tcp::22500-:80 -hda alpine.qcow2		qemu-system-i386 -m 512 -net nic,model=e1000 -net user,hostfwd=tcp::22500-:80 -hda alpine.qcow2
	* Run the setup script (on the guest)		* Run the setup script (on the guest)
	cd /tmp		cd /tmp
	wget https://~~tinyurl~~.~~com~~/~~setfpup~~ -O setup		wget https://go.nul.sh/fpultimate -O setup
	chmod +x setup		chmod +x setup
	./setup		./setup
			For Infinity use: https://go.nul.sh/fpinfinity
	* Clean up <code>/tmp</code> and power off the machine (on the guest)		* Clean up <code>/tmp</code> and power off the machine (on the guest)
	rm -r /tmp/*		rm -r /tmp/*

← Older revision		Revision as of 04:06, 22 January 2021
Line 148:		Line 148:

	Your <code>alpine.qcow2</code> image is ready!		Your <code>alpine.qcow2</code> image is ready!

			<noinclude>[[Category:Technologies]]</noinclude>