* Add dameng stand
* Rename compose file
* Move damengdb files in tests folder
* Remove copy bin disql command
* Refactoring damengdb stand
* Update readme instructions
* Refactor: update readme
* Refactor: add note
* Update run command for disql copy
* Remove scripts and add volumes in compose file
Stand was updated. Main changes that scripts for prepare environment was removed.Now damengdb image can be pulled from hub.docker, also disql will be mounted from damengdb container in documentserver container.
* Update damengdb image version
* Actualized damengdb compose file
Use damengdb image from onlyoffice repo. Also do not use develop documentserver build anymore
* Don't mount entrypoint script anymore
After release it will be inside the image with the necessary edits
* Add the ability to build an image before compose is started
* Dameng: Execute schema on build stage
Now if you want use damengdb, you nedd build own image, schema for Documentserver will be create on build stage. Add dockerfile for the build dameng image. Also disql bin file don't share between containers
* Actualize readme for damengdb stand
* Editing typos
* Remove useless lines
* Small cosmetic change
* Remove useless volume from compose file
* Use default password for check connection
* Remove `image` filed from compose
The key that is automatically generated weaken the security strength.
As noted in RFC7518 section 3.2 [0]:
```
A key of the same size as the hash output (for instance, 256 bits for
"HS256") or larger MUST be used with this algorithm. (This
requirement is based on Section 5.3.4 (Security Effect of the HMAC
Key) of NIST SP 800-117 [NIST.800-107], which states that the
effective security strength is the minimum of the security strength
of the key and two times the size of the internal hash value.)
```
Some JWT libraries are rejecting by default keys that are too small in
a attempt to prevent misusages so generating a key that does not respect
the minimal length can be problematic for OO integrations.
[0] https://www.rfc-editor.org/rfc/rfc7518.html#section-3.2
