Hu: It seems a bit unreasonable to force users to download WAMP, which also comes with, separately, PHP, and MySQL, both of which are over 1-gb, just to run p-dash, which, itself, is <200-kb. [D]: The raw file size, of the entire wamp64 folder, after the prog-langs have been installed. Only if I can convince you to run an entire suite of features, that I’ve also built, using WAMP, can this file size be justified, but we may get there, pretty soon # Relative to other | operating systems, WAMP is actually max.red-easy<Turing> to install, and to install programs. The code will be open-source, but you can pay me $50 to help you with setup, which can take 20-min to 1 hour. Resources will also be available online, for users who want to do this themselves.
H3S1: Programming WAMP auto-installs:
Hu: I can potentially wrap a .exe around WAMP, to automatically install what you need, with macros, and also set up the 1) Virtual Host 2) generate a URL that you can click on, which will trigger a php file, that will generate the initial db-architecture<H3S2>. Following,
H3S2: Database-architecture:
Hu: I think it makes sense to have a single users_tb that feeds into all of the services, within the BOWSER-suite<WP.MIC-H2S67>, but each user, within each service, might have separate tbs. Initially, we can use a single db, but we might, at some point, separate out to a db per service, with users_tb becoming users_db, at that point, but it may be after the 10th service, that we’ll reach this point.
H3S3: Curating includes<Turing>:
Hu: Since we’re convincing you to install WAMP anyway, it may be worth it # to check Github, and see if there are other open sourced projects, with useful tools, that we can envelop. Some adaptation may be necessary, to add these to our users_tb, so this is not without technical debt. Obviously, only projects written in PHP, with no other lang-dependencies, and no exorbitant framework/lib/extension dependencies #, will work with our architecture. Note that our inclusion of WAMP itself, is already a form of this, and it took about 30 days of work, to get the integration going.