CJ/Pi-Hosted
1
0
Fork 0
Code Issues Pull Requests Activity

Upload files to "/"

Browse Source
This commit is contained in:
CJ
2026-01-18 12:00:22 +00:00
commit d5de0ee2c8
2 changed files with 763 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
LICENSE
+232
View File
@@ -0,0 +1,232 @@
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for software and other kinds of works.
The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.
Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and modification follow.
TERMS AND CONDITIONS
0. Definitions.
“This License” refers to version 3 of the GNU General Public License.
“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.
To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.
A “covered work” means either the unmodified Program or a work based on the Program.
To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
1. Source Code.
The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.
A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
7. Additional Terms.
“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
11. Patents.
A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's “contributor version”.
A contributor's “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.
You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.
README.md
+531
View File
@@ -0,0 +1,531 @@
# Pi-Hosted <a href='https://ko-fi.com/cjgameslive' target='_blank'><img height='35' align='right' style='border:0px;height:46px;' src='https://storage.ko-fi.com/cdn/kofi3.png?v=6' border='0' alt='Buy Me a Coffee at ko-fi.com' /></a>
I've used the ARM64 Template to pull my Docker images from [Pi-Hosted](https://github.com/pi-hosted/pi-hosted), these are just a few notes to remind me how I set a few thing up should anything happen to my Pi.
You can install various remote file browsers and terminals to access your set up online but I like using [Portable Apps](https://portableapps.com/) to run various programs, for Pi-Hosted stuff I would recommend checking out [Kitty](https://portableapps.com/apps/internet/kitty-portable) (there's also [PuTTY](https://portableapps.com/apps/internet/putty_portable) if you prefer) for SSH and [FileZilla](https://portableapps.com/apps/internet/filezilla_portable) for SFTP.
If you find any of this useful and would like to buy us a coffee please use the link at the top of this page.
<details>
# <summary><h4>Getting permission denied error when trying to access folders &#10067</h4></summary>
By default some folders are set up with different access meaning you may not have access to them (777 means everyone can read / write / execute, 755 means everyone can read / execute but ownly the owner can write, 644 means everyone can execute but only the owner can read / write. 777 is a major security risk and should never be used.)
The easiest way to gain SFTP access is to change the file ownership from `root` to your user (in this example `pi`):
```
sudo chown -R [user]:[group] [folder]
```
e.g.
```
sudo chown -R pi:pi /portainer/Files/Plex/Movies
```
to change ownership back to its defult:
```
sudo chown -R root:root /portainer/Files/Plex/Movies
```
</details>
<details>
<summary><h2>Setting up Docker and Portainer</h2></summary>
First ensure git is installed by typing `git` into the terminal, if it's not then run `sudo apt install git`.
*Optional:* Check what folers are already there by running `ls` and select one, or make one by running `mkdir <folder>` so that any prerequisite scripts are stored in one place and `cd <folder>` to enter the new folder`.
#### 1. First install docker:
```
wget -qO- https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/install_docker.sh | bash
```
Then reboot for good measure
```
sudo reboot
```
#### 2. Install Portainer:
```
wget -qO- https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/install_portainer.sh | bash
```
#### 3. Log in
Go to your Pi's IP followed by `:9000` in the browser to set up your account (e.g. `192.168.1.22:9000`)
Pick your username and password to create a user, select the Docker installation and click connect, click on your local installation, go to setting and enter your template.
<details>
<summary>Where to get your app template:</summary>
<br>
I'm using `https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/template/portainer-v2-arm64.json` but you can find different templates depending on your OS over on the [Pi-Hosted](https://github.com/pi-hosted/pi-hosted) GitHub page.
</details>
<details>
<summary>How to update Portainer:</summary>
<br>
```
wget -qO- https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/update_portainer.sh | bash
```
</details>
</details>
<details>
<summary><h2>Setting up <a href="https://github.com/bastienwirtz/homer/" target="_blank">Homer</a></h2></summary>
Find the Homer template in the App Templates list, click it and `Deploy the container`.
To edit your dashboard SSH in and edit `config.yml`:
```
sudo nano /portainer/Files/AppData/Config/Homer/assets/config.yml
```
Here you can change your dashboard title, subtitle, logo, default theme, etc. You can find my anonymised config [here](Homer/config.yml).
You can use icons for your various apps by using font awesome (such as a cloud `icon: "fas fa-cloud"`) or by uploading your own logos to the Pi (such as nginx `logo: "assets/icons/nginx.png"` which would be saved to `/portainer/Files/AppData/Config/Homer/assets/icons/`).
You can also display some custom service information, such as if PiHole is enabled and the % of blocked queeries by adding a type to the yml (`type: "PiHole"`). For a full list of available custom service information you can check [here](https://github.com/bastienwirtz/homer/blob/main/docs/customservices.md).
</details>
<details>
<summary><h2>Setting up <a href="https://github.com/benphelps/homepage" target="_blank">Homepage</a></h2></summary>
Find the Homer template in the App Templates list, click it and `Deploy the container`.
Ensure there are 3 volume links:
container: `/app/config` host:`/portainer/Files/AppData/Config/Homepage`
container: `/app/public/images` host:`/portainer/Files/AppData/Config/Homepage/icons`
container: `/var/run/docker.sock` host:`/var/run/docker.sock`
You can find more settings for Homepage [here](Homepage)
</details>
<details>
<summary><h2>Setting up <a href="https://github.com/go-shiori/shiori" target="_blank">Shiori</a></h2></summary>
Find the Homer template in the App Templates list, click it and `Deploy the container`.
Default username and password:
```
username: shiori
password: gopher
```
</details>
<details>
<summary><h2>Setting up <a href="https://github.com/pi-hosted/pi-hosted/blob/master/docs/rpi_docker_monitor.md" target="_blank">RPi Docker Monitor</a></h2></summary>
RPi Docker Monitor is one of the more involved installs, I would suggest checking out the link above and following all the steps as this will vary depending on your install. Below are the instructions I need.
#### 1. Enable c-groups
First we need to enable c-groups by editing 1cmdline.txt`:
```
sudo nano /boot/cmdline.txt
```
Add this to the beginning of the line:
```
systemd.unified_cgroup_hierarchy=0 cgroup_enable=memory cgroup_memory=1
```
Reboot:
```
sudo reboot
```
Once you are logged back in confirm that c-groups are enabled by running
```
cat /proc/cgroups
```
and you should see something like this
```
#subsys_name hierarchy num_cgroups enabled
cpuset 9 15 1
cpu 7 69 1
cpuacct 7 69 1
blkio 8 69 1
memory 11 158 1
devices 3 69 1
freezer 5 16 1
net_cls 2 15 1
perf_event 6 15 1
net_prio 2 15 1
pids 4 76 1
rdma 10 1 1
```
#### 2. Folder Setup Script
Run the below:
```
wget -qO- https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/tools/rpi_docker_monitor.sh | bash
```
You should see an output like this:
```
Checking if you are online...Online. Continuing.
Creating directories...
Downloading Prometheus config files if they don't exist
--2022-12-10 10:15:17-- https://raw.githubusercontent.com/oijkn/Docker-Raspberry-PI-Monitoring/main/prometheus/prometheus.yml
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.109.133, 185.199.110.133, 185.199.111.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.109.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 163 [text/plain]
Saving to: ‘/portainer/Files/AppData/Config/prometheus/config/prometheus.yml’
/portainer/Files/AppData/Config/prometheus/config/prometheu 100%[========================================================================================================================================>] 163 --.-KB/s in 0s
2022-12-10 10:15:17 (3.77 MB/s) - ‘/portainer/Files/AppData/Config/prometheus/config/prometheus.yml’ saved [163/163]
Setting permissions...
Done You are ready to goto next step in the install document
```
#### 3. Install the app template
Go to the Docker apps templates and find `Raspberry Pi Docker Monitor`, you don't have to change anything here but you can update the data retention period from 15 days if you wish before deploying the stack.
#### 4. Setup Grafana
Go to your Pi's IP followed by `:3000` in the browser to set up your account (e.g. `192.168.1.22:3000`) and enter the default log in (Username: `admin` Password: `admin`)
Navigate to `Cog > Configuration > Data Sources > Prometheus`
Under `HTTP` enter the `URL`:
```
http://monitoring-prometheus:9090/
```
Navigate to `Dashboards > Import` and paste everything from the below page into the `Import via panel json` panel:
https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/configs/rpi_dashboard/arm_rpi_dashboard.json
If the container crashes and will not load just run the below and reload the page:
```
wget -qO- https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/tools/rpi_docker_monitor.sh | bash
```
#### Resolving issues
If there are issues loading RPi Monitor try running the following script:
```
wget -qO- https://gitea.cjgameslive.com/CJ/Pi-Hosted/raw/branch/main/Tools/rpi_docker_monitor.sh | bash
```
</details>
<details>
<summary><h2>Setting up <a href="https://nextcloud.com/" target="_blank">NextCloudPi</a></h2></summary>
Find the NextcloudPi template in the App Templates list, click it and `Deploy the container`.
Go to `https://` followed by your Pi's IP followed by `:8443` in the browser to set up your account (e.g. `https://192.168.1.22:8443`)
:warning: Take note of your username (`ncp`) and password before clicking `Activate` or you will have to remove everything and redeploy the container :warning:
Once NextCloud has finished activating go to `https://` followed by your Pi's IP followed by `:4444` in the browser to set up your account (e.g. `https://192.168.1.22:4444`). For the page to load you will have to ignore the security warning and enter your username and the top admin user password you coppied.
Run the configuration wizard and go to the web pannel when prompted, navigate to `nc-trusted-domains` and add your Raspberry Pi's IP address as a trusted domain (along with any other domains you intend to access NextCloud with). Go through the other settings when you have time and update as necessary, especially the `nc-admin` tab where you can set a new password.
<details>
<summary><h4>Trusted domains not working &#10067</h4></summary>
You can manually add trusted domains by editing the `config.php`:
`sudo nano /portainer/Files/AppData/Config/ncdata/nextcloud/config/config.php`
Just look for the `trusted_domains` array.
</details>
Go to `https://` followed by your Pi's IP followed by `:8443` in the browser to set up your account (e.g. `https://192.168.1.22:8443`) and enter your username and the bottom password you coppied and you should be in.
Click on your profile image and apps to add any apps, including the ability to edit files within next cloud or make calls through the platform.
Click on your profile and settings to find server settings, change your password, update your profile information.
If the container crashes or fails to load just run the below and restart the container:
```
wget -qO- https://gitea.cjgameslive.com/CJ/Pi-Hosted/raw/branch/main/Tools/reset_premissions_nextcloud.sh | bash
```
</details>
<details>
<summary><h2>Setting up <a href="https://github.com/pi-hosted/pi-hosted/blob/master/docs/nginx_proxy_manager.md" target="_blank">Nginx Proxy Manager</a></h2></summary>
Nginx Proxy Manager is one of the more involved installs, I would suggest checking out the link above and following all the steps. Below are the instructions I need.
:warning: Remember to expose ports 80 and 443 on your router if you want external network access. Please ensure you set up sufficent network security before opening any ports on your network, and check that the required ports are not blocked by your ISP.
#### 1. Folder Setup Script
Run the following script:
```
wget -qO- https://git.io/JPXF5 | sudo bash
```
Your output should look something like this:
```
# wget -qO- https://git.io/JPXF5 | sudo bash
Creating directories...
Creating a blank nginx-proxy-manager config files
Setup complete. You can now install the stack using the App Template.
```
Alternalively run:
```
wget qO- https://gitea.cjgameslive.com/CJ/Pi-Hosted/raw/branch/main/Tools/nginx-proxy-manager.sh | sudo bash
```
#### 2. Install the app template
Find the Nginx Proxy Manager v2 with Mysql template in the App Templates list, click it, set the Time Zone (TZ), Database password, MYSQL password, and `Deploy the container`.
Go to the `nginx-proxy-manager` logs in Portainer and ensure everything is set up.
#### 3. Log In
Go to your Pi's IP followed by `:81` in the browser to set up your account (e.g. `192.168.1.22:81`) and enter the default log in (Username: `admin@example.com` Password: `changeme`). You will be prompted to set up your admin account after your first log in.
<details>
<summary><h4>Gateway Error when trying to log in &#10067</h4></summary>
When I first tried this I could not log in to the admin dashboard, it was pretty easy to solve.
1. Go back to Portainer and stio the `nginx-proxy-manager` container.
2. Go to the `nginx-proxy-manager-db-1` container and enter the `Console`, click `Connect`
3. Enter `mysql -u root -p npm` and enter the password you set during installation.
4. Enter `SHOW DATABASES;` and look for `npm`
5. Enter `drop database npm;`
6. Enter `SHOW DATABASES;` and make sure `npm` is gone
7. Run `create database npm;`
8. Reboot your Raspberry Pi and try logging in again after a few minutes.
</details>
#### 4. Set up your proxies
The fist proxie I would set up is your Pi's IP address to direct you to your Homer Dashboard.
Enter your Pi's IP in the `Domain Names` filed, leave the Scheme as `http`, enter your Pi's IP again in the `Forward Hostname / IP` field, and enter your Homer port from Portainer (`8902`) in the `Forward Port` field.
When setting up other domains the `Forward Hostname / IP` will always be your Pi's IP if you are trying to expose one of your Portainer containers, and your `Forward Port` can be found in Portainer. Some containers, such as NextCloud, may require the scheme to be `https`.
When adding external access make sure to enable `Block Common Exploits`, I would also suggest going to the SSL tab and selecting `Request a new SSL Certificate`.
</details>
<details>
<summary><h2>Setting up external access with external URL and <a href="https://www.cloudflare.com/dns/" target="_blank">Cloudflare</a> </h2></summary>
Presuming you have already set up [Nginx Proxy Manager](#setting-up-nginx-proxy-manager) we'll quickly go over exposing your new containers to the world so you can access them from outside of your network.
Set up a URL with your favorite domain registrar.
Go to [CloudFlare](https://www.cloudflare.com/dns/) and set up an account, when your in the dashboard find `Add site` and enter your new URL, select the tier you want (there is a free tier!) and continue.
You will want to create an `A` record, set the name as your new domain, and content to your external network IP (you can Google `What is my IP?` or just head over to https://whatismyipaddress.com/). If you want to set up subdomains set up a `CNAME` record with the `Name` as the subdomain you want and content as your new domain so you will have something similar to below for `blog.coolsite.com` and `www.coolsite.com`:
| Type | Name | Content |
| ------ |:------------:| ------------:|
| A | coolsite.com | [externalIP] |
| CNAME | www | coolsite.com |
| CNAME | blog | coolsite.com |
Click continue, at the bottom of the next page you will see `Add Cloudflare's nameservers`, take a note of these and we'll head back over to your domain registrar.
In the client area of your registrar set custom nameservers to the two nameservers from Cloudflare. (*Registrars can take 24 hours to process nameserver updates. You should receive an email when your site is active on Cloudflare.*)
Go back to Cloudflare and click `Done, check nameservers` and you should be good to go. Give it some time for changes to propogate and try your new domain, if you have tried it beofre and it still fails trying clearing your cache or visiting it in a private session.
If you are using a home network with a dynamic IP address you will want to set your system up to automatically update your IP on Cloudflare. :warning: This does not work for `.tk` or other free domains, you will need to manually update Cloudflare.
1. On the `Overview` page you should see an API section near the bottom, click `Get your API token`
2. On the next page click `Create Token`
3. Find Edit zone DNS and click `Use template`
4. Under Zone Resources select your domain or change `Specific zone` to `All zones`, click `Continue to summary`
5. Click `Create Token`
6. Copy token.
7. Head over to Portainer and look for `Cloudflare DDNS`
8. Paste your API token in `CF_API_Token`
9. Enter your domain (in the example above it would be `coolsite.com`)
10. Deploy the container
Go to the Nginx Proxy Manager dashboard and set up your domain to the container you wish (in our example `coolsite.com` would be to one container, and `blog.coolsite.com` would be to another. (`www.coolsite.com` should be set up as another proxy to go to the same place as `coolsite.com`)
</details>
<details>
<summary><h2>Setting Discord alerts with <a href="https://github.com/louislam/uptime-kuma" target="_blank">Uptime Kuma</a></h2></summary>
When setting up notifications from Uptime Kuma to Discord you can use embed formatting in the prefix custom message:
| Type | embed format | Output |
| --------------------- |:-------------------:| -------------:|
| Menion user name | <@Discord_User_ID> | @Discord_user |
| Mention user nickname | <@!Discord_User_ID> | @Discord |
| Mention channel | <#Channel_ID> | #How_to |
| Mention role | <@&Role_ID> | @Admins |
| Custom emoji | <:Name:ID> | 🔥 |
</details>
<details>
## <summary><h2>Make <a href="https://github.com/docker-library/docs/tree/master/wordpress" target="_blank">Wordpress</a> accessible externally with <a href="https://www.cloudflare.com/dns/" target="_blank">Cloudflare</a> and <a href="https://github.com/pi-hosted/pi-hosted/blob/master/docs/nginx_proxy_manager.md" target="_blank">Nginx Proxy Manager</a></h2></summary>
#### 1. Setting your URL on Wordpress
On Wordpress set your URL on the admin dashboard under `Settings` > `General`:
![WordPress set URL](https://cdn4.wpbeginner.com/wp-content/uploads/2019/10/wordpress-address-site-address.png)
#### 2. Adding a redirect and SSL certificate to your Wordpress on Nginx Proxy Manager
Add your domain with and without the *WWW* prefix to your Domain Names, set the IP address to your Pi hosting Portainer and port to Wordpress (`5080` by default), and select `Block Common Exploits`:
![WordPress New Proxy Host](https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/docs/images/WordPress_New_Proxy_Host.PNG)
Navigate to the `SSL` tab, agree to the terms of service and save:
![WordPress Adding SSL Certificate](https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/docs/images/WordPress_Adding_SSL_Certificate.PNG)
It may take some time but your SSL tab should look like the below once all is done, I have turned on `Force SSL`, `HTTP/2 Support`, and `HSTS Enabled`:
![WordPress Enable SSL Certificate](https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/docs/images/WordPress_Enable_SSL_Certificate.PNG)
#### 3. Extra steps required on Cloudflare</h3>
If you haven't already set up Cloudflare check out the [Setting up external access with external URL and Cloudflare](README.md#setting-up-external-access-with-external-url-and-cloudflare-) section.
On Cloudflare, under `SSL/TLS` > `Overview` ensure `Full` or `Full (Strict)` is selected, before setting this my Wordpress site would not load:
![Cloudflare SSL Certificate](https://cdn2.wpbeginner.com/wp-content/uploads/2022/04/cloudflare-dashboard-ssl.png)
</details>
<details>
<summary><h2>Setting up <a href="https://vikunja.io/docs/full-docker-example/" target="_blank">Vikunja</a></h2></summary>
Run the below:
```
wget -qO- https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/tools/install_vikunja.sh | bash
```
Find the Vikunja template in the App Templates list and click it, fill in the required fields and update your `TZ`, and click `Deploy the container`.
In Portainer go to `Stacks` > `vikunja`, and click on `Stop this stack`, then go to `Editor`.
#### Things to configure
Here there are a few things you can edit, I'll let you know which line does what.
I removed `TZ` under the API and added `VIKUNJA_SERVICE_TIMEZONE` which is your servers timezone, and `VIKUNJA_DEFAULTSETTINGS_TIMEZONE` which is your users default timezone.
To add email services (such as password resets, email reminders, service messages, etc.) you'll need to add the below and insert your appropriate details:
```
VIKUNJA_MAILER_HOST: <smtp_host>
VIKUNJA_MAILER_PORT: 587
VIKUNJA_MAILER_USERNAME: <name>@<domain>.com
VIKUNJA_MAILER_PASSWORD: <password>
VIKUNJA_MAILER_FROMEMAIL: <name>@<domain>.com
VIKUNJA_DEFAULTSETTINGS_EMAIL_REMINDERS_ENABLED: true
```
If you have set up all the accounts you want, and want to disable registration for new users add `VIKUNJA_SERVICE_ENABLEREGISTRATION: false`, you can remove this line or stop the stack and change this to `true` if you want to enable registration again.
By default Vikunja sets the first day of the week to Sunday (`0`), you can change this to Monday by setting `VIKUNJA_DEFAULTSETTINGS_WEEK_START: 1`.
Once you've updated all these the `api` section should look like the below:
```
api:
container_name: api
hostname: api
image: vikunja/api:latest
environment:
VIKUNJA_SERVICE_TIMEZONE: ${TZ}
VIKUNJA_DEFAULTSETTINGS_TIMEZONE: ${TZ}
VIKUNJA_DATABASE_HOST: 'mariadb'
VIKUNJA_DATABASE_USER: ${DATABASE_USER}
VIKUNJA_DATABASE_PASSWORD: ${DATABASE_PASSWORD}
VIKUNJA_DATABASE_DATABASE: ${DATABASE_NAME}
VIKUNJA_DATABASE_TYPE: mysql
VIKUNJA_MAILER_ENABLED: true
VIKUNJA_MAILER_HOST: <smtp_host>
VIKUNJA_MAILER_PORT: 587
VIKUNJA_MAILER_USERNAME: <name>@<domain>.com
VIKUNJA_MAILER_PASSWORD: <password>
VIKUNJA_MAILER_FROMEMAIL: <name>@<domain>.com
VIKUNJA_DEFAULTSETTINGS_EMAIL_REMINDERS_ENABLED: true
VIKUNJA_SERVICE_ENABLEREGISTRATION: false
VIKUNJA_DEFAULTSETTINGS_WEEK_START: 1
networks:
- network
restart: unless-stopped
volumes:
- /portainer/Files/AppData/Config/Vikunja/files:/app/vikunja/files
depends_on:
- mariadb
```
Just click `Update the stack` and your changes should be implimented, you can find a full list of environmental vaiables on the <a href="https://vikunja.io/docs/full-docker-example/" target="_blank">Vikunja docs</a> page.
</details>
<details>
<summary><h2>Setting up <a href="https://www.hesk.com/" target="_blank">Hesk</a></h2></summary>
:warning: You will need a working database with a username and password set up, such as the `mariadb` container. :warning:
Go to the [download page](https://www.hesk.com/download.php) of HESK and download HESK free.
Find the nginx template in the App Templates list and click it, then click `Show advanced options` and change the `Host` ports to some free ports for your portainer.
Change the `Name` to something more appropriate, such as `help-desk`.
Add volume mapping from your container:
```
/config
```
Set to `Bind` to:
```
/portainer/Files/AppData/Config/help-desk
```
Then click `Deploy the container`.
Extract the zip we downloaded earlier to `/portainer/Files/AppData/Config/help-desk/www`
Hesk comes with its own tutorial in the downloaded zip, just look for the `readme.html` file and follow their instructions once you've set up your Nginx container. I've put a brief summary and some changes below.
Navigate in your browser to `https://<your-containers_ip:<port>/install` and:
1. Read the HESK License agreement and confirm that you agree with the terms.
2. The script will test your server to see if all required settings are correct and advise solutions to any problems.
3. Enter your database settings, and the setup script will test them.
4. If everything is OK the script will install MySQL tables.
:warning: Before closing the installation script, **DELETE** the "install" directory from your server! :warning:
```
/portainer/Files/AppData/Config/help-desk/www/install
```
Click the `Continue` link in the install script or open the admin folder in your browser by navigating to `https://<your-containers_ip:<port>/admin/`
In the admin console go through each of the tabs and set things up as desired.
Replace `https://<your-containers_ip:<port>/` above with any URL you have set in your proxy manager, your service desk agents can view and respond to tickets by adding `/admin` to the URL and logging in, your end users will just need to visit the base URL.
</details>