Rewrite: Added documentation and cleared up code into an OOP design

[Jayy001]

TODO:

• [x] Fix build scripts
• [x] Add docstrings for other modules
• [ ] Cleanup server code at a later date
• [ ] Update README documentation for API support
• [ ] Disable automatic update on boot
• [ ] Enable Toltec on boot (?)
• [ ] Enable RmHacks on boot (?)
• [ ] Add GUI version
• [ ] Enable web-interface automatically
• [ ] Make USB network private
• [ ] Add command to explore contents and mount command

[Eeems]

I would recommend against a modules folder, and instead just have the modules alongside __init__.py at the top level of the codexctl package. Especially since you'll now have to add a new __init__.py to make the modules folder a valid module to be loaded by the parent codexctl package.

I also would not recommend moving the Makefile or requirements.txt out of the root directory, as this adds complexity for users who are trying to do the build for the first time, It also adds a lot of complexity to all of the standard tooling that expects things to be in the same directory as the code by default.

[Jayy001]

I would recommend against a modules folder, and instead just have the modules alongside __init__.py at the top level of the codexctl package. Especially since you'll now have to add a new __init__.py to make the modules folder a valid module to be loaded by the parent codexctl package.

I also would not recommend moving the Makefile or requirements.txt out of the root directory, as this adds complexity for users who are trying to do the build for the first time, It also adds a lot of complexity to all of the standard tooling that expects things to be in the same directory as the code by default.

Thought about this, and come to the conclusion that I agree. (Also saves me changing all the build process).