{"id":21452626,"url":"https://github.com/mserajnik/vmangos-deploy","last_synced_at":"2025-07-14T23:30:49.525Z","repository":{"id":205756639,"uuid":"713098313","full_name":"mserajnik/vmangos-deploy","owner":"mserajnik","description":"A Docker setup for VMaNGOS","archived":false,"fork":false,"pushed_at":"2024-04-09T20:22:45.000Z","size":104,"stargazers_count":7,"open_issues_count":0,"forks_count":1,"subscribers_count":1,"default_branch":"master","last_synced_at":"2024-04-10T00:35:20.289Z","etag":null,"topics":["docker","vmangos"],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"agpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/mserajnik.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null}},"created_at":"2023-11-01T20:45:30.000Z","updated_at":"2024-04-15T12:50:20.523Z","dependencies_parsed_at":"2024-03-25T12:50:42.523Z","dependency_job_id":"e55d9fde-6341-4c87-8db9-f665afb8129f","html_url":"https://github.com/mserajnik/vmangos-deploy","commit_stats":null,"previous_names":["mserajnik/vmangos-deploy"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mserajnik%2Fvmangos-deploy","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mserajnik%2Fvmangos-deploy/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mserajnik%2Fvmangos-deploy/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mserajnik%2Fvmangos-deploy/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/mserajnik","download_url":"https://codeload.github.com/mserajnik/vmangos-deploy/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":226002739,"owners_count":17558149,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["docker","vmangos"],"created_at":"2024-11-23T04:31:00.560Z","updated_at":"2025-07-14T23:30:49.512Z","avatar_url":"https://github.com/mserajnik.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"# vmangos-deploy\n\n[![Latest built VMaNGOS commit][badge-latest-vmangos-commit]][badge-latest-vmangos-commit-url] [![Latest build date][badge-latest-build-date]][badge-latest-build-date-url] [![GitHub Actions status][badge-actions-status]][badge-actions-status-url]\n\n\u003e A Docker setup for VMaNGOS\n\nThis is a Docker-based solution for running [VMaNGOS][vmangos] that focuses on\nproviding a streamlined and user-friendly experience. It offers a range of\nfeatures that simplify managing a VMaNGOS setup:\n\n+ __Prebuilt Docker images for both `x86_64` and `aarch64`, leveraging GitHub__\n  __Actions:__ simply pull the provided images that have been optimized for\n  size, performance and stability instead of having to re-compile VMaNGOS\n  yourself every time you want to update\n+ __The ability to run VMaNGOS configured for any of its supported client__\n  __versions:__ prebuilt images for all versions ranging from `1.6.1.4544` to\n  `1.12.1.5875` are provided\n+ __Seamless, automated database migrations:__ when pulling the latest Docker\n  images and re-creating the containers, migrations are applied automatically\n  to keep your database up-to-date at all times\n+ __A transparent and easy-to-follow user experience:__ the number of different\n  commands that need to be run to install and manage VMaNGOS is kept to a\n  minimum. You can use the Docker CLI or any other tool that is able to manage\n  Docker containers\n+ __A clean and organized structure:__ the VMaNGOS configuration can be found\n  in [`./config`](config), everything else that is shared between the Docker\n  containers and your host system lives inside [`./storage`](storage)\n\n\u003e [!NOTE]\n\u003e The Docker images are built on a daily schedule, unless there have been no\n\u003e new commits to VMaNGOS since the last build. Additionally, every Monday, the\n\u003e latest images are rebuilt to ensure software and dependencies are up-to-date,\n\u003e even if there have been no updates to VMaNGOS itself.\n\n## Table of contents\n\n+ [Install](#install)\n  + [Dependencies](#dependencies)\n  + [Instructions](#instructions)\n    + [Cloning the repository and adjusting the VMaNGOS configuration](#cloning-the-repository-and-adjusting-the-vmangos-configuration)\n    + [Adjusting the Docker Compose configuration](#adjusting-the-docker-compose-configuration)\n    + [Extracting the client data](#extracting-the-client-data)\n    + [Providing the Warden modules (optional)](#providing-the-warden-modules-optional)\n    + [Utilizing automatic world database corrections (optional)](#utilizing-automatic-world-database-corrections-optional)\n    + [Modifying the world database with custom changes (optional)](#modifying-the-world-database-with-custom-changes-optional)\n+ [Usage](#usage)\n  + [Starting VMaNGOS](#starting-vmangos)\n  + [Observing the VMaNGOS output](#observing-the-vmangos-output)\n  + [Creating the first account](#creating-the-first-account)\n  + [Stopping VMaNGOS](#stopping-vmangos)\n  + [Updating](#updating)\n    + [Breaking changes](#breaking-changes)\n  + [Creating database backups](#creating-database-backups)\n  + [Accessing the database](#accessing-the-database)\n  + [Database security](#database-security)\n+ [Maintainer](#maintainer)\n+ [Contribute](#contribute)\n+ [License](#license)\n\n## Install\n\n### Dependencies\n\n+ [Docker][docker] (including [Compose V2][docker-compose])\n\n### Instructions\n\n#### Cloning the repository and adjusting the VMaNGOS configuration\n\nFirst, clone the repository and create copies of the provided VMaNGOS example\nconfiguration files:\n\n```sh\ngit clone https://github.com/mserajnik/vmangos-deploy.git\ncd vmangos-deploy\ncp ./config/mangosd.conf.example ./config/mangosd.conf\ncp ./config/realmd.conf.example ./config/realmd.conf\n```\n\nNext, adjust the two configuration files you have just created for your desired\nsetup. The default configuration should work well as a starting point, but you\nmay still want to adjust certain things such as the `GameType`, the `RealmZone`\nor `Anticheat.*` and `Warden.*` options. Descriptions are provided for each\noption in the configuration files, so you should be able to find your way\naround easily.\n\n\u003e [!CAUTION]\n\u003e Options relating to certain things that vmangos-deploy relies on to work\n\u003e correctly (like the database connections or configured directories such as\n\u003e the `DataDir` or the `LogsDir`) should not be adjusted unless you absolutely\n\u003e need to change them and are aware of the implications (e.g., which\n\u003e other configuration options may need to be adjusted as well to avoid\n\u003e discrepancies resulting in unexpected behavior). No support will be provided\n\u003e for non-default setups.\n\n### Adjusting the Docker Compose configuration\n\nOnce you are done adjusting the VMaNGOS configuration, create a copy of the\nDocker Compose example configuration:\n\n```sh\ncp ./compose.yaml.example ./compose.yaml\n```\n\nNext, adjust your `compose.yaml`. The first thing to decide on is which Docker\nimages you want to use based on the client version the server should support.\nYou can choose from the following versions:\n\n| Supported client version | Image                                   |\n| ------------------------ | --------------------------------------- |\n| `1.12.1.5875`            | `ghcr.io/mserajnik/vmangos-server:5875` |\n| `1.11.2.5464`            | `ghcr.io/mserajnik/vmangos-server:5464` |\n| `1.10.2.5302`            | `ghcr.io/mserajnik/vmangos-server:5302` |\n| `1.9.4.5086`             | `ghcr.io/mserajnik/vmangos-server:5086` |\n| `1.8.4.4878`             | `ghcr.io/mserajnik/vmangos-server:4878` |\n| `1.7.1.4695`             | `ghcr.io/mserajnik/vmangos-server:4695` |\n| `1.6.1.4544`             | `ghcr.io/mserajnik/vmangos-server:4544` |\n\nAdjust the configured image for the `realmd` and `mangosd` services based on\nthis table. E.g., if you wanted to run a server that supports client version\n`1.6.1.4544`, you would choose `ghcr.io/mserajnik/vmangos-server:4544`.\n\nBy default, the latest available images are used. Alternatively, you can also\nselect specific ones via the VMaNGOS commit hash they have been built from. To\nallow for this, the `vmangos-server` image (used by the `realmd` and `mangos`\nservices) and the `vmangos-database` image (used by the `database` service)\nhave tags that include the respective commit hash. E.g., for commit\n[`46183d287f80ab1ebf27bab12f37bc0b5b188c86`][vmangos-example-commit]:\n\n| `realmd`/`mangos` service image                                                  | `database` service image                                                      |\n| -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |\n| `ghcr.io/mserajnik/vmangos-server:5875-46183d287f80ab1ebf27bab12f37bc0b5b188c86` | `ghcr.io/mserajnik/vmangos-database:46183d287f80ab1ebf27bab12f37bc0b5b188c86` |\n\n\u003e [!IMPORTANT]\n\u003e When you decide to select images via VMaNGOS commit hash you should always\n\u003e make sure to use the same one for the `vmangos-server` and the\n\u003e `vmangos-database` images so there are no potential discrepancies between\n\u003e code and data. It is _not_ possible (or intended) to switch to images based\n\u003e on an older commit than the previous ones you used to perform a clean\n\u003e downgrade due to the database migrations.\n\nSince the Docker images are generally built only once a day it, is unlikely\nthat there will be a build for every single VMaNGOS commit. Older images are\nautomatically deleted, roughly after 45 days; in practice, you should not rely\non specific images staying available for any prolonged period of time. If you\nabsolutely need images based on a specific VMaNGOS commit, you can always build\nthem yourself instead.\n\n\u003e [!TIP]\n\u003e You can find all the currently available `vmangos-server` and\n\u003e `vmangos-database` images [here][image-vmangos-server-versions] and\n\u003e [here][image-vmangos-database-versions] respectively.\n\nAside from which Docker images you want to use you mainly have to pay attention\nto the `environment` sections of each service configuration. In particular, you\nwill want to adjust the `TZ` (time zone) environment variable for each service.\nThe `VMANGOS_REALMLIST_*` environment variables of the `database` service\nshould also be of interest; changing the `VMANGOS_REALMLIST_ADDRESS` to a LAN\nIP, a WAN IP or a domain name is required if you want to allow non-local\nconnections.\n\nAlso take note of the `healthcheck` sections; if you are using a low end system\nyou may have to adjust the `start_period` setting so that the initial database\ncreation process will be able to complete in time before the healthcheck\nconsiders the container unhealthy and causes a restart.\n\n\u003e [!CAUTION]\n\u003e Anything in your `compose.yaml` that is not commented or explicitly mentioned\n\u003e in this README, regardless of the section, is likely something you do not\n\u003e have to (or, in some cases, _must not_) change. Doing so may lead to\n\u003e unexpected behavior and is not supported.\n\n### Extracting the client data\n\nVMaNGOS uses data that is generated from extracted client data to handle things\nlike mob movement and line of sight. If you have already acquired this data\npreviously, you can place it directly into\n[`./storage/mangosd/extracted-data`](storage/mangosd/extracted-data) and skip\nthe next steps.\n\nTo extract the data, first copy the contents of your client directory into\n[`./storage/mangosd/client-data`](storage/mangosd/client-data). Next, simply\nrun the following command:\n\n```sh\ndocker run \\\n  -i \\\n  -v ./storage/mangosd/client-data:/opt/vmangos/storage/client-data \\\n  -v ./storage/mangosd/extracted-data:/opt/vmangos/storage/extracted-data \\\n  --rm \\\n  --user 1000:1000 \\\n  ghcr.io/mserajnik/vmangos-server:5875 \\\n  extract-client-data\n```\n\nThere are two things to look out for here:\n\n+ If you are using a Linux host and your user's UID and GID are not 1000,\n  change the `--user` argument to reflect your user's UID and GID. This will\n  cause the user in the container to use the same UID and GID and prevent\n  permission issues on the bind mounts. If you are on Windows or macOS, you can\n  ignore this (or even remove the `--user` argument altogether, if you want to)\n+ The Docker image must reflect the client version you want to extract the data\n  from; see the table further above in the\n  [Docker Compose configuration section](#adjusting-the-docker-compose-configuration)\n\n\u003e [!IMPORTANT]\n\u003e Extracting the data can take many hours (depending on your hardware). Some\n\u003e notices/errors during the process are normal and usually nothing to worry\n\u003e about (as long as the execution continues afterwards).\n\nOnce the extraction is finished you can find the data in\n[`./storage/mangosd/extracted-data`](storage/mangosd/extracted-data). Note that\nyou may want to re-run the process in the future if VMaNGOS makes changes (to\nbenefit from potentially improved mob movement etc.). In case it becomes\nnecessary to do so (e.g., if the extraction process changes), the\n[breaking changes section](#breaking-changes) further below will be updated\naccordingly.\n\nIf you re-run the extraction, it will automatically detect previously extracted\ndata and ask you if you want to continue (which will overwrite the old data).\nYou can also skip this confirmation prompt (and force the re-extraction) by\nadding the `--force` flag to the `extract-client-data` command, like this:\n\n```sh\ndocker run \\\n  -i \\\n  -v ./storage/mangosd/client-data:/opt/vmangos/storage/client-data \\\n  -v ./storage/mangosd/extracted-data:/opt/vmangos/storage/extracted-data \\\n  --rm \\\n  --user 1000:1000 \\\n  ghcr.io/mserajnik/vmangos-server:5875 \\\n  extract-client-data --force\n```\n\n### Providing the Warden modules (optional)\n\nTo use Warden, you have to provide the [Warden modules][warden-modules]\nyourself. See [here][compose-warden-modules] for details on how to do so.\n\n\u003e [!WARNING]\n\u003e Using [HermesProxy][hermesproxy] (or projects derived from it) to connect\n\u003e `1.14.x` clients to VMaNGOS will likely not be possible (in a stable manner\n\u003e without getting kicked off the server) when Warden is enabled.\n\n### Utilizing automatic world database corrections (optional)\n\nvmangos-deploy keeps track of certain, unusual VMaNGOS code changes (such as\nmigration edits) that lead to a faulty (or out-of-sync) world database state\nwhen updating and would normally require manual intervention by you to rectify.\n\nBy default, vmangos-deploy can automatically correct the state of your world\ndatabase in such cases by re-creating it. It is strongly suggested to keep this\nfeature enabled.\n\nIf you do decide to [disable it][compose-automatic-world-db-corrections], you\nyourself are responsible for monitoring VMaNGOS for problematic code changes\nand taking appropriate actions (e.g., manually triggering the re-creation of\nthe world database by mounting a database dump, as described\n[here][compose-world-db-dump-mount]).\n\n### Modifying the world database with custom changes (optional)\n\nIf you want to make custom changes to the world database, it is recommended to\ndo so using SQL files and placing them in\n[`./storage/database/custom-sql`](storage/database/custom-sql) (a bind mount\nfor this directory is\n[configured out-of-the-box][compose-custom-sql-bind-mount]). This way, you can\nkeep\n[automatic world database corrections](#utilizing-automatic-world-database-corrections-optional)\nenabled without having to worry about your changes getting lost.\n\nBy default, all SQL files (files with a `.sql` extension) in that directory\nwill be processed during each startup in alphabetical order (after the world\ndatabase has been created and updated with the latest migrations). Thus, the\nSQL statements in your files have to be idempotent (i.e., they can be processed\nmultiple times without causing issues).\n\nAn example SQL file that shows how you can populate the `auctionhousebot` table\nwith custom data\n[is provided](storage/database/custom-sql/auctionhousebot.sql.example). This\nSQL file will not be processed by default without removing the `.example`\nsuffix from the file name. If you want to use it, it is recommended to first\nmake a copy of the file and then adjust the copy to your liking instead of\nrenaming the original file (to avoid dirtying the working tree).\n\nYou can find further details about this feature [here][compose-custom-sql].\n\n## Usage\n\n### Starting VMaNGOS\n\nOnce you are happy with the configuration and have extracted the client data,\nyou can start VMaNGOS for the first time. To do so, run:\n\n```sh\ndocker compose up -d\n```\n\nThis pulls the Docker images first and afterwards automatically creates and\nstarts the containers. During the first startup it might take a little longer\nuntil the server becomes available due to the initial database creation.\n\n\u003e [!CAUTION]\n\u003e Make sure to not (accidentally) stop VMaNGOS before the database creation\n\u003e process has finished; otherwise, you will likely end up with a broken\n\u003e database and will have to delete and re-create it.\n\n### Observing the VMaNGOS output\n\nEspecially during the first startup you might want to follow the server output\nto know when VMaNGOS is up and running:\n\n```sh\ndocker compose logs -f mangosd\n```\n\nOnce you see the output `World initialized.` you know that the intialization\nprocess has finished and VMaNGOS is ready.\n\n### Creating the first account\n\nTo create the first account, attach to the `mangosd` container (make sure\n[that the server is ready](#observing-the-vmangos-output) before attaching):\n\n```sh\ndocker attach vmangos-deploy-mangosd-1\n```\n\nAfter attaching, create the account and assign an account level:\n\n```sh\naccount create \u003caccount name\u003e \u003caccount password\u003e\naccount set gmlevel \u003caccount name\u003e \u003caccount level\u003e # see https://github.com/vmangos/core/blob/46183d287f80ab1ebf27bab12f37bc0b5b188c86/src/shared/Common.h#L183-L189\n```\n\nWhen you are done, detach from the Docker container by pressing\n\u003ckbd\u003eCtrl\u003c/kbd\u003e+\u003ckbd\u003eP\u003c/kbd\u003e and \u003ckbd\u003eCtrl\u003c/kbd\u003e+\u003ckbd\u003eQ\u003c/kbd\u003e. You should\nnow be able to log in with your newly created account.\n\n### Stopping VMaNGOS\n\nTo stop VMaNGOS, simply run:\n\n```sh\ndocker compose down\n```\n\n### Updating\n\nTo update, pull the latest images:\n\n```sh\ndocker compose pull\n```\n\nAfterwards, re-create the containers:\n\n```sh\ndocker compose up -d\n```\n\n\u003e [!NOTE]\n\u003e Selecting specific images via VMaNGOS commit hash (as described further\n\u003e above) will obviously prevent you from updating until you edit each\n\u003e respective service in your `compose.yaml` to pull newer images. Attempting to\n\u003e update without changing the configured images is not harmful, it will just\n\u003e not have any effect.\n\n#### Breaking changes\n\nIt is recommended to regularly check this repository (either manually or by\nupdating your local repository via `git pull`). Usually, the commits here will\njust consist of maintenance and potentially new VMaNGOS configuration options\n(that you may want to incorporate into your configuration).\n\nSometimes, there may be new features or changes that require manual\nintervention. Such breaking changes will be listed here (and removed again once\nthey become irrelevant), sorted by newest first:\n\n+ __[2025-02-22] - Automatic world database corrections are now available and__\n  __enabled by default:__ vmangos-deploy now keeps track of certain, unusual\n  VMaNGOS code changes (such as migration edits) that lead to a faulty (or\n  out-of-sync) world database state when updating and would normally require\n  manual intervention by you to rectify. In such cases, vmangos-deploy can\n  automatically correct the state of your world database by re-creating it. It\n  is strongly suggested to keep this feature enabled. If you do decide to\n  [disable it][compose-automatic-world-db-corrections] in your `compose.yaml`,\n  you yourself are responsible for monitoring VMaNGOS for problematic code\n  changes and taking appropriate actions (e.g., manually triggering the\n  re-creation of the world database by mounting a database dump, as described\n  [here][compose-world-db-dump-mount]). This section will no longer list such\n  changes.\n+ __[2024-10-31] - Removal of separate images with anticheat support:__\n  As of\n  [`vmangos/core@fbbc4ae`](https://github.com/vmangos/core/commit/fbbc4ae899f876a78a37d8fee805dce40a182331)\n  VMaNGOS no longer supports building without anticheat support, thus anticheat\n  is always available and there is no longer a need for separate images. If\n  you were using one of the anticheat images (which were suffixed with\n  `-anticheat`), simply switch to the regular version of that image.\n\n### Creating database backups\n\nIt is recommended to perform regular database backups, particularly before\nupdating.\n\nTo automatically create database backups periodically, uncomment the\n[`database-backup` service configuration][compose-database-backups] in your\n`compose.yaml` and follow the comments for further information.\n\n### Accessing the database\n\nTo make certain changes (e.g., managing accounts or changing the realm\nconfiguration) it can be necessary to access the database with a MySQL/MariaDB\nclient.\n\nA common web-based MySQL/MariaDB database administration tool called\n[phpMyAdmin][phpymadmin] is included and can be enabled by uncommenting the\n[`phpmyadmin` service configuration][compose-phpmyadmin] in your\n`compose.yaml`. See the comments there for further information.\n\n### Database security\n\nIt is not recommended to expose your database to the public (whether through\ndirect port access, a WAN-accessible phpMyAdmin instance, or any other means).\nIf you decide to do so, you will have to implement appropriate security\nmeasures. Please note that no further support or guidance regarding this will\nbe provided here.\n\n\u003e [!CAUTION]\n\u003e The default database users with full access to all VMaNGOS data (`root` and\n\u003e the user named via `MARIADB_USER` environment variable) do not have any\n\u003e restrictions in place in regards to which IPs/hosts can connect.\n\n## Maintainer\n\n[Michael Serajnik][maintainer]\n\n## Contribute\n\nYou are welcome to help out!\n\n[Open an issue][issues] or [make a pull request][pull-requests].\n\n## License\n\n[AGPL-3.0-or-later](LICENSE) © Michael Serajnik\n\n[badge-actions-status]: https://github.com/mserajnik/vmangos-deploy/actions/workflows/build-docker-images.yaml/badge.svg\n[badge-actions-status-url]: https://github.com/mserajnik/vmangos-deploy/actions/workflows/build-docker-images.yaml\n[badge-latest-build-date]: https://img.shields.io/endpoint?url=https%3A%2F%2Fscripts.mser.at%2Fvmangos-deploy-badges%2Fdate-badge.json\n[badge-latest-build-date-url]: https://github.com/mserajnik?tab=packages\u0026repo_name=vmangos-deploy\n[badge-latest-vmangos-commit]: https://img.shields.io/endpoint?url=https%3A%2F%2Fscripts.mser.at%2Fvmangos-deploy-badges%2Fcommit-badge.json\n[badge-latest-vmangos-commit-url]: https://github.com/vmangos/core/commits/development/\n\n[compose-automatic-world-db-corrections]: https://github.com/mserajnik/vmangos-deploy/blob/master/compose.yaml.example#L52-L63\n[compose-custom-sql]: https://github.com/mserajnik/vmangos-deploy/blob/master/compose.yaml.example#L64-L81\n[compose-custom-sql-bind-mount]: https://github.com/mserajnik/vmangos-deploy/blob/master/compose.yaml.example#L20\n[compose-database-backups]: https://github.com/mserajnik/vmangos-deploy/blob/master/compose.yaml.example#L213-L248\n[compose-phpmyadmin]: https://github.com/mserajnik/vmangos-deploy/blob/master/compose.yaml.example#L250-L269\n[compose-warden-modules]: https://github.com/mserajnik/vmangos-deploy/blob/master/compose.yaml.example#L197-L207\n[compose-world-db-dump-mount]: https://github.com/mserajnik/vmangos-deploy/blob/master/compose.yaml.example#L21-L35\n[docker]: https://docs.docker.com/get-docker/\n[docker-compose]: https://docs.docker.com/compose/install/\n[hermesproxy]: https://github.com/WowLegacyCore/HermesProxy\n[image-vmangos-database-versions]: https://github.com/mserajnik/vmangos-deploy/pkgs/container/vmangos-database/versions?filters%5Bversion_type%5D=tagged\n[image-vmangos-server-versions]: https://github.com/mserajnik/vmangos-deploy/pkgs/container/vmangos-server/versions?filters%5Bversion_type%5D=tagged\n[phpymadmin]: https://www.phpmyadmin.net/\n[vmangos]: https://github.com/vmangos/core\n[vmangos-example-commit]: https://github.com/vmangos/core/commit/46183d287f80ab1ebf27bab12f37bc0b5b188c86\n[warden-modules]: https://github.com/vmangos/warden_modules\n\n[issues]: https://github.com/mserajnik/vmangos-deploy/issues\n[maintainer]: https://github.com/mserajnik\n[pull-requests]: https://github.com/mserajnik/vmangos-deploy/pulls\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmserajnik%2Fvmangos-deploy","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmserajnik%2Fvmangos-deploy","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmserajnik%2Fvmangos-deploy/lists"}