Creates a new component project in the component root directory using a predefined template.
Operation is restricted to super_user roles only
operation (required) - must always be add_componentproject (required) - the name of the project you wish to createreplicated (optional) - if true, Harper will replicate the component to all nodes in the cluster. Must be a boolean.{
"operation": "add_component",
"project": "my-component"
}
{
"message": "Successfully added project: my-component"
}
Will deploy a component using either a base64-encoded string representation of a .tar file (the output from package_component) or a package value, which can be any valid NPM reference, such as a GitHub repo, an NPM package, a tarball, a local directory or a website.
If deploying with the payload option, Harper will decrypt the base64-encoded string, reconstitute the .tar file of your project folder, and extract it to the component root project directory.
If deploying with the package option, the package value will be written to harperdb-config.yaml. Then npm install will be utilized to install the component in the node_modules directory located in the hdb root. The value is a package reference, which should generally be a URL reference, as described here (it is also possible to include NPM registerd packages and file paths). URL package references can directly reference tarballs that can be installed as a package. However, the most common and recommended usage is to install from a Git repository, which can be combined with a tag to deploy a specific version directly from versioned source control. When using tags, we highly recommend that you use the semver directive to ensure consistent and reliable installation by NPM. In addition to tags, you can also reference branches or commit numbers. Here is an example URL package reference to a (public) Git repository that doesn't require authentication:
https://github.com/HarperDB/application-template#semver:v1.0.0
or this can be shortened to:
HarperDB/application-template#semver:v1.0.0
You can also install from private repository if you have an installed SSH keys on the server:
git+ssh:/git@github.com:my-org/my-app.git#semver:v1.0.0
Or you can use a Github token:
https://<my-token>@github.com/my-org/my-app#semver:v1.0.0
Or you can use a GitLab Project Access Token:
https://my-project:<my-token>@gitlab.com/my-group/my-project#semver:v1.0.0
Note that your component will be installed by NPM. If your component has dependencies, NPM will attempt to download and install these as well. NPM normally uses the public registry.npmjs.org registry. If you are installing without network access to this, you may wish to define custom registry locations if you have any dependencies that need to be installed. NPM will install the deployed component and any dependencies in node_modules in the hdb root directory (typically ~/hdb/node_modules).
Note: After deploying a component a restart may be required
Operation is restricted to super_user roles only
operation (required) - must always be deploy_componentproject (required) - the name of the project you wish to deploypackage (optional) - this can be any valid GitHub or NPM referencepayload (optional) - a base64-encoded string representation of the .tar file. Must be a stringrestart (optional) - must be either a boolean or the string rolling. If set to rolling, a rolling restart will be triggered after the component is deployed, meaning that each node in the cluster will be sequentially restarted (waiting for the last restart to start the next). If set to true, the restart will not be rolling, all nodes will be restarted in parallel. If replicated is true, the restart operations will be replicated across the cluster.replicated (optional) - if true, Harper will replicate the component to all nodes in the cluster. Must be a boolean.install_command (optional) - A command to use when installing the component. Must be a string. This can be used to install dependencies with pnpm or yarn, for example, like: "install_command": "npm install -g pnpm && pnpm install"{
"operation": "deploy_component",
"project": "my-component",
"payload": "A very large base64-encoded string representation of the .tar file"
}
{
"operation": "deploy_component",
"project": "my-component",
"package": "HarperDB/application-template",
"replicated": true
}
{
"message": "Successfully deployed: my-component"
}
Creates a temporary .tar file of the specified project folder, then reads it into a base64-encoded string and returns an object with the string and the payload.
Operation is restricted to super_user roles only
operation (required) - must always be package_componentproject (required) - the name of the project you wish to packageskip_node_modules (optional) - if true, creates option for tar module that will exclude the project's node_modules directory. Must be a boolean{
"operation": "package_component",
"project": "my-component",
"skip_node_modules": true
}
{
"project": "my-component",
"payload": "LgAAAAAAAAAAAAAAAAAAA...AAAAAAAAAAAAAAAAAAAAAAAAAAAAA=="
}
Deletes a file from inside the component project or deletes the complete project.
If just project is provided it will delete all that projects local files and folders
Operation is restricted to super_user roles only
operation (required) - must always be drop_componentproject (required) - the name of the project you wish to delete or to delete from if using the file parameterfile (optional) - the path relative to your project folder of the file you wish to deletereplicated (optional) - if true, Harper will replicate the component deletion to all nodes in the cluster. Must be a boolean.restart (optional) - if true, Harper will restart after dropping the component. Must be a boolean.{
"operation": "drop_component",
"project": "my-component",
"file": "utils/myUtils.js"
}
{
"message": "Successfully dropped: my-component/utils/myUtils.js"
}
Gets all local component files and folders and any component config from harperdb-config.yaml
Operation is restricted to super_user roles only
operation (required) - must always be get_components{
"operation": "get_components"
}
{
"name": "components",
"entries": [
{
"package": "HarperDB/application-template",
"name": "deploy-test-gh"
},
{
"package": "@fastify/compress",
"name": "fast-compress"
},
{
"name": "my-component",
"entries": [
{
"name": "LICENSE",
"mtime": "2023-08-22T16:00:40.286Z",
"size": 1070
},
{
"name": "index.md",
"mtime": "2023-08-22T16:00:40.287Z",
"size": 1207
},
{
"name": "config.yaml",
"mtime": "2023-08-22T16:00:40.287Z",
"size": 1069
},
{
"name": "package.json",
"mtime": "2023-08-22T16:00:40.288Z",
"size": 145
},
{
"name": "resources.js",
"mtime": "2023-08-22T16:00:40.289Z",
"size": 583
},
{
"name": "schema.graphql",
"mtime": "2023-08-22T16:00:40.289Z",
"size": 466
},
{
"name": "utils",
"entries": [
{
"name": "commonUtils.js",
"mtime": "2023-08-22T16:00:40.289Z",
"size": 583
}
]
}
]
}
]
}
Gets the contents of a file inside a component project.
Operation is restricted to super_user roles only
operation (required) - must always be get_component_fileproject (required) - the name of the project where the file is locatedfile (required) - the path relative to your project folder of the file you wish to viewencoding (optional) - the encoding that will be passed to the read file call. Defaults to utf8{
"operation": "get_component_file",
"project": "my-component",
"file": "resources.js"
}
{
"message": "/**export class MyCustomResource extends tables.TableName {\n\t/ we can define our own custom POST handler\n\tpost(content) {\n\t\t/ do something with the incoming content;\n\t\treturn super.post(content);\n\t}\n\t/ or custom GET handler\n\tget() {\n\t\t/ we can modify this resource before returning\n\t\treturn super.get();\n\t}\n}\n */\n/ we can also define a custom resource without a specific table\nexport class Greeting extends Resource {\n\t/ a \"Hello, world!\" handler\n\tget() {\n\t\treturn { greeting: 'Hello, world!' };\n\t}\n}"
}
Creates or updates a file inside a component project.
Operation is restricted to super_user roles only
operation (required) - must always be set_component_fileproject (required) - the name of the project the file is located infile (required) - the path relative to your project folder of the file you wish to setpayload (required) - what will be written to the fileencoding (optional) - the encoding that will be passed to the write file call. Defaults to utf8replicated (optional) - if true, Harper will replicate the component update to all nodes in the cluster. Must be a boolean.{
"operation": "set_component_file",
"project": "my-component",
"file": "test.js",
"payload": "console.log('hello world')"
}
{
"message": "Successfully set component: test.js"
}
Adds an SSH key for deploying components from private repositories. This will also create an ssh config file that will be used when deploying the components.
Operation is restricted to super_user roles only
operation (required) - must always be add_ssh_keyname (required) - the name of the keykey (required) - the private key contents. Must be an ed25519 key. Line breaks must be delimited with \n and have a trailing \nhost (required) - the host for the ssh config (see below). Used as part of the package url when deploying a component using this keyhostname (required) - the hostname for the ssh config (see below). Used to map host to an actual domain (e.g. github.com)known_hosts (optional) - the public SSH keys of the host your component will be retrieved from. If hostname is github.com this will be retrieved automatically. Line breaks must be delimited with \nreplicated (optional) - if true, HarperDB will replicate the key to all nodes in the cluster. Must be a boolean. Operation is restricted to super_user roles only{
"operation": "add_ssh_key",
"name": "harperdb-private-component",
"key": "-----BEGIN OPENSSH PRIVATE KEY-----\nthis\nis\na\nfake\nkey\n-----END OPENSSH PRIVATE KEY-----\n",
"host": "harperdb-private-component.github.com",
"hostname": "github.com"
}
{
"message": "Added ssh key: harperdb-private-component"
}
#harperdb-private-component
Host harperdb-private-component.github.com
HostName github.com
User git
IdentityFile /hdbroot/ssh/harperdb-private-component.key
IdentitiesOnly yes
"package": "git+ssh:/git@<host>:<github-repo-path>.git#semver:v1.2.3"
"package": "git+ssh:/git@harperdb-private-component.github.com:HarperDB/harperdb-private-component.git#semver:v1.2.3"
Note that deploy_component with a package uses npm install so the url must be a valid npm format url. The above is an example of a url using a tag in the repo to install.
Updates the private key contents of an existing SSH key.
Operation is restricted to super_user roles only
operation (required) - must always be update_ssh_keyname (required) - the name of the key to be updatedkey (required) - the private key contents. Must be an ed25519 key. Line breaks must be delimited with \n and have a trailing \nreplicated (optional) - if true, Harper will replicate the key update to all nodes in the cluster. Must be a boolean.{
"operation": "update_ssh_key",
"name": "harperdb-private-component",
"key": "-----BEGIN OPENSSH PRIVATE KEY-----\nthis\nis\na\nNEWFAKE\nkey\n-----END OPENSSH PRIVATE KEY-----\n",
"host": "harperdb-private-component.github.com",
"hostname": "github.com"
}
{
"message": "Updated ssh key: harperdb-private-component"
}
Deletes a SSH key. This will also remove it from the generated SSH config.
Operation is restricted to super_user roles only
operation (required) - must always be delete_ssh_keyname (required) - the name of the key to be deletedreplicated (optional) - if true, Harper will replicate the key deletion to all nodes in the cluster. Must be a boolean.{
"name": "harperdb-private-component"
}
{
"message": "Deleted ssh key: harperdb-private-component"
}
List off the names of added SSH keys
Operation is restricted to super_user roles only
operation (required) - must always be list_ssh_keys{
"operation": "list_ssh_keys"
}
[
{
"name": "harperdb-private-component"
}
]
Note: Additional SSH keys would appear as more objects in this array
Set SSH Known HostsSets the SSH known_hosts file. This will overwrite the file.
Operation is restricted to super_user roles only
operation (required) - must always be set_ssh_known_hostsknown_hosts (required) - The contents to set the known_hosts to. Line breaks must be delimite d withreplicated (optional) - if true, Harper will replicate the known hosts to all nodes in the cluster. Must be a boolean.{
"operation": "set_ssh_known_hosts",
"known_hosts": "github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEmKSENjQEezOmxkZMy7opKgwFB9nkt5YRrYMjNuG5N87uRgg6CLrbo5wAdT/y6v0mKV0U2w0WZ2YB/++Tpockg=\ngithub.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl\ngithub.com ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCj7ndNxQowgcQnjshcLrqPEiiphnt+VTTvDP6mHBL9j1aNUkY4Ue1gvwnGLVlOhGeYrnZaMgRK6+PKCUXaDbC7qtbW8gIkhL7aGCsOr/C56SJMy/BCZfxd1nWzAOxSDPgVsmerOBYfNqltV9/hWCqBywINIR+5dIg6JTJ72pcEpEjcYgXkE2YEFXV1JHnsKgbLWNlhScqb2UmyRkQyytRLtL+38TGxkxCflmO+5Z8CSSNY7GidjMIZ7Q4zMjA2n1nGrlTDkzwDCsw+wqFPGQA179cnfGWOWRVruj16z6XyvxvjJwbz0wQZ75XK5tKSb7FNyeIEs4TT4jk+S4dhPeAUC5y+bDYirYgM4GC7uEnztnZyaVWQ7B381AK4Qdrwt51ZqExKbQpTUNn+EjqoTwvqNj4kqx5QUCI0ThS/YkOxJCXmPUWZbhjpCg56i+2aB6CmK2JGhn57K5mj0MNdBXA4/WnwH6XoPWJzK5Nyu2zB3nAZp+S5hpQs+p1vN1/wsjk=\n"
}
{
"message": "Known hosts successfully set"
}
Gets the contents of the known_hosts file
Operation is restricted to super_user roles only
operation (required) - must always be get_ssh_known_hosts{
"operation": "get_ssh_known_hosts"
}
{
"known_hosts": "github.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEmKSENjQEezOmxkZMy7opKgwFB9nkt5YRrYMjNuG5N87uRgg6CLrbo5wAdT/y6v0mKV0U2w0WZ2YB/++Tpockg=\ngithub.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOMqqnkVzrm0SdG6UOoqKLsabgH5C9okWi0dh2l9GKJl\ngithub.com ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCj7ndNxQowgcQnjshcLrqPEiiphnt+VTTvDP6mHBL9j1aNUkY4Ue1gvwnGLVlOhGeYrnZaMgRK6+PKCUXaDbC7qtbW8gIkhL7aGCsOr/C56SJMy/BCZfxd1nWzAOxSDPgVsmerOBYfNqltV9/hWCqBywINIR+5dIg6JTJ72pcEpEjcYgXkE2YEFXV1JHnsKgbLWNlhScqb2UmyRkQyytRLtL+38TGxkxCflmO+5Z8CSSNY7GidjMIZ7Q4zMjA2n1nGrlTDkzwDCsw+wqFPGQA179cnfGWOWRVruj16z6XyvxvjJwbz0wQZ75XK5tKSb7FNyeIEs4TT4jk+S4dhPeAUC5y+bDYirYgM4GC7uEnztnZyaVWQ7B381AK4Qdrwt51ZqExKbQpTUNn+EjqoTwvqNj4kqx5QUCI0ThS/YkOxJCXmPUWZbhjpCg56i+2aB6CmK2JGhn57K5mj0MNdBXA4/WnwH6XoPWJzK5Nyu2zB3nAZp+S5hpQs+p1vN1/wsjk=\n"
}
This operation is deprecated, as it is handled automatically by deploy_component and restart. Executes npm install against specified custom function projects.
Operation is restricted to super_user roles only
operation (required) - must always be install_node_modulesprojects (required) - must ba an array of custom functions projects.dry_run (optional) - refers to the npm --dry-run flag: https://docs.npmjs.com/cli/v8/commands/npm-install#dry-run. Defaults to false.{
"operation": "install_node_modules",
"projects": ["dogs", "cats"],
"dry_run": true
}
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4