So again, to try to clarify some issues: everything QEWD-up needs in order to start up is in the config.json file. If you know what you’re doing, the idea is that you’d normally maintain that file manually. However, there are so many potential configuration options such as what database you’re using, what OS you’re using, how many child processes you want, what port you want to listen on etc etc, it can be confusing for anyone just wanting to kick the tyres of QEWD and quickly try it out. Also until you’re familiar with these parameters and the moving parts of QEWD, if you get something wrong in the config.json, it can be difficult to figure out why it’s going wrong.
So, in order to resolve that, I created the automated install/configure script that you see recommended for use in the QEWD-baseline and QEWD-jsdb repos. All they actually do is build the config.json for you in a foolproof way (provided you read and follow the instructions in the readme), and create a wrapper around the docker run command needed to start the dockerised version of QEWD. The script also pulls in pre-Initialised YottaDB database files so you can maintain persistence on the host.
None of that is essential. If you know how QEWD and QEWD-up works, and know how to initialise yottadb files and run Docker containers with the correct volume mapped for QEWD, then you can do it all yourself, as documented in all the other QEWD-related repos.
For anyone not 100% familiar with QEWD, I recommend you use my automation to get it working. The idea of open source is that all the source code is there for you to study and figure out what I’ve done and how what I’ve done works and why. See what my scripts create, study their code to see how they create what they create, and you’ll quickly learn how to control and operate QEWD for yourself in your own way that suits you. Nothing I’ve done is intended to force you to work in a particular way, other than the core QEWD-up files and syntax and the dockerised version’s mapped volume internal path
Hope this helps to explain the rationale of what I’ve created