380f406248
## ⚠️ATTENTION! ⚠️ Upgrading procedure: **Database:** After this PR will be merged you need to backup your DB first (you can use the db-assembler or any mysql client to generate the dump) and restore it after. The reason is that we use now docker named volumes instead of binded ones to improve performance. **Conf & client data**: if you use the default configuration, both the etc and the data folder are now available inside the **/env/docker**. Finally, you can cleanup the /docker folder previously used by our system. ## Changes Proposed: This PR will implement the [devcontainer ](https://code.visualstudio.com/docs/remote/containers) feature for VSCode. Allowing us to develop and debug directly within the container in the same way on all OSes. * Implemented support for vscode dev-container feature by remote-extension suite * Docker performance optimizations for MacOS and non-linux hosts * Bash system improvements * Implemented first command using Deno runtime environment (typescript) and [commander.js] * Implemented wait mechanism for db_assembler * Implemented db migration command * possibility to run the authserver and worldserver with GDB using the integrated simple-restarter * Implemented docker multi-stage mechanism to use one single Dockerfile for all the services * client-data downloader now creates a placeholder to avoid downloading the same version of data files multiple times * deployment of pre-compiled docker images on [docker hub](https://hub.docker.com/u/acore), you can test them [here](https://github.com/azerothcore/acore-docker)
36 lines
1.6 KiB
YAML
36 lines
1.6 KiB
YAML
version: '3.9'
|
|
services:
|
|
# Update this to the name of the service you want to work with in your docker-compose.yml file
|
|
ac-dev-server:
|
|
# If you want add a non-root user to your Dockerfile, you can use the "remoteUser"
|
|
# property in devcontainer.json to cause VS Code its sub-processes (terminals, tasks,
|
|
# debugging) to execute as the user. Uncomment the next line if you want the entire
|
|
# container to run as this user instead. Note that, on Linux, you may need to
|
|
# ensure the UID and GID of the container user you create matches your local user.
|
|
# See https://aka.ms/vscode-remote/containers/non-root for details.
|
|
#
|
|
# user: vscode
|
|
|
|
# Uncomment if you want to override the service's Dockerfile to one in the .devcontainer
|
|
# folder. Note that the path of the Dockerfile and context is relative to the *primary*
|
|
# docker-compose.yml file (the first in the devcontainer.json "dockerComposeFile"
|
|
# array). The sample below assumes your primary file is in the root of your project.
|
|
#
|
|
# build:
|
|
# context: .
|
|
# dockerfile: .devcontainer/Dockerfile
|
|
|
|
#volumes:
|
|
# Update this to wherever you want VS Code to mount the folder of your project
|
|
#- .:/workspace:cached
|
|
|
|
# Uncomment the next line to use Docker from inside the container. See https://aka.ms/vscode-remote/samples/docker-from-docker-compose for details.
|
|
# - /var/run/docker.sock:/var/run/docker.sock
|
|
|
|
# Uncomment the next four lines if you will use a ptrace-based debugger like C++, Go, and Rust.
|
|
# cap_add:
|
|
# - SYS_PTRACE
|
|
# security_opt:
|
|
# - seccomp:unconfined
|
|
tty: true
|