azerothcore-wotlk-pbot

mirror of https://github.com/mod-playerbots/azerothcore-wotlk.git synced 2025-11-29 17:38:24 +08:00

Files

Mike Delago ea51cdf0a6 fix(Docker): config loading for ac-dev-server container (#14755 )

## Changes Proposed:
-  This properly moves things from `DOCKER_ETC_FOLDER` to `confDir`
- originally broken with
888a718cf3

## Issues Addressed:
- Should hopefully close
https://github.com/azerothcore/acore-docker/issues/12

## SOURCE:

## Tests Performed:
- I'm not exactly aware of the testing procedure for this, as I don't
use acore-docker
- That said, the previous behavior has been replicated:

2420d19e54/apps/compiler/includes/functions.sh (L148-L150)
- Open to suggestions


## How to Test the Changes:
1. Open to Suggestions

## Known Issues and TODO List:

- Test properly

## How to Test AzerothCore PRs
 
When a PR is ready to be tested, it will be marked as **[WAITING TO BE
TESTED]**.

You can help by testing PRs and writing your feedback here on the PR's
page on GitHub. Follow the instructions here:

http://www.azerothcore.org/wiki/How-to-test-a-PR

**REMEMBER**: when testing a PR that changes something **generic** (i.e.
a part of code that handles more than one specific thing), the tester
should not only check that the PR does its job (e.g. fixing spell XXX)
but **especially** check that the PR does not cause any regression (i.e.
introducing new bugs).

**For example**: if a PR fixes spell X by changing a part of code that
handles spells X, Y, and Z, we should not only test X, but **we should
test Y and Z as well**.

2023-01-25 17:55:24 +01:00

includes

fix(Docker): config loading for ac-dev-server container (#14755 )

2023-01-25 17:55:24 +01:00

.gitignore

Directory Structure [step 1]: moving files

2017-10-12 20:00:52 +02:00

compiler.sh

feat(CORE): docker permissions and rework (#13454 )

2022-11-07 13:20:48 +01:00

README.md

feat(bash): support for derivated distro + refactor conf (#3259 )

2020-08-06 02:37:14 +02:00

README.md

How to compile:

first of all, if you need some custom configuration you have to copy /conf/dist/config.sh in /conf/config.sh and configure it

for a "clean" compilation you must run all scripts in their order:
```
  ./1-clean.sh
  ./2-configure.sh
  ./3-build.sh
```
if you add/rename/delete some sources and you need to compile it you have to run:
```
  ./2-configure.sh
  ./3-build.sh
```
if you have modified code only, you just need to run
```
  ./3-build.sh
```

compiler.sh

compiler.sh script contains an interactive menu to clean/compile/build. You can also run actions directly by command lines specifying the option. Ex: ./compiler.sh 3

It will start the build process (it's equivalent to ./3-build.sh)

Note:

For an optimal development process and really faster compilation time, is suggested to use clang instead of gcc