├── kubernetes ├── Makefile ├── scripts │ └── deploy.sh ├── illa-builder.yaml └── README.md ├── tips ├── assets │ └── images │ │ └── connect-to-local-database.png ├── how-to-use-my-own-external-postgres-databaseas-datastore-for-illa-builder.md └── how-to-connect-my-postgres-database-in-resource.md ├── docker-compose ├── docker-compose.yaml └── README.md ├── utils └── reinstall-docker-with-ubuntu.sh ├── known-issues └── known-issues.md ├── README.md └── LICENSE /kubernetes/Makefile: -------------------------------------------------------------------------------- 1 | .PHONY: all deploy 2 | 3 | all: deploy 4 | 5 | deploy: 6 | /bin/bash scripts/deploy.sh 7 | -------------------------------------------------------------------------------- /kubernetes/scripts/deploy.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | 4 | # deploy 5 | kubectl apply -f ./illa-builder.yaml 6 | 7 | kubectl get deployments; 8 | -------------------------------------------------------------------------------- /tips/assets/images/connect-to-local-database.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/illacloud/deploy-illa-manually/HEAD/tips/assets/images/connect-to-local-database.png -------------------------------------------------------------------------------- /docker-compose/docker-compose.yaml: -------------------------------------------------------------------------------- 1 | # illa-builder 2 | 3 | version: "3.9" 4 | 5 | services: 6 | illa-builder: 7 | container_name: illa-builder 8 | restart: always 9 | image: "illasoft/illa-builder:latest" 10 | ports: 11 | - "80:2022" 12 | volumes: 13 | - illa_database:/opt/illa/database:rw 14 | - illa_drive:/opt/illa/drive:rw 15 | 16 | volumes: 17 | illa_database: 18 | illa_drive: 19 | -------------------------------------------------------------------------------- /docker-compose/README.md: -------------------------------------------------------------------------------- 1 | Deploy All-in-One docker Image by Docker Compose 2 | ------------------------------------------------ 3 | 4 | 5 | # Desc 6 | 7 | This documents describe how to deploy illa units with docker compose. 8 | 9 | Note: 10 | 11 | We highly recommended deploying with our auto-deploy tools [illa-cli](https://github.com/illacloud/illa). 12 | 13 | 14 | 15 | # Index 16 | 17 | - [Desc](#desc) 18 | - [Index](#index) 19 | - [Run](#run) 20 | 21 | 22 | # Run 23 | 24 | Install docker-ce and clone this repo, into docker-compose folder and type: 25 | 26 | ```sh 27 | docker compose up -d 28 | ``` 29 | 30 | The illa-builder will listen on all interface with 80 port. 31 | 32 | Login with default username **```root```** and password **```password```**. 33 | -------------------------------------------------------------------------------- /utils/reinstall-docker-with-ubuntu.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | echo '' 4 | echo 'Removing old docker installation.' 5 | echo '' 6 | 7 | sudo apt-get remove docker docker-engine docker.io containerd runc -y 8 | 9 | echo '' 10 | echo 'Do update and add ubuntu official install source.' 11 | echo '' 12 | 13 | sudo apt-get update 14 | sudo apt-get install -y \ 15 | ca-certificates \ 16 | curl \ 17 | gnupg \ 18 | lsb-release 19 | 20 | sudo mkdir -p /etc/apt/keyrings 21 | 22 | curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg 23 | 24 | echo \ 25 | "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \ 26 | $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null 27 | 28 | sudo apt-get update 29 | 30 | echo '' 31 | echo 'installing docker-ce.' 32 | echo '' 33 | 34 | sudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin 35 | 36 | docker info 37 | 38 | echo 'DONE!' 39 | -------------------------------------------------------------------------------- /kubernetes/illa-builder.yaml: -------------------------------------------------------------------------------- 1 | --- 2 | # illa-builder deployment 3 | apiVersion: apps/v1 4 | kind: Deployment 5 | metadata: 6 | namespace: default 7 | name: illa-builder 8 | spec: 9 | selector: 10 | matchLabels: 11 | app.kubernetes.io/name: illa-builder 12 | replicas: 1 13 | template: 14 | metadata: 15 | labels: 16 | app.kubernetes.io/name: illa-builder 17 | infrastructure: fargate 18 | spec: 19 | containers: 20 | - image: docker.io/illasoft/illa-builder:latest 21 | imagePullPolicy: Always 22 | name: illa-builder 23 | ports: 24 | - containerPort: 2022 25 | env: 26 | - name: ILLA_DEPLOY_MODE 27 | value: "self-host" 28 | --- 29 | # illa-builder service 30 | apiVersion: v1 31 | kind: Service 32 | metadata: 33 | namespace: default 34 | name: illa-builder 35 | spec: 36 | ports: 37 | - port: 2022 38 | targetPort: 2022 39 | protocol: TCP 40 | type: NodePort 41 | selector: 42 | app.kubernetes.io/name: illa-builder 43 | infrastructure: fargate 44 | -------------------------------------------------------------------------------- /tips/how-to-use-my-own-external-postgres-databaseas-datastore-for-illa-builder.md: -------------------------------------------------------------------------------- 1 | How to Use My Own External Postgres Database as Datastore for Illa-Builder? 2 | --------------------------------------------------------------------------- 3 | 4 | 5 | ## Desc 6 | 7 | This document is for the user who wants to use their own postgres database as a datastore for illa-builder. 8 | 9 | 10 | ## Database DDL 11 | 12 | Connect to your own postgres database and run the following SQL to create the database and table. 13 | 14 | The database DDLs are in this script: 15 | 16 | [https://github.com/illacloud/build-all-in-one-image/blob/main/scripts/postgres-init.sh](https://github.com/illacloud/build-all-in-one-image/blob/main/scripts/postgres-init.sh) 17 | 18 | 19 | ## Run Image 20 | 21 | Then config the docker run command and run it. 22 | 23 | ```bash 24 | docker run -d \ 25 | --name illa-builder \ 26 | -p 80:2022 \ 27 | -e ILLA_PG_ADDR={your_pg_server} \ 28 | -e ILLA_PG_PORT=5433 \ 29 | -e ILLA_PG_USER=illa_builder \ 30 | -e ILLA_PG_PASSWORD=illa2022 \ 31 | -e ILLA_PG_DATABASE=illa_builder \ 32 | -e ILLA_SUPERVISOR_PG_ADDR={your_pg_server} \ 33 | -e ILLA_SUPERVISOR_PG_PORT=5433 \ 34 | -e ILLA_SUPERVISOR_PG_USER=illa_supervisor \ 35 | -e ILLA_SUPERVISOR_PG_PASSWORD=illa2022 \ 36 | -e ILLA_SUPERVISOR_PG_DATABASE=illa_supervisor \ 37 | illasoft/illa-builder:latest 38 | ``` 39 | 40 | That's it. 41 | -------------------------------------------------------------------------------- /known-issues/known-issues.md: -------------------------------------------------------------------------------- 1 | known-issues 2 | ------------ 3 | 4 | 5 | # Mount Type Issue 6 | 7 | Run ```illa deploy --self -port=1000 -s={your-ip-address}``` or ```run-official-image.sh```, return following error: 8 | 9 | ``` 10 | Docker responded with status code 400: invalid mount config for type "bind": bind source path does not exist: /tmp/illa-data 11 | ``` 12 | 13 | For now, the mount type only supports ```mount```, please config ```docker -v``` as ```mount``` mode. Or reinstall the docker by following scripts. 14 | 15 | - [reinstall-docker-with-ubuntu.sh](../utils/reinstall-docker-with-ubuntu.sh) 16 | 17 | And run deploy command again. 18 | 19 | 20 | 21 | # Error: file access denied (cmd.StorageErr) 22 | 23 | The error info like: 24 | 25 | ``` 26 | API: SYSTEM() 27 | Time: 23:20:24 UTC 04/17/2023 28 | DeploymentID: c0e0ac14-c375-41e8-9e4d-96e1c34fa987 29 | Error: file access denied (cmd.StorageErr) 30 | 2: cmd/fs-v1.go:305:cmd.(*FS0bjects).NSScanner() 31 | 1: cmd/data-scanner.go:151:cmd.runDataScanner() 32 | API :SYSTEM() 33 | Time: 23:21:24 UTC 04/17/2023 34 | DeploymentID: c0e0ac14-c375-41e8-9e4d-96e1c34fa987 35 | Error: file access denied (cmd.StorageErr) 36 | 2: cmd/fs-v1.go:305:cmd.(*FS0bjects).NSScanner() 37 | 1: cmd/data-scanner.go:151:cmd.runDataScanner() 38 | ``` 39 | 40 | Illa use minio for internal object storage, and the minio compatible file system list are here (linux environment): 41 | - TMPFS 42 | - EXT 43 | - HFS 44 | - MSDOS 45 | - REISERFS 46 | - NTFS 47 | - XFS 48 | - AUFS 49 | - NFS 50 | - EXT2OLD 51 | - EXT4 52 | - ecryptfs 53 | - overlayfs 54 | - zfs 55 | - cifs 56 | - wslfs 57 | 58 | [Compatible file system list from minio source code](https://github.com/minio/minio/blob/202d0b64eb5fb503310ee4ae5116bbdf3219257d/internal/disk/type_linux.go#L26) 59 | 60 | Other file systems will cause the compatible issue. So please make sure your filesystem is in these lists. 61 | -------------------------------------------------------------------------------- /tips/how-to-connect-my-postgres-database-in-resource.md: -------------------------------------------------------------------------------- 1 | How to Connect My Postgres Database in Resource 2 | ----------------------------------------------- 3 | 4 | 5 | ## Desc 6 | 7 | This document is for the user who wants to connect their postgres database in illa-builder. 8 | 9 | 10 | ## Can not Connect to `localhost` or `127.0.0.1`, why? 11 | 12 | ![connect-to-local-database](./assets/images/connect-to-local-database.png) 13 | 14 | The illa-builder are run in docker container. So the localhost means container it self. 15 | 16 | When you want to connect your database on your local machine. You can input your machine's LAN IP as connection address. 17 | 18 | 19 | ## Determine Connection Address 20 | 21 | Type linux command ```ip addr```. Then check out LAN IP address. 22 | 23 | ``` 24 | root@my-computer:/# ip addr 25 | 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 26 | link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 27 | inet 127.0.0.1/8 scope host lo 28 | valid_lft forever preferred_lft forever 29 | inet6 ::1/128 scope host 30 | valid_lft forever preferred_lft forever 31 | 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 32 | link/ether 1e:00:92:00:01:01 brd ff:ff:ff:ff:ff:ff 33 | inet 192.168.0.12/24 brd 192.168.0.255 scope global ens3 34 | valid_lft forever preferred_lft forever 35 | 3: docker0: mtu 1500 qdisc noqueue state UP group default 36 | link/ether 02:42:99:6e:3e:11 brd ff:ff:ff:ff:ff:ff 37 | inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 38 | valid_lft forever preferred_lft forever 39 | inet6 fe80::42:99ff:fe6e:3e11/64 scope link 40 | valid_lft forever preferred_lft forever 41 | 42 | ``` 43 | 44 | 45 | The Internet Assigned Numbers Authority (IANA) has assigned several address ranges to be used by private networks. 46 | 47 | Address ranges to be use by private networks are: 48 | 49 | - Class A: 10.0.0.0 to 10.255.255.255 50 | - Class B: 172.16.0.0 to 172.31.255.255 51 | - Class C: 192.168.0.0 to 192.168.255.255 52 | 53 | So, in the command return, the NIC **ens3** address **192.168.0.12**, is our LAN IP address. 54 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 |
2 | 3 | ILLA Design Logo 4 | 5 |
6 | 7 |

