diff --git a/.gitattributes b/.gitattributes new file mode 100644 index 0000000..dfe0770 --- /dev/null +++ b/.gitattributes @@ -0,0 +1,2 @@ +# Auto detect text files and perform LF normalization +* text=auto diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..485dee6 --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +.idea diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..e62ec04 --- /dev/null +++ b/LICENSE @@ -0,0 +1,674 @@ +GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. + 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. + + + Copyright (C) + + 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 . + +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: + + Copyright (C) + 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 +. + + 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 +. diff --git a/check/check.sh b/check/check.sh new file mode 100644 index 0000000..b6c5799 --- /dev/null +++ b/check/check.sh @@ -0,0 +1,4 @@ +if ps -ef|grep "nginx"|egrep -v grep >/dev/null +then + echo "1" +fi \ No newline at end of file diff --git a/course.json b/course.json new file mode 100644 index 0000000..ccb8dd6 --- /dev/null +++ b/course.json @@ -0,0 +1,100 @@ +{ + "version": "1", + "title": "Gitcourse Guide", + "author": "Freeman", + "description": "欢迎来到Gitcourse课程制作指南。本指南涵盖了Gircourse的基本重要特性，主要包括：项目构成、课件制作、流程控制。", + "preload": "scripts/auth.js", + "scenarios": [ + { + "title": "Gitcourse基础知识", + "shell":"/bin/bash", + "vscode_port":1234, + "environment": "registry.cn-hangzhou.aliyuncs.com/envs/gitcourse:test", + "description": "一开始，将学习关于gitcourse项目文件目录结构的所有基础内容。", + "steps": [ + { + "program":"scripts/bootstrap.sh", + "title": "项目概览", + "text": "scenario/ep1/1.md", + "oj":"http://online-judge.kfcoding.com/problem/1-2" + }, + { + "title": "发布课程", + "text": "scenario/ep1/2.md" + }, + { + "title": "访问课程", + "text": "scenario/ep1/3.md" + } + ] + }, + { + "title": "Gitcours图文课件制作", + "shell":"/bin/bash", + "environment": "registry.cn-hangzhou.aliyuncs.com/envs/gitcourse:test", + "description": "接下来，将学习如何制作gitcourse图文课件。", + "steps": [ + { + "title": "查看已经修改的容器", + "text": "scenario/ep3/0.md" + }, + { + "title": "Markdown语法及规范", + "text": "scenario/ep3/1.md", + "extraTab":"https://www.w3cschool.cn/markdownyfsm/markdownyfsm-odm6256r.html" + }, + { + "title": "图片插入", + "text": "scenario/ep3/2.md" + } + ] + }, + { + "title": "Gitcours配置文件:基础部分", + "shell":"/bin/bash", + "environment": "registry.cn-hangzhou.aliyuncs.com/envs/gitcourse:v1", + "description": "接下来，将学习如何填写gitcourse的配置文件。首先是基础部分", + "steps": [ + { + "title": "course.json基本字段", + "text": "scenario/ep4/1.md", + "extraTab":"http://gitcourse.kfcoding.com/?compact=true#https://code.kfcoding.com/liuchangfreeman/gitcourse-guide" + }, + { + "title": "scenario基础字段", + "text": "scenario/ep4/2.md", + "extraTab":"http://gitcourse.kfcoding.com/scenarios/0?compact=true#https://code.kfcoding.com/liuchangfreeman/gitcourse-guide" + }, + { + "title": "step基础字段", + "text": "scenario/ep4/3.md", + "extraTab":"http://gitcourse.kfcoding.com/?compact=true#https://code.kfcoding.com/liuchangfreeman/gitcourse-guide" + } + ] + }, + { + "title": "Gitcours配置文件:进阶", + "shell":"/bin/bash", + "environment": "registry.cn-hangzhou.aliyuncs.com/envs/gitcourse:v1", + "description": "接下来，将通过一个例子学习使用gitcourse配置文件的高阶内容。", + "steps": [ + { + "title": "配置容器服务", + "program":"scripts/init.sh", + "text": "scenario/ep5/1.md", + "check":"check/check.sh" + }, + { + "title": "访问容器服务", + "text": "scenario/ep5/2.md", + "extraTab": "[domain]:[:8888]/index.html" + }, + { + "title": "外部网页", + "text": "scenario/ep5/3.md", + "extraTab":"http://www.baidu.com" + } + ] + } + ] +} diff --git a/scenario/ep1/1.md b/scenario/ep1/1.md new file mode 100644 index 0000000..3260454 --- /dev/null +++ b/scenario/ep1/1.md @@ -0,0 +1,24 @@ +## GitCourse项目结构 +一个典型的GitCourse目录结构如下所示： +``` +- 项目根目录 +|- course.json +|- shell + |-- 1.1-check.sh + |-- 1.2-check.sh +|- scenario + |-- 1.1-sample1.md + |-- 1.2-sample2.md +|- script + |-- auth.js + |-- complete.js + |-- preload.js +|- ...其它文件或者目录 +``` +每一个GitCourse项目根目录下都含有一个`course.json`这是核心配置文件 + +其余文件将在配置文件中以**相对路径**的形式进行访问 + +您可以自由地组织其余文件，但是务必确保`course.json`处于根目录下 + +示例中一个合理的文件路径可以为`shell\1.1-check.sh` diff --git a/scenario/ep1/2.md b/scenario/ep1/2.md new file mode 100644 index 0000000..9794a58 --- /dev/null +++ b/scenario/ep1/2.md @@ -0,0 +1,16 @@ + +## 任务 +`git clone https://code.kfcoding.com/liuchangfreeman/gitcourse-guide`使用命令拉取本课程的项目文件。 + +`cd gitcourse-guide`使用命令进入示例目录。 + +这是一个已经初始化完毕的示例gitcouse项目，下面我们将学习如何将其发布到代码托管平台上。 + +` git remote rm origin `使用命令删除已存在的远程仓库地址。 + +` git remote add origin git@github.com:gitcourse-sample/gitcourse-guide.git `命令使用将远程仓库地址设置为https://github.com/gitcourse-sample/gitcourse-guide + +` git push -u -f origin master `使用命令将代码上传到github仓库中。 + +## 专家提示 +免密码登录github需要将系统的ssh-key绑定到账号中，在本示例中这一步骤已预完成，具体教程请参考 [如何绑定ssh-key到github账号](https://www.cnblogs.com/wx1993/p/6646973.html)。 \ No newline at end of file diff --git a/scenario/ep1/3.md b/scenario/ep1/3.md new file mode 100644 index 0000000..6350444 --- /dev/null +++ b/scenario/ep1/3.md @@ -0,0 +1,10 @@ +## 观察 +在上一步中您已将代码发布到了https://github.com/gitcourse-sample/gitcourse-guide + +您可以通过此链接访问刚刚发布的gitcourse: + +http://gitcourse.kfcoding.com/#https://github.com/gitcourse-sample/gitcourse-guide + +我们支持在querystring中添加参数开启gitcourse的编辑模式，您可以通过此链接进行容器镜像的编辑: + +http://gitcourse.kfcoding.com/?edit=true#https://github.com/gitcourse-sample/gitcourse-guide \ No newline at end of file diff --git a/scenario/ep2/1.md b/scenario/ep2/1.md new file mode 100644 index 0000000..d248860 --- /dev/null +++ b/scenario/ep2/1.md @@ -0,0 +1,8 @@ +# GitCourse容器镜像制作 +现在，您已进入gitcourse的容器镜像制作模式 +右侧终端连接到了一个已经启动的**Docker容器**，在**12小时**内您可以对该容器进行修改，并在任意时刻提交该容器并持久化为可供多人使用的**Docker镜像** + +在开始容器镜像制作之前，您需要首先进行以下准备工作: +1. 向管理员获取镜像仓库服务器地址(目前支持registry.cn-hangzhou.aliyuncs.com) +2. 获取镜像仓库的账号和密码 +3. 学习基于命令行的Linux系统基本操作 \ No newline at end of file diff --git a/scenario/ep2/2.md b/scenario/ep2/2.md new file mode 100644 index 0000000..41c7f14 --- /dev/null +++ b/scenario/ep2/2.md @@ -0,0 +1,13 @@ +# 修改容器内容 + +现在您已获取到一个基础容器镜像，您可以在此之上对其进行修改 + +学员将使用制作完成的镜像进行学习，例如执行shell命令或者在提供的web网页上进行操作 + +## 简单的例子 +`date +镜像修改于%Y年%m月%d日%H:%M -d "+8 hour" >>temp` +使用此命令在根目录下创建一个文件，您将保存当前时间到容器中 + +`cat temp` +使用此命令查看您创建的文件内容，下一步将保存此容器为镜像 +当您使用新创建的镜像制作新课程时，将可以直接查看到之前创建的内容 \ No newline at end of file diff --git a/scenario/ep2/3.md b/scenario/ep2/3.md new file mode 100644 index 0000000..8af739c --- /dev/null +++ b/scenario/ep2/3.md @@ -0,0 +1,12 @@ +# 保存容器为镜像 +在这一步，您将可以把上一步修改的容器保存为镜像 + + +1. 镜像仓库服务器请填写*registry.cn-hangzhou.aliyuncs.com* +2. 镜像仓库账号和密码请询问系统管理员 +3. 新镜像的名称请填写为**gitcourse:test** +4. 点击**提交**按钮，数十秒后将会提示成功创建镜像 + +创建完成后，您将会得到容器镜像地址，请保存，这个地址将在以后的场景中用到 + +![](/scenario/images/1.png) \ No newline at end of file diff --git a/scenario/ep3/0.md b/scenario/ep3/0.md new file mode 100644 index 0000000..91b7a8e --- /dev/null +++ b/scenario/ep3/0.md @@ -0,0 +1,19 @@ +# 预览上一步的修改 +本场景的定义如下，使用了上一场景修改的镜像**registry.cn-hangzhou.aliyuncs.com/envs/gitcourse:test** +``` +{ + "title": "Gitcours图文课件制作", + "shell":"/bin/bash", + "environment": "registry.cn-hangzhou.aliyuncs.com/envs/gitcourse:test", + "description": "接下来，将学习如何制作gitcourse图文课件。", + "steps": [ + { + "title": "查看已经修改的容器", + "text": "scenario/ep3/0.md" + }, + ...(略)... + ] +} +``` +您可以通过此命令观察到这是由刚才修改的容器保存的镜像启动而来: +`cat temp` \ No newline at end of file diff --git a/scenario/ep3/1.md b/scenario/ep3/1.md new file mode 100644 index 0000000..266e77e --- /dev/null +++ b/scenario/ep3/1.md @@ -0,0 +1,184 @@ +# Gitcourse课件制作规范 + +**适用于团队的统一 MarkDown 书写规范** + +由于 MarkDown 语法在细节的书写方式很多，为了让不同个体的文档传产出结构一致，提炼出此规范。 +该规范遵循 [MarkDown 官方语法] 以及 [GitHub MakDown 语法]，旨在统一书写格式和代码风格，将多种写法统一。 + +## 1.1全局规范 + +* MarkDown 文件均使用`.md`作为后缀 (**小写字母**) +* 普通文本换行，使用行末尾`2空格`触发 + +## 格式规范 + +### 标题结构格式 + +1. 标题与紧贴的`上下正文`使用`1整行换行`隔开 +2. `#`号和文字之间`1个空格`连接 +3. 标题层级如下，最多6级 + +``` +# 顶级标题 等价于 title 和

