From c2502d5f4492f63560f6d1af038cfeeabf9fd71a Mon Sep 17 00:00:00 2001 From: tiennm99 Date: Sat, 19 Sep 2026 12:43:05 +0700 Subject: [PATCH] chore: drop ollama, netdata, per-service licenses and stale plans Rename gitea-mirror-local to gitea-mirror. --- README.md | 4 +- alloy/LICENSE | 202 ------------------ couchbase/LICENSE | 201 ----------------- .../skills/gitea-mirror-maintenance/SKILL.md | 0 .../references/failure-taxonomy.md | 0 .../scripts/cleanup-failed-mirrors.ps1 | 0 .../scripts/detect-failed-mirrors.ps1 | 0 .../.env.example | 0 .../.gitignore | 0 .../README.md | 2 +- .../compose.yml | 0 netdata/LICENSE | 201 ----------------- netdata/README.md | 36 ---- netdata/docker-compose.yml | 32 --- ollama/LICENSE | 201 ----------------- ollama/README.md | 31 --- ollama/docker-compose.yml | 14 -- .../README.md | 75 ------- ...cs-manager-260918-1055-paseo-docs-audit.md | 152 ------------- ...arch-260918-1648-openhands-opencode-web.md | 153 ------------- traffmonetizer/LICENSE | 201 ----------------- 21 files changed, 2 insertions(+), 1503 deletions(-) delete mode 100644 alloy/LICENSE delete mode 100644 couchbase/LICENSE rename {gitea-mirror-local => gitea-mirror}/.claude/skills/gitea-mirror-maintenance/SKILL.md (100%) rename {gitea-mirror-local => gitea-mirror}/.claude/skills/gitea-mirror-maintenance/references/failure-taxonomy.md (100%) rename {gitea-mirror-local => gitea-mirror}/.claude/skills/gitea-mirror-maintenance/scripts/cleanup-failed-mirrors.ps1 (100%) rename {gitea-mirror-local => gitea-mirror}/.claude/skills/gitea-mirror-maintenance/scripts/detect-failed-mirrors.ps1 (100%) rename {gitea-mirror-local => gitea-mirror}/.env.example (100%) rename {gitea-mirror-local => gitea-mirror}/.gitignore (100%) rename {gitea-mirror-local => gitea-mirror}/README.md (98%) rename {gitea-mirror-local => gitea-mirror}/compose.yml (100%) delete mode 100644 netdata/LICENSE delete mode 100644 netdata/README.md delete mode 100644 netdata/docker-compose.yml delete mode 100644 ollama/LICENSE delete mode 100644 ollama/README.md delete mode 100644 ollama/docker-compose.yml delete mode 100644 plans/260918-1648-openhands-opencode-web/README.md delete mode 100644 plans/reports/docs-manager-260918-1055-paseo-docs-audit.md delete mode 100644 plans/reports/research-260918-1648-openhands-opencode-web.md delete mode 100644 traffmonetizer/LICENSE diff --git a/README.md b/README.md index 6596561..9d13c78 100644 --- a/README.md +++ b/README.md @@ -56,9 +56,7 @@ Each links to its own README for variables, ports, and storage. | [alloy](alloy/README.md) | Grafana Alloy shipping host and Docker telemetry to Grafana Cloud | | [code-server](code-server/README.md) | VS Code in the browser, as a remote dev box | | [couchbase](couchbase/README.md) | Couchbase Server | -| [gitea-mirror-local](gitea-mirror-local/README.md) | Gitea + PostgreSQL + gitea-mirror, mirroring GitHub repos | -| [netdata](netdata/README.md) | Netdata monitoring agent | -| [ollama](ollama/README.md) | Ollama LLM server | +| [gitea-mirror](gitea-mirror/README.md) | Gitea + PostgreSQL + gitea-mirror, mirroring GitHub repos | | [opencode-web](opencode-web/README.md) | opencode coding agent, served as a browser UI | | [openhands](openhands/README.md) | OpenHands coding agent, running each session in a container it spawns | | [paseo](paseo/README.md) | Paseo coding-agent daemon and web UI | diff --git a/alloy/LICENSE b/alloy/LICENSE deleted file mode 100644 index 57bc88a..0000000 --- a/alloy/LICENSE +++ /dev/null @@ -1,202 +0,0 @@ - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - - END OF TERMS AND CONDITIONS - - APPENDIX: How to apply the Apache License to your work. - - To apply the Apache License to your work, attach the following - boilerplate notice, with the fields enclosed by brackets "[]" - replaced with your own identifying information. (Don't include - the brackets!) The text should be enclosed in the appropriate - comment syntax for the file format. We also recommend that a - file or class name and description of purpose be included on the - same "printed page" as the copyright notice for easier - identification within third-party archives. - - Copyright [yyyy] [name of copyright owner] - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. - diff --git a/couchbase/LICENSE b/couchbase/LICENSE deleted file mode 100644 index 261eeb9..0000000 --- a/couchbase/LICENSE +++ /dev/null @@ -1,201 +0,0 @@ - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - - END OF TERMS AND CONDITIONS - - APPENDIX: How to apply the Apache License to your work. - - To apply the Apache License to your work, attach the following - boilerplate notice, with the fields enclosed by brackets "[]" - replaced with your own identifying information. (Don't include - the brackets!) The text should be enclosed in the appropriate - comment syntax for the file format. We also recommend that a - file or class name and description of purpose be included on the - same "printed page" as the copyright notice for easier - identification within third-party archives. - - Copyright [yyyy] [name of copyright owner] - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. diff --git a/gitea-mirror-local/.claude/skills/gitea-mirror-maintenance/SKILL.md b/gitea-mirror/.claude/skills/gitea-mirror-maintenance/SKILL.md similarity index 100% rename from gitea-mirror-local/.claude/skills/gitea-mirror-maintenance/SKILL.md rename to gitea-mirror/.claude/skills/gitea-mirror-maintenance/SKILL.md diff --git a/gitea-mirror-local/.claude/skills/gitea-mirror-maintenance/references/failure-taxonomy.md b/gitea-mirror/.claude/skills/gitea-mirror-maintenance/references/failure-taxonomy.md similarity index 100% rename from gitea-mirror-local/.claude/skills/gitea-mirror-maintenance/references/failure-taxonomy.md rename to gitea-mirror/.claude/skills/gitea-mirror-maintenance/references/failure-taxonomy.md diff --git a/gitea-mirror-local/.claude/skills/gitea-mirror-maintenance/scripts/cleanup-failed-mirrors.ps1 b/gitea-mirror/.claude/skills/gitea-mirror-maintenance/scripts/cleanup-failed-mirrors.ps1 similarity index 100% rename from gitea-mirror-local/.claude/skills/gitea-mirror-maintenance/scripts/cleanup-failed-mirrors.ps1 rename to gitea-mirror/.claude/skills/gitea-mirror-maintenance/scripts/cleanup-failed-mirrors.ps1 diff --git a/gitea-mirror-local/.claude/skills/gitea-mirror-maintenance/scripts/detect-failed-mirrors.ps1 b/gitea-mirror/.claude/skills/gitea-mirror-maintenance/scripts/detect-failed-mirrors.ps1 similarity index 100% rename from gitea-mirror-local/.claude/skills/gitea-mirror-maintenance/scripts/detect-failed-mirrors.ps1 rename to gitea-mirror/.claude/skills/gitea-mirror-maintenance/scripts/detect-failed-mirrors.ps1 diff --git a/gitea-mirror-local/.env.example b/gitea-mirror/.env.example similarity index 100% rename from gitea-mirror-local/.env.example rename to gitea-mirror/.env.example diff --git a/gitea-mirror-local/.gitignore b/gitea-mirror/.gitignore similarity index 100% rename from gitea-mirror-local/.gitignore rename to gitea-mirror/.gitignore diff --git a/gitea-mirror-local/README.md b/gitea-mirror/README.md similarity index 98% rename from gitea-mirror-local/README.md rename to gitea-mirror/README.md index 98142ca..59d929c 100644 --- a/gitea-mirror-local/README.md +++ b/gitea-mirror/README.md @@ -1,4 +1,4 @@ -# gitea-mirror-local +# gitea-mirror Self-hosted [Gitea](https://about.gitea.com/) backed by PostgreSQL, with [gitea-mirror](https://github.com/RayLabsHQ/gitea-mirror) mirroring GitHub diff --git a/gitea-mirror-local/compose.yml b/gitea-mirror/compose.yml similarity index 100% rename from gitea-mirror-local/compose.yml rename to gitea-mirror/compose.yml diff --git a/netdata/LICENSE b/netdata/LICENSE deleted file mode 100644 index 261eeb9..0000000 --- a/netdata/LICENSE +++ /dev/null @@ -1,201 +0,0 @@ - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - - END OF TERMS AND CONDITIONS - - APPENDIX: How to apply the Apache License to your work. - - To apply the Apache License to your work, attach the following - boilerplate notice, with the fields enclosed by brackets "[]" - replaced with your own identifying information. (Don't include - the brackets!) The text should be enclosed in the appropriate - comment syntax for the file format. We also recommend that a - file or class name and description of purpose be included on the - same "printed page" as the copyright notice for easier - identification within third-party archives. - - Copyright [yyyy] [name of copyright owner] - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. diff --git a/netdata/README.md b/netdata/README.md deleted file mode 100644 index edcf248..0000000 --- a/netdata/README.md +++ /dev/null @@ -1,36 +0,0 @@ -# netdata - -[Netdata](https://www.netdata.cloud) monitoring agent. - -Uses `docker-compose.yml`, and sets `restart: unless-stopped` and -`container_name: netdata` — unlike the platform-managed services described in -the [root README](../README.md). - -Runs with `network_mode: host` and `pid: host`, plus `SYS_PTRACE`/`SYS_ADMIN` -and an unconfined AppArmor profile, so it can read host processes and metrics. -The dashboard is therefore on the host's own `19999`, not a published port. - -## Environment - -| Variable | Purpose | -| --- | --- | -| `NETDATA_CLAIM_TOKEN` | Netdata Cloud claim token. Without it the agent runs standalone. | - -```sh -NETDATA_CLAIM_TOKEN= docker compose up -d -``` - -## Storage - -| Volume | Mount | Holds | -| --- | --- | --- | -| `netdataconfig` | `/etc/netdata` | Agent configuration | -| `netdatalib` | `/var/lib/netdata` | Metrics database, claim state | -| `netdatacache` | `/var/cache/netdata` | Cache | - -Host paths (`/`, `/proc`, `/sys`, `/var/log`, the Docker socket, dbus) are -mounted read-only for collection. - -## Related - -- [alloy](../alloy/README.md) — ships metrics to Grafana Cloud instead diff --git a/netdata/docker-compose.yml b/netdata/docker-compose.yml deleted file mode 100644 index cf53762..0000000 --- a/netdata/docker-compose.yml +++ /dev/null @@ -1,32 +0,0 @@ -version: '3' -services: - netdata: - image: netdata/netdata:stable - container_name: netdata - pid: host - network_mode: host - restart: unless-stopped - cap_add: - - SYS_PTRACE - - SYS_ADMIN - security_opt: - - apparmor:unconfined - volumes: - - netdataconfig:/etc/netdata - - netdatalib:/var/lib/netdata - - netdatacache:/var/cache/netdata - - /:/host/root:ro,rslave - - /etc/passwd:/host/etc/passwd:ro - - /etc/group:/host/etc/group:ro - - /etc/localtime:/etc/localtime:ro - - /proc:/host/proc:ro - - /sys:/host/sys:ro - - /etc/os-release:/host/etc/os-release:ro - - /var/log:/host/var/log:ro - - /var/run/docker.sock:/var/run/docker.sock:ro - - /run/dbus:/run/dbus:ro - -volumes: - netdataconfig: - netdatalib: - netdatacache: diff --git a/ollama/LICENSE b/ollama/LICENSE deleted file mode 100644 index 261eeb9..0000000 --- a/ollama/LICENSE +++ /dev/null @@ -1,201 +0,0 @@ - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - - END OF TERMS AND CONDITIONS - - APPENDIX: How to apply the Apache License to your work. - - To apply the Apache License to your work, attach the following - boilerplate notice, with the fields enclosed by brackets "[]" - replaced with your own identifying information. (Don't include - the brackets!) The text should be enclosed in the appropriate - comment syntax for the file format. We also recommend that a - file or class name and description of purpose be included on the - same "printed page" as the copyright notice for easier - identification within third-party archives. - - Copyright [yyyy] [name of copyright owner] - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. diff --git a/ollama/README.md b/ollama/README.md deleted file mode 100644 index 8393bcd..0000000 --- a/ollama/README.md +++ /dev/null @@ -1,31 +0,0 @@ -# ollama - -[Ollama](https://ollama.com) LLM server. CPU-only. - -Uses `docker-compose.yml`, publishes `11434`, and sets -`restart: unless-stopped` and `container_name: ollama` — unlike the -platform-managed services described in the [root README](../README.md). - -## Usage - -```sh -docker compose exec ollama ollama pull llama3.2 -docker compose exec ollama ollama run llama3.2 -``` - -The API is on `http://localhost:11434`: - -```sh -curl http://localhost:11434/api/generate -d '{ - "model": "llama3.2", - "prompt": "Why is the sky blue?", - "stream": false -}' -``` - -For GPU, add `deploy.resources.reservations.devices` for the NVIDIA runtime — -see the [Ollama Docker docs](https://hub.docker.com/r/ollama/ollama). - -## Storage - -`ollama` at `/root/.ollama` — pulled models and manifests. diff --git a/ollama/docker-compose.yml b/ollama/docker-compose.yml deleted file mode 100644 index d66a335..0000000 --- a/ollama/docker-compose.yml +++ /dev/null @@ -1,14 +0,0 @@ -version: '3' - -services: - ollama: - image: ollama/ollama - container_name: ollama - volumes: - - ollama:/root/.ollama - ports: - - 11434:11434 - restart: unless-stopped - -volumes: - ollama: diff --git a/plans/260918-1648-openhands-opencode-web/README.md b/plans/260918-1648-openhands-opencode-web/README.md deleted file mode 100644 index 8951625..0000000 --- a/plans/260918-1648-openhands-opencode-web/README.md +++ /dev/null @@ -1,75 +0,0 @@ -# Plan: openhands + opencode-web services - -Status: accepted, ready to implement -Branch: `dev` -Research: [../reports/research-260918-1648-openhands-opencode-web.md](../reports/research-260918-1648-openhands-opencode-web.md) - -## Outcome - -Two new service directories, each deployable as a Coolify/Dokploy compose -resource on the ARM64 host, following the repo conventions in `CLAUDE.md`. - -## Accepted decisions - -| Decision | Choice | Source | -| --- | --- | --- | -| opencode toolchain | local `Dockerfile` on `ghcr.io/anomalyco/opencode`, apk layer for bash/git/curl/openssh-client | user | -| openhands workspace | no host workspace — `SANDBOX_VOLUMES` omitted, agent works inside its sandbox container only | user | -| image tags | track `latest` | user | -| agent-server tag | pinned to `1.26.0-python`; GHCR publishes no floating tag for that repo (verified) | evidence | -| opencode state | one named volume on `/root`, as `paseo` does with `$HOME` | evidence: state spread across `.config`, `.local/share`, `.local/state`, `.cache` | -| opencode credentials | `docker compose exec … auth login`, persisted on the `/root` volume; no provider env vars | evidence: `auth login` is interactive, `exec` gives a TTY | -| `xdg-utils` | not installed | `apk --simulate`: pulls X11, 31 MiB image | - -## Non-goals - -- Publishing ports, `restart:`, `container_name:` — the platform owns these. -- Provider API keys as compose variables. -- Reaching OpenHands sandbox-hosted previews from outside (`SANDBOX_CONTAINER_URL_PATTERN`). - -## Phases - -### 1. `openhands/` - -`compose.yml`, `README.md`. No `Dockerfile`, no `.env.example` — nothing is -per-deployment once `SANDBOX_VOLUMES` is out. - -- `image: ghcr.io/openhands/openhands:latest` -- `environment:` `AGENT_SERVER_IMAGE_REPOSITORY`, `AGENT_SERVER_IMAGE_TAG` - (must-have group, repository first), `TZ`, `LOG_ALL_EVENTS` -- `extra_hosts: host.docker.internal:host-gateway` -- `volumes:` `openhands-state:/.openhands`, docker socket **read-write** -- README covers: rw socket is root-equivalent and why `:ro` cannot work, the - `extra_hosts` requirement, `/.openhands` not `$HOME`, why no host workspace, - why the agent-server tag is pinned while the app image is not, port 3000. - -### 2. `opencode-web/` - -`Dockerfile`, `compose.yml`, `.env.example`, `README.md`. - -- `Dockerfile`: `FROM ghcr.io/anomalyco/opencode:latest`, one apk layer, `WORKDIR /workspace`. -- `command: ['web', '--hostname', '0.0.0.0', '--port', '4096']` -- `environment:` `OPENCODE_SERVER_PASSWORD`/`OPENCODE_SERVER_USERNAME` group, - `TZ`, the four `GIT_*` -- `volumes:` `opencode-home:/root`, `opencode-workspace:/workspace` -- `.env.example` in compose order, generic values only. -- README covers: the vendor image ships only the binary, the unsecured-without-password - warning, `auth login` over `exec`, the harmless `xdg-open` stack trace on start, - `--cors` if the UI is cross-origin, port 4096. - -### 3. Root `README.md` - -Two rows in the services table, alphabetical. - -## Acceptance criteria - -- `docker compose config` parses in both directories. -- `opencode-web` image builds on arm64 and `git`, `bash` run inside it. -- No `ports:`, `restart:` or `container_name:` in either compose file. -- No rationale comments inside compose/Dockerfile; reasoning in the READMEs. -- `.env.example` carries no real hostname, identity or domain. - -## Validation - -`docker compose config`; `docker compose build` for opencode-web; `git diff` -review against `CLAUDE.md` conventions. diff --git a/plans/reports/docs-manager-260918-1055-paseo-docs-audit.md b/plans/reports/docs-manager-260918-1055-paseo-docs-audit.md deleted file mode 100644 index 918fe50..0000000 --- a/plans/reports/docs-manager-260918-1055-paseo-docs-audit.md +++ /dev/null @@ -1,152 +0,0 @@ -# paseo README audit — accuracy vs. actual files - -Scope: `paseo/README.md` against `paseo/Dockerfile`, `paseo/entrypoint.sh`, -`paseo/compose.yml`, `paseo/.env.example`, and the root `README.md`/`CLAUDE.md` -conventions. Stateful record of a point-in-time audit (2026-09-18) — not a -durable authority surface itself. - -## 1. Go/SDKMAN removal — cleanup verification - -The uncommitted diff (`git diff -- paseo/Dockerfile paseo/entrypoint.sh -paseo/README.md`) shows the removal was applied consistently across all three -files. Checked every surviving reference: - -- No occurrence of `Go`, `SDKMAN`, `JVM`, `Java`, or `Bun-in-the-image` claims - remains except two, both correctly reframed as history: - - `README.md:176-177` — "Bun used to be here for `omp` and went the same - way." (past tense, correct — Dockerfile has no Bun install step) - - `README.md:183-186` — "No other language toolchain is in the image. Go - and the JVM (through SDKMAN) used to be, and are not worth a rebuild..." - (past tense, correct — matches current Dockerfile/entrypoint.sh, neither - of which mention Go/SDKMAN) -- The `[SDKMAN](#sdkman)` link and the whole `## SDKMAN` section are gone from - `README.md`. `grep -n '\[.*\](#'` over the file found only four links, all - to `#agents`, which still exists (`## Agents` header) — **no orphaned anchor - survives**. -- The Image table (`README.md:157-163`) no longer has a `Go` row, and the old - catch-all apt row (`less nano jq unzip zip lsof psmisc ugrep bfs zsh sudo`) - was correctly split into `build-essential, sudo` / `zsh, nano` matching - `Dockerfile:8-10` exactly. `grep` for `jq|unzip|zip|lsof|psmisc|ugrep|bfs|less` - in README.md returns nothing — no stray reference to the other dropped - packages either. -- The Storage table (`README.md:143-146`) dropped "SDKMAN and its candidates" - from the `paseo-home` row — matches, since `entrypoint.sh` no longer - installs it. -- The intro (`README.md:3-7`) dropped `Go` and changed "shell tooling" to "a - shell" — matches `Dockerfile:8-10` (only `zsh`/`nano` remain, one shell). -- The `sudo secure_path` / `go` bullet and the "SDKMAN and agent installs" - wording in the `chpasswd`/`chown` bullets were removed — both were - Go/SDKMAN-specific and no longer apply. -- `Dockerfile` and `entrypoint.sh` header comments were updated to drop - "language toolchains" → "Python, a C toolchain" and "installs SDKMAN, then" - respectively — both still state *what*, not *why*, per the repo's comment - policy in root `CLAUDE.md`. - -**Result: the Go/SDKMAN cleanup is complete and accurate. No stale reasoning -bullets defend a removed decision.** - -## 2. Claim-by-claim verification (remainder of README.md) - -| README claim | Line | Status | Evidence | -| --- | --- | --- | --- | -| Adds `gh`, `glab`, Python, a C toolchain, and a shell | 3-6 | Verified | `Dockerfile:8-10,15-20,25-37` install exactly these | -| Agent CLIs not baked in, installed on start into `$HOME` | 6-7 | Verified | `entrypoint.sh:11-42` installs via `gosu paseo`, nothing in `Dockerfile` installs agent CLIs | -| `AGENT_CLIS=claude codex` is the `.env.example` default | 82-85 | Verified | `.env.example:28` | -| 6 agents, one row each, URLs and env names | 89-96 | Verified | `entrypoint.sh:12-19` `agent_installer()` matches every URL and name | -| Only 2 of 6 install by default, other 4 opt-in | 86-87 | Verified | same case statement, default is `claude codex` | -| Installer runs as `paseo` via `gosu`, lands in `~/.local/bin` or `~/.opencode/bin` | 98-101 | Verified | `entrypoint.sh:40` (`gosu paseo`); `Dockerfile:41` PATH has exactly those two dirs | -| Unrecognised agent name is logged and skipped | 111 | Verified | `entrypoint.sh:30-33` | -| Failed install is logged, container continues | 107-109 | Verified | `entrypoint.sh:41` `|| echo ... continuing` | -| Both agent dirs are on the image's `PATH` | 116 | Verified | `Dockerfile:41` | -| Shell rc entries don't reach the daemon's own env | 117-120 | Verified (design fact) | consistent with PATH being set at image level, not in `.bashrc`/`.zshrc` | -| `entrypoint.sh` wraps `paseo-docker-entrypoint`, runs before it, execs it at the end | 192-198 | Verified | `entrypoint.sh:45` `exec /usr/local/bin/paseo-docker-entrypoint "$@"`; `Dockerfile:45-46` copies it to `/usr/local/bin/entrypoint` and sets it as `ENTRYPOINT` | -| Password set via piped `chpasswd`, not an argument; empty `PASEO_PASSWORD` leaves account untouched/locked | 199-204 | Verified | `entrypoint.sh:7-9` — `printf ... | chpasswd`, guarded by `-n "${PASEO_PASSWORD:-}"` | -| `chown paseo:paseo /home/paseo` runs before any agent install | 205-207 | Verified | `entrypoint.sh:23` precedes the install loop at `entrypoint.sh:27` | -| PATH entries hardcoded as `/home/paseo/...` because `ENV` can't expand `$HOME` set later | 208-212 | Verified | `Dockerfile:41` uses literal `/home/paseo/...`, no `$HOME` is ever set as an `ENV` in this Dockerfile | -| `.env.example` variable list and defaults (`SHELL=/bin/zsh`, `PASEO_TRUSTED_PROXIES=uniquelocal`, `TZ=Asia/Ho_Chi_Minh`, `SERVICE_HOSTNAME=paseo`) match the Environment table's descriptions | 37-44 | Verified | `.env.example:1-42` — descriptions match 1:1 | -| `SERVICE_HOSTNAME` feeds both `hostname:` and `HOST` | 46-47 | Verified | `compose.yml:4,16` | -| **"the entrypoint chowns the volumes** [plural]**, then drops to the `paseo` user... with `gosu`"** | 190-191 | **Wrong / overstated** | `entrypoint.sh:23` chowns only `/home/paseo` (the `paseo-home` volume). Nothing in this repo's `entrypoint.sh` chowns `/workspace` (`paseo-workspace`). The plural implies both volumes; only one is proven from these files. The base image's own `paseo-docker-entrypoint` may chown `/workspace`, but that file is outside this repo and unverifiable here. Also: `entrypoint.sh` itself never runs `gosu` for the final user-drop — that happens inside the base entrypoint it `exec`s into, so attributing the `gosu`-drop to "the entrypoint" [singular, our script] is imprecise; it's accurate only if read as "the combined entrypoint chain," which the sentence doesn't say. **Suggested correction:** either soften to "chowns `/home/paseo`" (drop "volumes," matching what this repo's script actually does), or if `/workspace` really is chowned by the base entrypoint, say so explicitly and attribute the `gosu` line-drop to the base entrypoint, not to `entrypoint.sh`. | -| `build-essential` serves `npm`'s `node-gyp` and Python C extensions | 180-182 | Unverifiable | Neither `npm` nor Node.js is installed by this `Dockerfile`; if present it comes from the base image (`ghcr.io/getpaseo/paseo:latest`), which isn't inspectable from this repo. Not part of the recent diff — pre-existing claim, left as-is per "verified decision" rule (no new evidence to overturn it), flagged only for completeness. | -| Debian 12 ships Python 3.11 | 161 | Verified (general knowledge) | Debian 12 "bookworm" default `python3` is 3.11 | -| Port `6767`, published nowhere, daemon binds `PASEO_LISTEN` | 12, 26, 73-74 | Unverifiable from repo | No `ports:` or `PASEO_LISTEN` in `compose.yml`/`.env.example`; this is an upstream Paseo default, not something this repo's files assert or contradict. Pre-existing claim, not touched by the current diff — left as a previously-verified decision per audit rules. | -| `$HOME`/`.claude`/`.codex`/`.config/*` config dirs, `CLAUDE_CONFIG_DIR`/`CODEX_HOME`/`XDG_*` set by the base image | 148-153 | Unverifiable from repo | These env vars are not set in this repo's `Dockerfile`; claim is about the base image's own defaults, outside this repo's evidence. Pre-existing, not part of the diff. | - -## 3. Three-way variable sync — `compose.yml` ↔ `.env.example` ↔ README table - -**No mismatches.** Every variable is present in all three, and the reverse -holds too (nothing documented-but-absent, nothing present-but-undocumented): - -- `compose.yml` environment block reads: `PASEO_PASSWORD`, `PASEO_HOSTNAMES`, - `PASEO_TRUSTED_PROXIES`, `SHELL`, `AGENT_CLIS`, `TZ`, `GIT_NAME` (feeds - `GIT_AUTHOR_NAME`+`GIT_COMMITTER_NAME`), `GIT_EMAIL` (feeds - `GIT_AUTHOR_EMAIL`+`GIT_COMMITTER_EMAIL`), `SERVICE_HOSTNAME` (feeds - `hostname:` at `compose.yml:4` and `HOST` at `compose.yml:16`). -- `.env.example` declares exactly these 9 names, same values referenced. -- The README Environment table (`README.md:35-44`) has one row per name (with - `GIT_NAME`/`GIT_EMAIL` combined into one row, `SERVICE_HOSTNAME` calling out - the double use) — full coverage, no extra rows for anything not in - `compose.yml`/`.env.example`. - -**Ordering per root `CLAUDE.md`'s "Environment variable order" rule:** -`.env.example` orders each variable at the position of the *first* -`environment:` entry that reads it. Walking `compose.yml`'s `environment:` -block top to bottom: `PASEO_PASSWORD`, `PASEO_HOSTNAMES`, -`PASEO_TRUSTED_PROXIES`, `SHELL`, `AGENT_CLIS`, `TZ`, `GIT_NAME` (first hit is -`GIT_AUTHOR_NAME`), `GIT_EMAIL` (first hit is `GIT_AUTHOR_EMAIL`), -`SERVICE_HOSTNAME` (first hit *inside `environment:`* is `HOST=` at the -bottom). `.env.example` follows this exactly, in this order. The `hostname:` -key at `compose.yml:4` sits outside the `environment:` block the rule -describes, so `SERVICE_HOSTNAME` correctly lands last in `.env.example`, not -first. **Ordering is correct — no fix needed.** - -## 4. `.env.example` — generic-value check - -Checked every value against the "no real hostname, domain, git identity, -email, or account name" rule (root `CLAUDE.md` → composes `CLAUDE.md` -"Secrets" section): - -- `PASEO_PASSWORD=`, `PASEO_HOSTNAMES=`, `GIT_NAME=`, `GIT_EMAIL=` — empty. OK. -- `PASEO_TRUSTED_PROXIES=uniquelocal` — a keyword the daemon defines, not a - real value. OK. -- `SHELL=/bin/zsh`, `AGENT_CLIS=claude codex` — generic defaults, no personal - data. OK. -- `SERVICE_HOSTNAME=paseo` — this is "the service's own name," explicitly - allowed by the rule's own example. OK. -- `TZ=Asia/Ho_Chi_Minh` — not one of the rule's named forbidden categories - (hostname/domain/git identity/email/account name), so not a rule violation. - Flagged only as a borderline observation: it is a real, specific value - rather than an empty placeholder. No change recommended without the user's - input, since the rule doesn't cover timezone and other services in this - collection may follow the same pattern. - -**No violations found.** - -## 5. Suggestions (user decides) - -None. No missing tooling, package, or dependency surfaced during this audit — -per the task's hard constraint, none is proposed. - -## Recommended README fix - -One line, `README.md:190-191`: - -> The image stays root: the entrypoint chowns the volumes, then drops to the -> `paseo` user (uid 1000) with `gosu`. - -Correct to what `entrypoint.sh` actually shows (drop "volumes" → the specific -volume it chowns; drop the implication that this script itself does the -`gosu` user-drop): - -> The image stays root: `entrypoint.sh` chowns `/home/paseo`, then execs into -> the base entrypoint, which drops to the `paseo` user (uid 1000) with -> `gosu`. - -(Exact wording is the controller's call — this preserves the file's existing -voice and only removes the unproven "volumes" plural and the misattributed -`gosu` step.) - ---- - -Status: DONE_WITH_CONCERNS -Summary: The Go/SDKMAN removal was applied cleanly and completely across Dockerfile, entrypoint.sh, and README.md — no orphaned references, links, or stale reasoning bullets found, and all three-way variable sync (compose.yml/.env.example/README) and ordering checks pass with no mismatches. One pre-existing (not part of this diff) README claim overstates what entrypoint.sh proves: "chowns the volumes" implies both paseo-home and paseo-workspace, but the script only chowns /home/paseo. -Concerns/Blockers: The "chowns the volumes" line (README.md:190-191) needs either a narrower claim or explicit confirmation (unverifiable from this repo) that the base image's own entrypoint chowns /workspace too. diff --git a/plans/reports/research-260918-1648-openhands-opencode-web.md b/plans/reports/research-260918-1648-openhands-opencode-web.md deleted file mode 100644 index 0b9d194..0000000 --- a/plans/reports/research-260918-1648-openhands-opencode-web.md +++ /dev/null @@ -1,153 +0,0 @@ -# Research Report: openhands + opencode web as compose services - -Conducted 2026-09-18. Target: Linux ARM64 host, deployed via Coolify/Dokploy. - -## Executive Summary - -Both ship usable upstream images with arm64 manifests, so no cross-build -needed. They differ sharply in how much the image gives you. - -OpenHands is a complete product image: one container, port 3000, spawns -sibling *agent-server* containers through the host docker socket. It needs a -read-write socket, `host.docker.internal`, and a state directory. Nothing to -build. - -opencode's official image is the opposite — Alpine with a single static -`opencode` binary and nothing else. Verified by running it: no `git`, `bash`, -`curl`, `ssh`, `node`, `python3`. A coding agent whose shell tool has no shell -and no git is close to inert, so a local `Dockerfile` layer is required, the -way `paseo/` already does it. - -## Method - -- Sources: openhands docs (local-setup, runtimes/docker), opencode docs - (server, web), GHCR registry API, and direct `docker run` inspection. -- Date: 2026-09-18. Everything below verified against live registries or a - running container, not recalled. - -## Findings — OpenHands - -Upstream `docker run` (docs.openhands.dev/usage/local-setup): - -```bash -docker run -it --rm --pull=always \ - -e AGENT_SERVER_IMAGE_REPOSITORY=ghcr.io/openhands/agent-server \ - -e AGENT_SERVER_IMAGE_TAG=1.26.0-python \ - -e LOG_ALL_EVENTS=true \ - -v /var/run/docker.sock:/var/run/docker.sock \ - -v ~/.openhands:/.openhands \ - -p 3000:3000 \ - --add-host host.docker.internal:host-gateway \ - --name openhands-app \ - docker.openhands.dev/openhands/openhands:1.8 -``` - -Registry facts (GHCR API, 2026-09-18): - -| Image | arm64 | Note | -| --- | --- | --- | -| `ghcr.io/openhands/openhands:1.8` | yes | `docker.openhands.dev/...` is a mirror of this | -| `ghcr.io/openhands/openhands:latest` | yes | | -| `ghcr.io/openhands/agent-server:1.26.0-python` | yes | pulled by the app, not by compose | -| `ghcr.io/all-hands-ai/openhands` | yes | the old 0.x line, superseded | - -Constraints that shape the compose file: - -- **Socket must be read-write.** The app creates containers; connecting to a - unix socket needs write permission, so `:ro` — what `code-server/` uses — - breaks it. This is full host root-equivalent access. -- **`extra_hosts: host.docker.internal:host-gateway`** is mandatory. Sandbox - containers publish on the host, and the app reaches them through that name, - not over the compose network. -- **State lives at `/.openhands`** (repo root, not `$HOME`). -- **`SANDBOX_VOLUMES=host_path:/workspace:rw`** mounts code for the agent. The - path is resolved by the *host* daemon for the sibling container, so a named - volume or a path inside the app container does not work. -- Reverse-proxy knobs exist (`AGENT_SERVER_USE_HOST_NETWORK`, - `SANDBOX_CONTAINER_URL_PATTERN`) but only matter for reaching sandbox-hosted - previews from outside; the main UI does not need them. -- LLM credentials are set in the UI and persist in the state directory. - -## Findings — opencode web - -`opencode web` (opencode.ai/docs/web) starts the server *and* a browser UI. -`opencode serve` is the same server without the UI. Flags shared by both: -`--port` (default `0` = random), `--hostname` (default `127.0.0.1`), `--mdns`, -`--cors`. So a container needs `web --hostname 0.0.0.0 --port `. - -Auth: `OPENCODE_SERVER_PASSWORD` — *"If `OPENCODE_SERVER_PASSWORD` is not set, -the server will be unsecured."* `OPENCODE_SERVER_USERNAME` defaults to -`opencode`. Non-negotiable behind a public domain. - -Official image `ghcr.io/anomalyco/opencode` (the repo moved from `sst/`; -`ghcr.io/sst/opencode` now denies anonymous pulls). Tags are plain versions, -`1.0.94`–`1.0.196`, plus `latest`. amd64 + arm64. - -Inspected `latest` directly: - -``` -NAME="Alpine Linux" -git/bash/curl/ssh/node/python3/gh: all MISSING -Entrypoint: ["opencode"] User: root HOME=/root WorkingDir: / -opencode --version -> 1.18.31 -``` - -(Note the image tag series and `--version` disagree; the binary is what counts.) - -Consequences: - -- A local `Dockerfile` must add at minimum `git`, plus a shell, `curl`, - `openssh-client`, and whatever toolchain the agent is expected to run. -- `ENTRYPOINT ["opencode"]` means compose passes only `command: [web, ...]`. -- Config and credentials land under `/root`: `~/.config/opencode` (config), - `~/.local/share/opencode` (auth, storage). Both must persist. -- `opencode auth login` is interactive; in a container the practical path is - provider API keys as environment variables. - -## Comparison - -| | openhands | opencode-web | -| --- | --- | --- | -| Build | none, upstream image | local `Dockerfile` required | -| Port | 3000 | chosen, e.g. 4096 | -| Auth | in-app, after first login | `OPENCODE_SERVER_PASSWORD` or open to the world | -| Docker socket | required, rw | not needed | -| Isolation | agent runs in a sibling container | agent runs in *this* container | -| Workspace | host path via `SANDBOX_VOLUMES` | ordinary named volume | - -## Recommendations - -1. `openhands/` — no build, pin `ghcr.io/openhands/openhands` and the - `AGENT_SERVER_IMAGE_TAG`, named volume for `/.openhands`, rw socket, - `extra_hosts`, `SANDBOX_VOLUMES` as a variable so the host path is a - per-deployment value. -2. `opencode-web/` — `Dockerfile` on `ghcr.io/anomalyco/opencode`, apk layer - for git/bash/curl/openssh, named volumes for `/root/.config/opencode`, - `/root/.local/share/opencode` and `/workspace`, `command: [web, --hostname, - 0.0.0.0, --port, 4096]`, mandatory password. -3. Both get a README carrying the reasoning, and a root README row, per repo - convention. - -## Pitfalls - -- `:ro` on the OpenHands docker socket — silently fatal. -- Omitting `extra_hosts` — UI loads, agent never connects. -- Expecting `SANDBOX_VOLUMES` to accept a named volume. -- Shipping opencode without `OPENCODE_SERVER_PASSWORD` — an open agent with - shell access on a public domain. -- Assuming the vendor opencode image can run `git`. - -## References - -- https://docs.openhands.dev/usage/local-setup -- https://docs.openhands.dev/usage/runtimes/docker -- https://opencode.ai/docs/server/ -- https://opencode.ai/docs/web/ -- https://github.com/anomalyco/opencode - -## Unresolved - -- Which toolchains the opencode image should carry beyond git/bash/curl. -- Whether OpenHands should get a host workspace path at all, or run purely on - sandbox-internal storage. -- Whether to pin versions or track `latest`, as `code-server/` does. diff --git a/traffmonetizer/LICENSE b/traffmonetizer/LICENSE deleted file mode 100644 index 261eeb9..0000000 --- a/traffmonetizer/LICENSE +++ /dev/null @@ -1,201 +0,0 @@ - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - - END OF TERMS AND CONDITIONS - - APPENDIX: How to apply the Apache License to your work. - - To apply the Apache License to your work, attach the following - boilerplate notice, with the fields enclosed by brackets "[]" - replaced with your own identifying information. (Don't include - the brackets!) The text should be enclosed in the appropriate - comment syntax for the file format. We also recommend that a - file or class name and description of purpose be included on the - same "printed page" as the copyright notice for easier - identification within third-party archives. - - Copyright [yyyy] [name of copyright owner] - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License.