PSF-LoginServer/docker-compose.yml

services:
  loginserver:
    image: sbtscala/scala-sbt:eclipse-temurin-jammy-8u352-b08_1.8.3_2.13.10
    volumes:
      - .:/PSF-Loginserver:z
    working_dir: /PSF-Loginserver
    depends_on:
      - db
    ports:
      - 51000-51001:51000-51001/udp
      - 51002:51002/tcp
    command: sbt server/run
    environment:
      CONFIG_FORCE_database_host: db
      CONFIG_FORCE_bind: 0.0.0.0
  adminer:
    image: adminer
    ports:
      - 51010:8080
  db:
    image: postgres:14
    ports:
      - 5432:5432
    environment:
      POSTGRES_USER: psforever
      POSTGRES_PASSWORD: psforever
      POSTGRES_DATABASE: psforever
Add docker-compose file (#466) 2020-05-26 20:19:44 +00:00			`services:`
			`loginserver:`
fix docker-compose.yml 2024-04-17 10:55:06 +00:00			`image: sbtscala/scala-sbt:eclipse-temurin-jammy-8u352-b08_1.8.3_2.13.10`
Add docker-compose file (#466) 2020-05-26 20:19:44 +00:00			`volumes:`
			`- .:/PSF-Loginserver:z`
			`working_dir: /PSF-Loginserver`
			`depends_on:`
			`- db`
			`ports:`
			`- 51000-51001:51000-51001/udp`
			`- 51002:51002/tcp`
Networking The game uses a UDP-based protocol. Unlike TCP, UDP does not guarantee that packets arrive, or that they arrive in the correct order. For this reason, the game protocol implements those features using the following: * All packets have a sequence number that is utilized for reordering * Important packets are wrapped in a SlottedMetaPacket with a subslot number * RelatedA packets ae used to request lost packets using the subslot number * RelatedB packets are used to confirm received SlottedMetaPackets All of these go both ways, server <-> client. We used to only partially implement these features: Outgoing packet bundles used SMPs and could be resent, but not all packets were bundled and there was no logic for requesting lost packets from the client and there was no packet reordering, which resulted in dire consequences in the case of packet loss (zoning failures, crashes and many other odd bugs). This patch addresses all of these issues. * Packet bundling: Packets are now automatically bundled and sent as SlottedMetaPackets using a recurring timer. All manual bundling functionality was removed. * Packet reordering: Incoming packets, if received out of order, are stashed and reordered. The maximum wait time for reordering is 20ms. * Packet requesting: Missing SlottedMetaPackets are requested from the client. * PacketCoding refactor: Dropped confusing packet container types. Fixes #5. * Crypto rewrite: PSCrypto is based on a ancient buggy version of cryptopp. Updating to a current version was not possible because it removed the MD5-MAC algorithm. For more details, see Md5Mac.scala. This patch replaces PSCrypto with native Scala code. * Added two new actors: * SocketActor: A simple typed UDP socket actor * MiddlewareActor: The old session pipeline greatly simplified into a typed actor that does most of the things mentioned above. * Begun work on a headless client * Fixed anniversary gun breaking stamina regen * Resolved a few sentry errors 2020-09-17 15:04:06 +00:00			`command: sbt server/run`
Fix docker compose file 2021-06-26 04:32:28 +00:00			`environment:`
			`CONFIG_FORCE_database_host: db`
Update docker configuration these changes resolve issues, preventing successful startup and binding with Docker for Windows 2021-06-27 00:30:26 +00:00			`CONFIG_FORCE_bind: 0.0.0.0`
Add docker-compose file (#466) 2020-05-26 20:19:44 +00:00			`adminer:`
			`image: adminer`
			`ports:`
			`- 51010:8080`
			`db:`
fix docker-compose.yml 2024-04-17 10:55:06 +00:00			`image: postgres:14`
Persistence #1 featuring quill (#508) * Add .scalafmt.conf * Adopt quill for database access * Removed postgresql-async * Refactored all instances of database access * Creating duplicate characters of the same account is no longer possible * Rewrote large parts of LoginSessionActor * Implement migrations * Move overrides into subdirectory * Make usernames case insensitive * Use LOWER(?) comparison instead of storing lowercased username * import scala.util.{Success, Failure} * Add config and joda-time dependencies * Add sbt-scalafmt * Use defaultWithAlign scalafmt preset * Format all * Add scalafix * Remove unused imports * Don't lowercase username when inserting * Update readme * Listen on worldserver.Hostname address * Remove database test on startup It could fail when the global thread pool is busy loading zone maps. Migrations run on the main thread and also serve the purpose of verifying the database configuration so it's fine to remove the test altogether. * Refactor chat message handlers, zones What started as a small change to how zones are stored turned into a pretty big effort of refactoring the chat message handler. The !hack command was removed, the /capturebase commandwas added. * Expose db ports in docker-compose.yml * Silence property override log * Rework configuration * Unify configuration using the typesafe.config library * Add configuration option for public address * Configuration is now loaded from application.conf rather than worldserver.ini * Refactor PsLogin and remove unnecessary logging * Move pslogin into net.psforever.pslogin namespace * Fix coverage 2020-07-14 03:54:05 +00:00			`ports:`
			`- 5432:5432`
Add docker-compose file (#466) 2020-05-26 20:19:44 +00:00			`environment:`
			`POSTGRES_USER: psforever`
			`POSTGRES_PASSWORD: psforever`
Persistence #1 featuring quill (#508) * Add .scalafmt.conf * Adopt quill for database access * Removed postgresql-async * Refactored all instances of database access * Creating duplicate characters of the same account is no longer possible * Rewrote large parts of LoginSessionActor * Implement migrations * Move overrides into subdirectory * Make usernames case insensitive * Use LOWER(?) comparison instead of storing lowercased username * import scala.util.{Success, Failure} * Add config and joda-time dependencies * Add sbt-scalafmt * Use defaultWithAlign scalafmt preset * Format all * Add scalafix * Remove unused imports * Don't lowercase username when inserting * Update readme * Listen on worldserver.Hostname address * Remove database test on startup It could fail when the global thread pool is busy loading zone maps. Migrations run on the main thread and also serve the purpose of verifying the database configuration so it's fine to remove the test altogether. * Refactor chat message handlers, zones What started as a small change to how zones are stored turned into a pretty big effort of refactoring the chat message handler. The !hack command was removed, the /capturebase commandwas added. * Expose db ports in docker-compose.yml * Silence property override log * Rework configuration * Unify configuration using the typesafe.config library * Add configuration option for public address * Configuration is now loaded from application.conf rather than worldserver.ini * Refactor PsLogin and remove unnecessary logging * Move pslogin into net.psforever.pslogin namespace * Fix coverage 2020-07-14 03:54:05 +00:00			`POSTGRES_DATABASE: psforever`