+## 次级标题 等价于

+### 3级标题 等价于

+#### 4级标题 等价于

+##### 5级标题 等价于

+###### 6级标题 等价于
+####### 注：此行错误，标题层级最多6级 没有标签 +``` + +### 加强和强调规范 + +以下两种写法都是正确的，请统一为**第一种**，即一律使用 `**加强` `*强调` + +``` +*emphasize* **strong** 相当于标签和标签 +_emphasize_ __strong__ +``` + +使用`~~`给文字添加删除线 +``` +~~strikethrough~~ +``` + +### 代码块规范 + +* 行内代码使用`1对波浪号` 如： \`hello world!\` +* 块级代码使用`3个波浪号` 或 `整体4空格缩进`，且上下均用`整行隔开`，如下: (**占用7行**) + +``` + +``` + + + +### 列表写法 + +* 列号`1.` 或者`* `后其后内容`空格`隔开 +* 列表块前后`整行隔开` 如下： + +``` +1. Windows +2. Mac +3. iOS + * iPhone + * iPad +4. Android +``` + +**实际预览：** + +1. Windows +2. Mac +3. iOS + * iPhone + * iPad +4. Android + +``` +* Windows +* Mac +* iOS +* Android + 1. v3.2 + 2. v4.1 +``` + +**实际预览：** + +* Windows +* Mac +* iOS +* Android + 1. v3.2 + 2. v4.1 + +### 其他标签规范 + +链接和Email +Inline: + +``` +An [example](http://url.com/ "Title") +``` + +引用样式标签 (titles are optional): + + An [example][id]. Then, anywhere + else in the doc, define the link: + + [id]: http://example.com/ "Title" + +Email: + +``` +An email link. +``` + +插图 +Inline (titles are optional): + +``` +![alt text](/path/img.jpg "Title") +``` + +引用式插图: + + ![alt text][id] + + [id]: /url/to/img.jpg "Title" + + +引用块及嵌套 + +> Email-style angle brackets +> are used for blockquotes. + +> > And, they can be nested. + +> #### Headers in blockquotes +> +> * You can quote a list. +> * Etc. + +内联代码 + +`` 段落中的用法 + +也可以 `` `代码中包含波浪号` ``. +代码块 + +Indent every line of a code block by at least 4 spaces or 1 tab. +代码的每行都最少用4个空格或者一个制表符(tab) + +我是普通文本块 + + 我是一个预格式化的 + 代码块. + +水平分割线 +三个`连字符-`: + +--- + +### 表格规范 + +一个简单的表格看起来如下： + +第一个头部 | 第二个头部 | 第三个头部 +--------|---------|------- +内容格子 | 内容格子 | 内容格子 +内容格子 | 内容格子 | 内容格子 + +每列的对齐可以通过在分割线上添加冒号来实现： + +第一个头部 | 第二个头部 | 第三个头部 +:--------|:---------:|-------: +左对齐 | 居中 | 右对齐 +左对齐 | 居中 | 右对齐 +--- \ No newline at end of file diff --git a/scenario/ep3/2.md b/scenario/ep3/2.md new file mode 100644 index 0000000..b7ae266 --- /dev/null +++ b/scenario/ep3/2.md @@ -0,0 +1,20 @@ +# Gitcourse课件图片插入 +您可以直接将图片内置在gitcourse项目中 +您也可以使用对象存储上传图片，并在上传完图片后获取到超链接并以MarkDown的格式引入到课件中 +`![标题](链接)` +``` +- 项目根目录 +|- course.json +|- scenario + |-- ep3 + |-- 0.md + |-- 1.md + |- images + |-- 1.png + |-- 2.png +|- ...其它文件或者目录 +``` + +在本示例中，访问文件目录中的*2.png*的正确做法是: +`![](../images/2.png)` +![](../images/2.png) \ No newline at end of file diff --git a/scenario/ep4/1.md b/scenario/ep4/1.md new file mode 100644 index 0000000..56b1658 --- /dev/null +++ b/scenario/ep4/1.md @@ -0,0 +1,23 @@ +# course.json基础字段定义 + +| 字段 | 类型 | 默认值 | 说明 | +| ---- | ---- | ---- | ---- | +| version | string | "1" | 所使用的GitCourse解释器版本，目前只支持版本"1" | +| title | string | "" | 课程标题 | +| author | string | "" | 作者 | +| description | string | "" | 课程简介 | +| scenarios | array | [] | 课程的场景，将会按顺序逐个进行解析 | +| preload | string | "" | 预加载的js脚本，用于进行Docker服务器认证 | + +在右侧的GitCourse示例中，基础字段的填写方法为: +``` +{ + "version": "1", + "title": "Gitcourse Guide", + "author": "Freeman", + "description": "欢迎来到Gitcourse课程制作指南。本指南涵盖了Gircourse的基本重要特性，主要包括：项目构成、实训环境、课件制作、流程控制。", + "preload": "scripts/auth.js", + "scenarios": [...(略)...] +} +``` +其中scenarios是一个列表，定义了本课程所具有的场景，将在下一节进行详细说明 \ No newline at end of file diff --git a/scenario/ep4/2.md b/scenario/ep4/2.md new file mode 100644 index 0000000..53e0fa9 --- /dev/null +++ b/scenario/ep4/2.md @@ -0,0 +1,23 @@ +# scenario字段定义 + +| 字段 | 类型 | 默认值 | 说明 | +| ---- | ---- | ---- | ---- | +| title | string | "" | 场景打开时显示的标题 | +| description | string | "" | 场景的描述 | +| shell | string | "/bin/sh" | 指定终端使用*/bin/sh*还是*/bin/bash* | +| docker_endpoint | string | "" | 所使用的docker容器服务的提供方，不指定则使用当前gitcourse服务方所提供的全局地址 | +| environment | string | "null" | 本场景所使用的docker容器镜像 | +| steps | array | [] | 场景的步骤，将会按顺序逐个进行解析，以供学员分步骤完成本场景的学习 | + +在本章的GitCourse示例中，其基础字段的填写方法为: + +``` +{ + "title": "Gitcours配置文件详解:基础部分", + "shell":"/bin/bash", + "environment": "registry.cn-hangzhou.aliyuncs.com/envs/gitcourse:test", + "description": "接下来，将学习如何填写gitcourse的配置文件。首先是基础部分", + "steps": [...(略)...] +} +``` +其中steps是一个列表，定义了本场景所具有的步骤，将在下一节进行详细说明 \ No newline at end of file diff --git a/scenario/ep4/3.md b/scenario/ep4/3.md new file mode 100644 index 0000000..8213ab3 --- /dev/null +++ b/scenario/ep4/3.md @@ -0,0 +1,19 @@ +# step字段定义 + +| 字段 | 类型 | 默认值 | 说明 | +| ---- | ---- | ---- | ---- | +| title | string | "" | 此步骤的标题 | +| text | string | "null" | markdown文件的相对路径，用于在此步骤中展示 | +| program | string | "null" | shell脚本的相对路径，步骤初始化时在docker容器中执行 | +| check | string | "null" | shell脚本的相对路径，用户点击完成步骤时在docker容器中执行，用于检查完成情况。当脚本检查通过后应当输出任意字符，否则本步骤不会进入下一步(当脚本执行出错时，也会进入下一步)。 | +| extraTab | string | "null" | 实训环境除了可以使用默认的docker容器命令行之外，还可以在一个iframe中访问web网页，该服务既可以由容器提供也可以是外部网页。 | + +在本步骤的GitCourse示例中，其基础字段的填写方法为: + +``` +{ + "title": "step基础字段", + "text": "scenario/ep4/3.md", + "extraTab":"http://gitcourse.kfcoding.com/?compact=true#https://code.kfcoding.com/liuchangfreeman/gitcourse-guide" +} +``` \ No newline at end of file diff --git a/scenario/ep5/1.md b/scenario/ep5/1.md new file mode 100644 index 0000000..3dd834d --- /dev/null +++ b/scenario/ep5/1.md @@ -0,0 +1,52 @@ +# 容器内部服务 + +这是本步骤的定义: +``` +{ + "title": "配置容器服务", + "program":"scripts/init.sh", + "text": "scenario/ep5/1.md", + "check":"check/check.sh" +} +``` +本步骤中使用到了**program**与**check**字段，这两个字段分别引用了一个在本步骤开始前执行，以及结束时用于检查当前步骤是否完成的shell脚本，下面将以此为实例，介绍这两个字段的用途。 +## 初始化脚本 +`date +gitcourse服务器端脚本执行于%Y年%m月%d日%H:%M -d "+8 hour" >>temp` +这是*scripts/init.sh*的具体内容，它的作用是在本步骤开始前，将当前的时间打印到*/temp*文件中，我们将在下一步中通过容器内部服务访问到此文件的内容 +## 准备工作 +这是/etc/nginx/nginx.conf的内容 +``` +events { + worker_connections 1024; +} +http { + server { + default_type 'text/html'; + charset utf-8; + listen 8888; + location / { + root /; + index index.html; + } + } +} + +``` +此实验已经预装了**nginx**服务，并在配置文件中指定了**8888**端口作为对外服务的入口 +并且在根目录下放置了一个*index.html*文件，当本步骤开启后，您将可以通过nginx服务访问到*index.html*以及由*init.sh*创建的*temp*文件 +但是在此之前，请完成**nginx服务的开启**： +`service nginx start` +否则在下一步将无法访问由容器提供的服务 +## 检查脚本 +为了确保学员完成必要的前置任务，您可以通过**check**字段指定一个检查脚本 +这是当前步骤的*check/check.sh*的内容: +``` +if ps -ef|grep "nginx"|egrep -v grep >/dev/null +then + echo "1" +fi +``` +当且仅当容器中已运行nginx服务时，才会允许进入下一步。当您在编写检查脚本时，需要注意以下几点: +1. 脚本默认通过*/bin/bash*来执行 +2. 有任何输出或者报错，均会允许进入下一步 +3. 没有任何输出才不会进入下一步 diff --git a/scenario/ep5/2.md b/scenario/ep5/2.md new file mode 100644 index 0000000..4453257 --- /dev/null +++ b/scenario/ep5/2.md @@ -0,0 +1,20 @@ +# 访问容器服务 +在上一步中您启动了容器内部的nginx服务，但是并不能直接对其进行访问 +受到复杂的网络环境限制，对容器内部服务的访问依赖于代理转发 +但是您不必关注此步骤是如何实现的，gitcourse对于特定端口的http服务有较为完美的转发方案 +## 查看nginx服务 +在右侧的iframe中，您看到的是上一步中的*/index.html*的内容 +在其中有一个超链接，指向了上一步一开始创建的*/temp*文件，点开它，您可以看到以下内容: +`gitcourse服务器端脚本执行于XX年XX月XX日XX:XX ` +## 使用extraTab字段访问容器内部服务 +这是本步骤的定义: +``` +{ + "title": "访问容器服务", + "text": "scenario/ep5/2.md", + "extraTab": "[domain]:[:8888]/index.html" +} +``` +通过**extraTab**访问容器内部服务，需要严格以以下格式进行填写: +`[domain]:[:内部服务监听的端口号]访问路径` +在本示例中，nginx监听了容器的8888端口，同时需要服务的根目录下的/index.html文件 diff --git a/scenario/ep5/3.md b/scenario/ep5/3.md new file mode 100644 index 0000000..382c9a7 --- /dev/null +++ b/scenario/ep5/3.md @@ -0,0 +1,4 @@ +# extraTab的其他用法 +extraTab不仅仅可以用来访问容器内部服务，还可以加载外部网页 +但是需要该网页允许本身被iframe加载 +本示例中加载的是:http://www.baidu.com \ No newline at end of file diff --git a/scripts/auth.js b/scripts/auth.js new file mode 100644 index 0000000..9636547 --- /dev/null +++ b/scripts/auth.js @@ -0,0 +1,25 @@ +function getCookie(name) { + var value = `; ${document.cookie}`; + var pairs = value.split("; " + name + "="); + if (pairs.length == 2) { + return pairs.pop().split(";").shift() + }; +} + +if (document.location.host == 'gitcourse.test.kfcoding.com') { + var token=getCookie('token'); + fetch('http://api.kfcoding.com/api/basic/users/current', { + headers: { + 'Content-Type': 'application/json', + 'Authorization': token + }, + method: 'GET', + }).then(response => response.json()).then(data => { + if (data.status !== 200) { + window.location.href = "http://kfcoding.com/user/login?redirect=" + window.location.href; + } + else{ + window.env=[`token=${token}`] + } + }); +} \ No newline at end of file diff --git a/scripts/bootstrap.sh b/scripts/bootstrap.sh new file mode 100644 index 0000000..380e6d1 --- /dev/null +++ b/scripts/bootstrap.sh @@ -0,0 +1 @@ +/code-server --auth none --host 0.0.0.0 --port 1234 \ No newline at end of file diff --git a/scripts/complete.js b/scripts/complete.js new file mode 100644 index 0000000..2882eb2 --- /dev/null +++ b/scripts/complete.js @@ -0,0 +1,27 @@ +function getCookie(name) { + var value = "; " + document.cookie; + var parts = value.split("; " + name + "="); + if (parts.length == 2) return parts.pop().split(";").shift(); +} +try { + fetch('http://api.kfcoding.com/api/practice/trains/competition', { + headers: { + 'Content-Type': 'application/json', + Authorization: getCookie('token') + }, + method: 'POST', + body: JSON.stringify({repo: 'https://github.com/openx-lab/go-study-guide.git'}) + }).then(resp => resp.json()) + .then(data => { + return fetch('http://api.kfcoding.com/api/practice/trains/competition/end', { + headers: { + 'Content-Type': 'application/json', + Authorization: getCookie('token') + }, + method: 'PUT', + body: JSON.stringify({id: data.data.id}) + }) + }) +} catch (e) { + console.log(e) +} diff --git a/scripts/init.sh b/scripts/init.sh new file mode 100644 index 0000000..1d73633 --- /dev/null +++ b/scripts/init.sh @@ -0,0 +1 @@ +date +gitcourse服务器端脚本执行于%Y年%m月%d日%H:%M -d "+8 hour" >>temp diff --git a/scripts/preload b/scripts/preload new file mode 100644 index 0000000..1620f35 --- /dev/null +++ b/scripts/preload @@ -0,0 +1,18 @@ +function getCookie(name) { + var value = "; " + document.cookie; + var parts = value.split("; " + name + "="); + if (parts.length == 2) return parts.pop().split(";").shift(); +} + +fetch('http://api.kfcoding.com/api/practice/trains/competition/begin', { + headers: { + 'Content-Type': 'application/json', + Authorization: getCookie('token') + }, + method: 'POST', + body: JSON.stringify({repo: 'https://github.com/openx-lab/go-study-guide.git'}) +}).then(resp => resp.json()) + .then(data => { + if (data.data) + localStorage.setItem('comp_id', data.data.id) + });