Deploy Illa Manually

8 | 9 |

Deploy illa utils manually. Docker and k8s are all avaliable in this repo.

10 | 11 | 12 |

13 | 14 | 15 | 16 | 17 |

18 | 19 | 20 | 21 | 22 | # Desc 23 | 24 | Deploy illa utils manually. Docker and k8s are all avaliable in this repo. 25 | 26 | (Note: We highly recommended deploying with our auto-deploy tools [illa-cli](https://github.com/illacloud/illa)) 27 | 28 | 29 | # Index 30 | 31 | * [Desc](#Desc) 32 | * [Quick Start](#quick-start) 33 | * [Build Docker All-in-One Image](https://github.com/illacloud/build-all-in-one-image) 34 | * [Run by Docker Compose](./docker-compose/docker-compose.md) 35 | * [Run by Kubernetes](./kubernetes/README.md) 36 | * [How to Build Your Own Illa Units and Run it Locallly](./build-by-yourself/README.md) 37 | * [Known Issues](./known-issues/known-issues.md) 38 | 39 | 40 | # Tips 41 | * [How to Connect My Postgres Database in Resource?](#how-to-connect-my-postgres-database-in-resource.md) 42 | * [How to Use My Own External Postgres Database as Datastore for Illa-Builder?](#how-to-use-my-own-external-postgres-databaseas-datastore-for-illa-builder.md) 43 | 44 | 45 | # Quick Start 46 | 47 | Just type: 48 | 49 | ```sh 50 | mkdir -p ~/illa/database; mkdir -p ~/illa/drive; 51 | docker run -d -p 80:2022 --name illa_builder -v ~/illa/database:/opt/illa/database -v ~/illa/drive:/opt/illa/drive illasoft/illa-builder:latest 52 | ``` 53 | 54 | And Login with default username **```root```** and password **```password```** (self-host mode (docker all-in-one image) only). 55 | -------------------------------------------------------------------------------- /kubernetes/README.md: -------------------------------------------------------------------------------- 1 | Deploy Docker Image by Docker Compose 2 | ------------------------------------- 3 | 4 | 5 | # Desc 6 | 7 | Build illa all-in-one image and run it by k8s on your machine. 8 | You can check out the scripts file which in [scripts](./scripts/) folder for more details. 9 | 10 | Note: 11 | 12 | We highly recommended deploying with our auto-deploy tools [illa-cli](https://github.com/illacloud/illa). 13 | 14 | # Index 15 | 16 | - [Desc](#desc) 17 | - [Index](#index) 18 | - [Run with official image](#run-with-official-image) 19 | - [For Database Persistent Storage](#for-database-persistent-storage) 20 | - [For HTTPS Config](#for-https-config) 21 | 22 | 23 | # Run with official image 24 | 25 | Install GNU make and type: 26 | 27 | ```sh 28 | make deploy 29 | ``` 30 | 31 | or just execute: 32 | 33 | ```sh 34 | /bin/bash scripts/deploy.sh 35 | ``` 36 | 37 | this command will pull illasoft official all-in-one image and deploy it on your kubernetes cluster. 38 | 39 | # For Database Persistent Storage 40 | 41 | Edit [illa-builder.yaml](illa-builder.yaml), add your IAAS persistent storage config on it. 42 | 43 | The database mount point at ```/opt/illa/database```. 44 | 45 | The object storage mount point at ```/opt/illa/drive```. 46 | 47 | # For HTTPS Config 48 | 49 | You can route the NodePort to your kubernetes cluster ingress gateway and rewrite to 443 port, and add https cert in your ingress gateway. 50 | 51 | Or, you can deploy an ingress gateway manually into your kubernetes server, config like this: 52 | 53 | ```yaml 54 | static_resources: 55 | listeners: 56 | - name: https_listener 57 | address: 58 | socket_address: 59 | address: 0.0.0.0 60 | port_value: 443 61 | filter_chains: 62 | - filters: 63 | - name: envoy.filters.network.http_connection_manager 64 | typed_config: 65 | "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager 66 | stat_prefix: https_listener 67 | route_config: 68 | name: local_route 69 | virtual_hosts: 70 | - name: illa_builder 71 | domains: 72 | - "illa.yourdomian.com" # replace with your domain 73 | routes: 74 | - match: 75 | prefix: "/" 76 | route: 77 | cluster: illa_builder 78 | http_filters: 79 | - name: envoy.filters.http.router 80 | typed_config: 81 | "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router 82 | transport_socket: 83 | name: envoy.transport_sockets.tls 84 | typed_config: 85 | "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext 86 | common_tls_context: 87 | tls_certificates: 88 | # replace this with your cert file 89 | - certificate_chain: 90 | filename: /your-cert-folder/fullchain.pem 91 | private_key: 92 | filename: /your-cert-folder/privkey.pem 93 | 94 | clusters: 95 | - name: illa_builder 96 | type: STRICT_DNS 97 | lb_policy: ROUND_ROBIN 98 | connect_timeout: 10s 99 | load_assignment: 100 | cluster_name: illa_builder 101 | endpoints: 102 | - lb_endpoints: 103 | - endpoint: 104 | address: 105 | socket_address: 106 | address: illa-builder 107 | port_value: 2022 108 | ``` 109 | 110 | that's all. 111 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright 2023 Illa Soft, Inc. 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | --------------------------------------------------------------------------------