hotstaq 0.5.24

package/.eslintignore

@@ -0,0 +1,17 @@
+db/
+
+build/
+build-web/
+builder/
+creator/
+docs/
+node_modules/
+output/
+
+client/
+tests/
+
+create-test-temp/
+
+./HotSite.json
+./*.config.js

package/.eslintrc.js

@@ -0,0 +1,11 @@
+module.exports = {
+    root: true,
+    parser: '@typescript-eslint/parser',
+    plugins: [
+      '@typescript-eslint',
+    ],
+    extends: [
+      'eslint:recommended',
+      'plugin:@typescript-eslint/recommended',
+    ],
+  };

package/.vscode/launch.json

@@ -0,0 +1,199 @@
+{
+	// Use IntelliSense to learn about possible attributes.
+	// Hover to view descriptions of existing attributes.
+	// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+	"version": "0.2.0",
+	"configurations": [
+		{
+			"type": "node",
+			"name": "Debug Web Server",
+			"program": "${workspaceFolder}/build/src/cli.js",
+			"request": "launch",
+			"skipFiles": [
+				"<node_internals>/**"
+			],
+			"outputCapture": "std",
+			"args": [
+				"run",
+				"--web-route",
+				"/=${workspaceFolder}",
+				"--web-dont-redirect-http-to-https",
+				"--web-js-url",
+				"/build-web/HotStaq.js",
+				"--web-serve-hott-files",
+				"--web-http-port",
+				"8080"
+			]
+		},
+		{
+			"type": "node",
+			"name": "Debug API Server",
+			"program": "${workspaceFolder}/build/src/cli.js",
+			"request": "launch",
+			"skipFiles": [
+				"<node_internals>/**"
+			],
+			"outputCapture": "std",
+			"args": [
+				"run",
+				"--server-type",
+				"api",
+				"--api-load",
+				"HelloWorldAPI=${workspaceFolder}/build/tests/server/HelloWorldAPI.js",
+				"--api-dont-redirect-http-to-https",
+				"--api-http-port",
+				"8181"
+			]
+		},
+		{
+			"type": "node",
+			"name": "Debug Web-API Server",
+			"program": "${workspaceFolder}/build/src/cli.js",
+			"request": "launch",
+			"skipFiles": [
+				"<node_internals>/**"
+			],
+			"outputCapture": "std",
+			"args": [
+				"run",
+				"--server-type",
+				"web-api",
+				"--api-load",
+				"HelloWorldAPI=${workspaceFolder}/build/tests/server/HelloWorldAPI.js",
+				"--web-route",
+				"/=${workspaceFolder}",
+				"--web-dont-redirect-http-to-https",
+				"--web-js-url",
+				"/build-web/HotStaq.js",
+				"--web-serve-hott-files",
+				"--web-http-port",
+				"8080",
+				"--api-dont-redirect-http-to-https",
+				"--api-http-port",
+				"8181"
+			]
+		},
+		{
+			"type": "node",
+			"name": "Debug Web Server - HotSite",
+			"program": "${workspaceFolder}/build/src/cli.js",
+			"request": "launch",
+			"skipFiles": [
+				"<node_internals>/**"
+			],
+			"outputCapture": "std",
+			"args": [
+				"run",
+				"--hotsite",
+				"./tests/hotsite/HotSite.json",
+				"--web-dont-redirect-http-to-https",
+				"--web-js-url",
+				"/build-web/HotStaq.js",
+				"--web-http-port",
+				"8080"
+			]
+		},
+		{
+			"type": "node",
+			"request": "launch",
+			"name": "Debug Web Server - Development",
+			"program": "${workspaceFolder}/build/src/cli.js",
+			"skipFiles": [
+				"<node_internals>/**"
+			],
+			"outputCapture": "std",
+			"args": [
+				"run",
+				"--web-dont-redirect-http-to-https",
+				"--development-mode",
+				"--web-js-url",
+				"/build-web/HotStaq.js",
+				"--web-serve-hott-files",
+				"--web-http-port",
+				"8080"
+			]
+		},
+		{
+			"type": "node",
+			"request": "launch",
+			"name": "Build from HotSite",
+			"program": "${workspaceFolder}/build/src/cli.js",
+			"skipFiles": [
+				"<node_internals>/**"
+			],
+			"outputCapture": "std",
+			"args": [
+				"build",
+				"--hotsite",
+				"./tests/hotsite/HotSite.json",
+				"--docker"
+			]
+		},
+		{
+			"type": "node",
+			"request": "launch",
+			"name": "Create an App",
+			"program": "${workspaceFolder}/build/src/cli.js",
+			"cwd": "/home/squigglet/temp2/app",
+			"skipFiles": [
+				"<node_internals>/**"
+			],
+			"outputCapture": "std",
+			"args": [
+				"create",
+				"--overwrite-cmd-create-transpile",
+				"npm link hotstaq && npm run build",
+				"app"
+			]
+		},
+		{
+			"type": "node",
+			"request": "launch",
+			"name": "Create an App API",
+			"program": "${workspaceFolder}/build/src/cli.js",
+			"skipFiles": [
+				"<node_internals>/**"
+			],
+			"outputCapture": "std",
+			"args": [
+				"create",
+				"--type",
+				"api",
+				"--overwrite-cmd-create-transpile",
+				"npm link hotstaq && npm run build",
+				"app"
+			]
+		},
+		{
+			"type": "node",
+			"request": "launch",
+			"name": "Run Tests",
+			"skipFiles": [
+				"<node_internals>/**"
+			],
+			"program": "${workspaceFolder}/node_modules/mocha/bin/mocha",
+			"args": [
+				"--timeout", "15", 
+				"--inspect=127.0.0.1:7478", 
+				"--colors", 
+				"./build/tests/db/*.js"
+			],
+			"attachSimplePort": 7478,
+			"cwd": "${workspaceFolder}",
+			"env": {
+				"HTTP_PORT": "3123",
+				"DATABASE_SERVER": "192.168.1.195",
+				"DATABASE_PORT": "3310",
+				"DATABASE_USERNAME": "5NKVBAt7OrzrumQyQVs",
+				"DATABASE_PASSWORD": "1BBrZbKYRUM7oiMA5oY",
+				"DATABASE_SCHEMA": "hotstaq",
+				"INFLUX_DATABASE_SERVER": "http://192.168.1.195:8088",
+				"INFLUX_DATABASE_USERNAME": "5NKVBAt7OrzrumQyQVs",
+				"INFLUX_DATABASE_PASSWORD": "1BBrZbKYRUM7oiMA5oY",
+				"INFLUX_DATABASE_ORG": "freelight",
+				"INFLUX_DATABASE_TOKEN": "Ife0HerzHrloa32PsE4yg4ixA6j7tZFSMRhvBg7akUK2e",
+				"INFLUX_DATABASE_SCHEMA": "hotstaq"
+			}
+		}
+	]
+}

package/.vscode/settings.json

@@ -0,0 +1,2 @@
+{
+}

package/.vscode/tasks.json

@@ -0,0 +1,78 @@
+{
+	"version": "2.0.0",
+	"tasks": [
+		{
+			"type": "typescript",
+			"tsconfig": "tsconfig.json",
+			"option": "watch",
+			"problemMatcher": [
+				"$tsc-watch"
+			],
+			"group": "build",
+			"runOptions": {
+				"instanceLimit": 1
+			},
+			"label": "Build"
+		},
+		{
+			"type": "shell",
+			"group": "build",
+			"runOptions": {
+				"instanceLimit": 1
+			},
+			"problemMatcher": [],
+			"label": "Build web debug",
+			"command": "npx webpack --mode=development --watch"
+		},
+		{
+			"type": "shell",
+			"group": "build",
+			"runOptions": {
+				"instanceLimit": 1
+			},
+			"problemMatcher": [],
+			"label": "Build web tests",
+			"command": "npx webpack --mode=development --config=webpack.config.tests.js --watch"
+		},
+		{
+			"type": "process",
+			"group": {
+				"kind": "build",
+				"isDefault": true
+			},
+			"runOptions": {
+				"instanceLimit": 1,
+				"runOn": "folderOpen"
+			},
+			"problemMatcher": [],
+			"label": "Build all",
+			"dependsOn": [
+				"Build",
+				"Build web debug",
+				"Build web tests"
+			]
+		},
+		{
+			"type": "process",
+			"runOptions": {
+				"instanceLimit": 1
+			},
+			"problemMatcher": [],
+			"label": "Run Temp DBs",
+			"command": "${workspaceFolder}/dbstart.sh",
+			"args": [
+			]
+		},
+		{
+			"type": "process",
+			"runOptions": {
+				"instanceLimit": 1
+			},
+			"problemMatcher": [],
+			"label": "Stop Temp DBs",
+			"command": "${workspaceFolder}/dbstop.sh",
+			"args": [
+			]
+		}
+	]
+}

package/CONTRIBUTING.md

@@ -0,0 +1,157 @@
+# Contributing to HotStaq
+
+Love HotStaq and want to help? Thanks so much, there's something to do for everybody!
+
+Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
+
+Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
+
+## Using the issue tracker
+
+The [issue tracker](https://github.com/OurFreeLight/HotStaq/issues) is
+the preferred channel for [bug reports](#bugs), [features requests](#features)
+and [submitting pull requests](#pull-requests).
+
+<a name="bugs"></a>
+
+## Bug reports
+
+A bug is a _demonstrable problem_ that is caused by the code in the repository.
+Good bug reports are extremely helpful - thank you!
+
+Guidelines for bug reports:
+
+1.  **Use the GitHub issue search** &mdash; check if the issue has already been reported.
+
+2.  **Check if the issue has been fixed** &mdash; try to reproduce it using the latest `master` or development branch in the repository.
+
+3.  **Isolate the problem** &mdash; ideally create a [reduced test case](https://css-tricks.com/reduced-test-cases/) and a live example.
+
+4.  **Use the bug report template** &mdash; please fill in the template which appears when you open a new issue.
+
+A good bug report shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What browser(s) and OS
+experience the problem? What would you expect to be the outcome? All these details will help people to fix any potential bugs.
+
+Example:
+
+> ## Description
+> A clear and concise description of what the bug is.
+>
+> Any other information you want to share that is relevant to the issue being
+> reported. This might include the lines of code that you have identified as
+> causing the bug, and potential solutions (and your opinions on their
+> merits).
+>
+> ## Steps to reproduce
+> Steps to reproduce the behavior:
+>
+> 1.  This is the first step
+> 2.  This is the second step
+> 3.  Further steps, etc.
+>
+> (Add link to a demo on https://jsfiddle.net or similar if possible)
+>
+> **Expected behavior**
+> A clear and concise description of what you expected to happen.
+>
+> **Screenshots**
+> If applicable, add screenshots to help explain your problem.
+>
+> ## Versions
+>
+> - HotStaq:
+> - Node/NPM:
+> - Browser:
+
+<a name="features"></a>
+
+## Feature requests
+
+Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to _you_ to make a strong case to convince the project's developers of the merits of this feature. Please provide as many details and as much context as possible.
+
+There is also a template for feature requests. Please make sure to use it.
+
+<a name="pull-requests"></a>
+
+## Pull requests
+
+Good pull requests - patches, improvements, new features - are a fantastic
+help. They should remain focused in scope and avoid containing unrelated
+commits.
+
+**Please ask first** before embarking on any significant pull request (e.g.
+implementing features, refactoring code, porting to a different language),
+otherwise you risk spending a lot of time working on something that the
+project's developers might not want to merge into the project.
+
+Please adhere to the coding conventions used throughout a project (indentation,
+accurate comments, etc.) and any other requirements (such as test coverage).
+
+Since the `master` branch is what people actually use in production, we have a
+`dev` branch that unstable changes get merged into first. Only when we
+consider that stable we merge it into the `master` branch and release the
+changes for real.
+
+Adhering to the following process is the best way to get your work
+included in the project:
+
+1.  [Fork](https://help.github.com/articles/fork-a-repo/) the project, clone your fork, and configure the remotes:
+
+    ```bash
+    # Clone your fork of the repo into the current directory
+    git clone https://github.com/<your-username>/HotStaq.git
+    # Navigate to the newly cloned directory
+    cd HotStaq
+    # Assign the original repo to a remote called "upstream"
+    git remote add upstream https://github.com/OurFreeLight/HotStaq.git
+    ```
+
+2.  If you cloned a while ago, get the latest changes from upstream:
+
+    ```bash
+    git checkout dev
+    git pull upstream dev
+    ```
+
+3.  Create a new topic branch (off the `dev` branch) to contain your feature, change, or fix:
+
+    ```bash
+    git checkout -b <topic-branch-name>
+    ```
+
+4.  Commit your changes in logical chunks. Please adhere to these [git commit message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) or your code is unlikely be merged into the main project. Use Git's [interactive rebase](https://help.github.com/articles/about-git-rebase/) feature to tidy up your commits before making them public.
+
+5.  Locally merge (or rebase) the upstream dev branch into your topic branch:
+
+    ```bash
+    git pull [--rebase] upstream dev
+    ```
+
+6.  Push your topic branch up to your fork:
+
+    ```bash
+    git push origin <topic-branch-name>
+    ```
+
+7.  [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
+    with a clear title and description.
+
+**IMPORTANT**: By submitting a patch, you agree to allow the project
+owners to license your work under the terms of the [MIT License](https://github.com/OurFreeLight/HotStaq/blob/master/LICENSE.md).
+
+# Collaborating guidelines
+
+You can find the list of all contributors in [README.md](./README.md).
+
+There are few basic rules to ensure high quality of the boilerplate:
+
+- Before merging, a PR requires at least two approvals from the collaborators unless it's an architectural change, a large feature, etc. If it is, then at least 50% of the core team have to agree to merge it, with every team member having a full veto right. (i.e. every single one can block any PR)
+- A PR should remain open for at least two days before merging (does not apply for trivial contributions like fixing a typo). This way everyone has enough time to look into it.
+
+You are always welcome to discuss and propose improvements to this guideline.
+
+# Add yourself as a contributor
+
+This project follows the [All Contributors specification](https://allcontributors.org/). To add yourself to the table of contributors in the README file, please use the [bot](https://allcontributors.org/docs/en/bot/overview) or the [CLI](https://allcontributors.org/docs/en/cli/overview) as part of your PR.
+
+If you've already added yourself to the list and are making a new type of contribution, you can run it again and select the new contribution type.

package/README.md

@@ -0,0 +1,126 @@
+# HotStaq
+HotStaq is a client-side HTML preprocessor, with a design similar to that of PHP. Tech stacks have grown in size significantly over the years, and it can be hard for small teams to efficiently utilize all the different tech stacks properly. HotStaq helps reduce the headache of maintaining all the various tech while ensuring the application's security and quality.
+
+Developers can quickly create their frontend and backends securely while adding their unit tests along the way in code During development, HotStaq developers know they can generate Dockerfiles to easily deploy their application to Kubernetes or Docker Swarm.
+
+For more information, please visit: [HotStaq](https://hotstaq.com)
+
+## Getting started
+First you gotta install like so:
+```console
+npm -g install hotstaq
+```
+
+Now you can create your project by entering:
+```console
+hotstaq create my-app
+```
+
+Run the development web server:
+
+```console
+cd my-app
+
+hotstaq start
+```
+
+Your site starts at `http://localhost:8080`.
+
+Open `public/index.hott` and change your landing page. Refresh your browser to see your changes immediately.
+
+That's it!
+
+## Running database tests
+Make sure you have Docker installed, then do:
+```console
+./dbstart.sh
+```
+
+This will launch the temporary MariaDB and InfluxDB databases.
+
+After testing/debugging you can stop them by entering:
+```console
+./dbstop.sh
+```
+
+## Environment Variables
+You can configure how HotStaq starts by using:
+* DATABASE_TYPE
+	* Type: string
+	* Description: The type of database to use.
+	* Accepted values:
+		* mysql
+		* influx
+* DATABASE_SERVER
+	* Type: string
+	* Description: The url to the database server to connect to.
+	* Accepted values:
+		* MySql example: 127.0.0.1
+		* Influx example: http://127.0.0.1:8086
+* DATABASE_PORT
+	* Type: number
+	* Description: The database port to use.
+	* Accepted values:
+		* Any integer.
+* DATABASE_USERNAME
+	* Type: string
+	* Description: The database username to use.
+	* Accepted values:
+		* Any string.
+* DATABASE_PASSWORD
+	* Type: string
+	* Description: The database password to use.
+	* Accepted values:
+		* Any string.
+* DATABASE_ORG
+	* Type: string
+	* Description: The organization that contains the database. For Influx use.
+	* Accepted values:
+		* Any string.
+* DATABASE_TOKEN
+	* Type: string
+	* Description: The database token to use. For Influx use.
+	* Accepted values:
+		* Any string.
+* DATABASE_SCHEMA
+	* Type: string
+	* Description: The database schema (or bucket) to use.
+	* Accepted values:
+		* Any string.
+* SELENIUM_REMOTE_SERVER
+	* Type: string
+	* Description: The remote selenium server to do web browser tests with.
+	* Accepted values:
+		* Any valid url.
+* SELENIUM_WINDOW_WIDTH
+	* Type: number
+	* Description: The width of the new browser window.
+	* Accepted values:
+		* Any integer.
+* SELENIUM_WINDOW_HEIGHT
+	* Type: number
+	* Description: The height of the new browser window.
+	* Accepted values:
+		* Any integer.
+* TESTING_DEVTOOLS
+	* Type: number
+	* Description: Set to 1 if you want chrome to open the dev tools as browser tests start. This is only for testing.
+	* Accepted values:
+		* 0
+		* 1
+* TESTING_REMOTE_SERVER
+	* Type: string
+	* Description: The remote server to use during browser tests.
+	* Accepted values:
+		* Any valid url.
+
+## Developing
+To get started developing you'll need to install:
+```console
+npm -g install typescript webpack-cli@4 typedoc
+```
+
+To run browser tests, you'll need to have the correct version of [chromedriver](https://chromedriver.chromium.org/) installed for the version of Chrome you are running on your machine.
+
+## Possible Future Compiler
+I'd like to create a CLI tool that compresses the entire public html directory into a zip file which can be downloaded and unzipped during runtime by the client's web browser then display the pages. During the compilation phase it would look for vulnerabilities and report them; for example when embedding JS files, if integrity hashes are missing, it would complain.

package/bin/hotstaq

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+
+require ("../build/src/cli.js");

package/bin/hotstaq.cmd

@@ -0,0 +1 @@
+node ../build/src/cli.js %*