├── .gitignore ├── LICENSE ├── README.md ├── caddy-jail.sh └── includes ├── Caddyfile ├── Caddyfile.example └── caddy /.gitignore: -------------------------------------------------------------------------------- 1 | caddy-config 2 | 3 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # freenas-iocage-caddy 2 | This script will create an iocage jail on TrueNAS CORE 13.0 with the latest Caddy 2.x release. 3 | 4 | ## Status 5 | This script will work with FTrueNAS CORE 13.0. It is unlikely to work reliably with earlier releases of FreeNAS. 6 | 7 | ## Usage 8 | Many users install a variety of web applications in jails on their FreeNAS servers, and often those applications run on non-standard ports like 6789, 8181, 7878, etc. These port numbers are far from intuitive, and the applications often either don't implement HTTPS at all, or make it difficult to configure. A common recommendation to address these issues is to install a separate web server to act as a reverse proxy (allowing you to browse to simpler URLs like http://yourserver/radarr), and also to handle the TLS termination. Although popular web servers like Apache and Nginx can act as reverse proxies, configuration is complex, and neither of them handle the TLS certificates and configuration by default. This guide will cover installing Caddy in its own jail, configuring it to act as a proxy for your other applications, and optionally obtaining TLS certificates from Let's Encrypt and/or ZeroSSL and using them to encrypt your communications. 9 | 10 | The Caddy installation performed by this script is pretty bare-bones, and can be adapted by the user for a variety of different uses. The primary purposes envisioned by this guide are: 11 | 12 | * Serve static HTML web pages (using PHP will require installing additional packages in the jail) 13 | * Acting as a reverse proxy, as described above 14 | * Optionally providing TLS termination for your apps 15 | 16 | This author's purpose for the reverse proxy is entirely on his own LAN, not anything that would be exposed to the Internet. If you're wanting to expose a reverse proxy to the Internet as a way of making services on your LAN accessible from the Internet, this installation will do that as well (just forward ports 80 and 443 to this jail). However, it'd be worth investigating whether your router has a similar capability (as both [pfSense](https://www.pfsense.org/) and [OPNsense](https://opnsense.org/) do). If so, implementing the proxy on your router may be the better way to go. 17 | 18 | ### Prerequisites 19 | 20 | Although not required, it's recommended to create a Dataset named `apps` with a sub-dataset named `caddy` on your main storage pool. Many other jail guides also store their configuration and data in subdirectories of `pool/apps/` If this dataset is not present, a directory `/apps/caddy` will be created in `$POOL_PATH`. 21 | 22 | ### Installation 23 | 24 | Download the repository to a convenient directory on your TrueNAS/FreeNAS system by changing to that directory and running `git clone https://github.com/danb35/freenas-iocage-caddy`. Then change into the new freenas-iocage-caddy directory and create a file called caddy-config with your favorite text editor. In its minimal form, it would look like this: 25 | 26 | ``` 27 | JAIL_IP="192.168.1.199" 28 | DEFAULT_GW_IP="192.168.1.1" 29 | POOL_PATH="/mnt/tank" 30 | ``` 31 | 32 | Many of the options are self-explanatory, and all should be adjusted to suit your needs, but only a few are mandatory. The mandatory options are: 33 | 34 | - JAIL_IP is the IP address for your jail. You can optionally add the netmask in CIDR notation (e.g., 192.168.1.199/24). If not specified, the netmask defaults to 24 bits. Values of less than 8 bits or more than 30 bits are invalid. 35 | - DEFAULT_GW_IP is the address for your default gateway 36 | - POOL_PATH is the path for your data pool. 37 | 38 | In addition, there are some other options which have sensible defaults, but can be adjusted if needed. These are: 39 | 40 | - JAIL_NAME: The name of the jail, defaults to "caddy" 41 | - CONFIG_PATH: This is the path to your Caddyfile, defaults to $POOL_PATH/apps/caddy. 42 | - INTERFACE: The network interface to use for the jail. Defaults to `vnet0`. 43 | - VNET: Whether to use the iocage virtual network stack. Defaults to `on`. 44 | - DNS_PLUGIN: This contains the name of the DNS validation plugin you'll use with Caddy to validate domain control. Visit the [Caddy download page](https://caddyserver.com/download) to see the DNS authentication plugins currently available. To build Caddy with your desired plugin, use the last part of the "Package" on that page as DNS_PLUGIN in your `caddy-config` file. E.g., if the package name is `github.com/caddy-dns/cloudflare`, you'd set `DNS_PLUGIN=cloudflare`. From that page, there are also links to the documentation for each plugin, which will describe what credentials are needed. 45 | 46 | $CONFIG_PATH is mounted inside the jail at `/usr/local/www`. The Caddyfile goes there, and that's also where your web pages will go, if you're serving any web content directly from this jail--that would ordinarily go in `/usr/local/www/html` inside the jail, or $CONFIG_PATH/html on your FreeNAS system. 47 | 48 | Also, if you're going to be using TLS with this Caddy installation, your domain needs to resolve to your jail from inside your network. You'll probably need to configure this on your router. If you're unable to do so, you can edit the hosts file on your client computers to achieve this result. 49 | 50 | ### Execution 51 | 52 | Once you've downloaded the script and prepared the configuration file, run this script (`./caddy-jail.sh`). The script will run for several minutes. When it finishes, your jail will be created and Caddy will be installed. 53 | 54 | ### Test 55 | 56 | To test your installation, enter your Caddy jail IP address and port 2020 e.g. `192.168.1.199:2020` in a browser. If the installation was successful, the message *Hello, world!* should be displayed. 57 | 58 | ## The Caddyfile 59 | Caddy looks for its configuration in the Caddyfile. Its syntax is fairly simple, and is fully documented in the [Caddy Docs](https://caddyserver.com/docs/). It's saved outside the jail in `$POOL_PATH/apps/caddy/`, so you can edit it without entering the jail. This script installs a very basic Caddyfile which only prints "Hello, world!"; to actually act as a reverse proxy or web server, you'll need to create your own Caddyfile. I'll discuss a few scenarios with examples of the Caddyfile below. 60 | 61 | For a more extensively-annotated Caddyfile, see `Caddyfile.example` at `/usr/local/www/Caddyfile.example` in your jail. 62 | 63 | ### Prerequisites (TLS Certificate) 64 | Caddy works best when your installation is able to obtain a TLS certificate. With the current release, Caddy will obtain certs from both Let's Encrypt and ZeroSSL if possible, giving you redundancy in the event of an outage of one certificate authority or the other. When you use it this way, Caddy is able to handle all of the TLS-related configuration for you, obtain and renew certificates automatically, etc. In order for this to happen, you must meet the two requirements below: 65 | 66 | First, you must own or control a real Internet domain name. This script obtains a TLS encryption certificate from Let's Encrypt and/or ZeroSSL, who will only issue for public domain names. Thus, domains like cloud.local, mycloud.lan, or nextcloud.home won't work. Domains can be very inexpensive, and in some cases, they can be free. Freenom, for example, provides domains for free if you jump through the right hoops. EasyDNS is a fine domain registrar for paid domains, costing roughly US$15 per year (which varies slightly with the top-level domain). 67 | 68 | Second, one of these two conditions must be met in order for the certificate authority to validate your control over the domain name: 69 | 70 | * You must be able and willing to open ports 80 and 443 from the entire Internet to the jail, and leave them open. 71 | * DNS hosting for the domain name needs to be with a provider that Caddy supports. 72 | 73 | For example, Cloudflare provides DNS hosting at no cost, and it's well-supported by Caddy. Cloudflare also provides Dynamic DNS service, if your desired Dynamic DNS client supports their API. If it doesn't, DNS-O-Matic is a Dynamic DNS provider that will interface with many DNS hosts including Cloudflare, has a much simpler API that's more widely supported, and is also free of charge. 74 | 75 | Due to abuse, Cloudflare has removed the ability to use its API with free domains when using Cloudflare's free plan. For this to work, you'll need to pay either for Cloudflare or for a domain (and the latter is likely less expensive). If you want to use a Freenom domain, you'll need to be able and willing to open ports 80 and 443 to your jail, so you can get your certificate without using DNS validation. 76 | 77 | If you aren't able or willing to obtain a certificate from Let's Encrypt, Caddy can be configured with a self-signed certificate, or with no certificate (and thus no HTTPS) at all. 78 | 79 | ### No TLS 80 | This is the simplest case of a Caddyfile. To serve static HTML pages, the basic case can look like this: 81 | ``` 82 | *:80 { 83 | root * /usr/local/www/html 84 | file_server 85 | } 86 | ``` 87 | This Caddyfile will serve HTML pages out of `/usr/local/www/html` over HTTP. Nice and easy. But suppose you want it to act as a reverse proxy? Almost as easy: 88 | ``` 89 | *:80 { 90 | root * /usr/local/www/html 91 | file_server 92 | reverse_proxy /sonarr* 192.168.1.12:8989 93 | reverse_proxy /radarr* 192.168.1.12:9898 94 | } 95 | ``` 96 | This will still serve static pages out of `/usr/local/www/html` over HTTP (so maybe you want to put a nice landing page there), but any requests for `/sonarr` or `/radarr` will be proxied to those respective ports on the host you specify. 97 | 98 | ### TLS with HTTP validation 99 | This case is nearly as simple. You'd use this if you're going expose this jail to the Internet, with ports 80 and 443 forwarded to the jail. The Caddyfile for the static web server will look like this: 100 | ``` 101 | { 102 | acme_ca https://acme-staging-v02.api.letsencrypt.org/directory 103 | email somebody@your_email.com 104 | } 105 | 106 | sub.domain.com { 107 | root * /usr/local/www/html 108 | file_server 109 | } 110 | ``` 111 | As before, this will serve HTML pages out of `/usr/local/www/html`. But unlike the previous example, this Caddyfile will obtain a certificate from Let's Encrypt, renew it automatically, configure TLS, and redirect HTTP to HTTPS. 112 | 113 | The top block here is optional, but recommended. The first directive tells Caddy to use the Let's Encrypt staging server. Certificates issued by this server won't be trusted by your browser, but you're much less likely to exceed the [rate limits](https://letsencrypt.org/docs/rate-limits/). Once you're sure your system is working properly, you can comment it out (or delete it). The second directive is an email address Let's Encrypt can use to notify you of certificate expiration or other major events. If things are working properly, you'll very rarely get an email from them. 114 | 115 | In the second block, there are two changes: 116 | 117 | * Your FQDN is specified here. As noted above, you need to own this domain, and public DNS records must point it to your server. 118 | * No port number is specified. This allows Caddy to serve this hostname over both HTTP and HTTPS. 119 | 120 | To implement the reverse proxy, add those lines (as shown above) to the second block. 121 | 122 | ### TLS with DNS validation 123 | This gets a little more complicated. DNS validation will let you obtain a certificate without your jail being accessible from the Internet. This will require that your Caddy installation be compiled with an appropriate DNS validation plugin--to see the available options, visit the [Caddy download page](https://caddyserver.com/download), and specify it in the config file when you run the script. The Caddyfile will look something like this: 124 | ``` 125 | { 126 | acme_ca https://acme-staging-v02.api.letsencrypt.org/directory 127 | email somebody@your_email.com 128 | } 129 | 130 | sub.domain.com { 131 | tls { 132 | dns cloudflare long_api_token 133 | } 134 | root * /usr/local/www/html 135 | file_server 136 | } 137 | ``` 138 | Compared to the last example, the only change is the `tls{}` block. In that block, `dns` is a required keyword, `cloudflare` is the name of the plugin being used, and `long_api_token` is a Cloudflare API token with appropriate permissions. The reverse proxy is added as above. 139 | 140 | Authentication credentials vary for each supported DNS host. The Caddy download page links to the individual plugins, which document the required credentials and how to specify them. You'll need to make adjustments for your own situation. 141 | 142 | ### Test 143 | 144 | You can validate your Caddyfile changes with `service caddy configtest`. To commit the changes gracefully and with zero downtime, use `service caddy reload` instead of `service caddy restart`. 145 | 146 | ## Limitations 147 | 148 | Some apps are not amenable to being served over a reverse proxy, or at least with the configuration described above. Two such apps appear to be Duplicati and Urbackup. If your app doesn't work, try doing a web search for "(app name) reverse proxy" to see if (1) it's possible at all, and (2) if any special settings are required. 149 | 150 | ## Support and Discussion 151 | 152 | Questions or issues about this resource can be raised in [this forum thread](https://www.ixsystems.com/community/threads/reverse-proxy-using-caddy-with-optional-automatic-tls.75978/). Be aware that any Caddyfile examples in that thread prior to August 2020 will be incorrect, as Caddy v1 used a significantly different Caddyfile syntax. 153 | 154 | Though we'll try to help on that thread, once Caddy's up and running, the [Caddy forum](https://caddy.community/) is likely to be a better resource for its configuration, particularly with applications whose reverse proxy settings prove to be difficult. Once you have something working, though, please post back in the iXSystems forum. 155 | -------------------------------------------------------------------------------- /caddy-jail.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | # Build an iocage jail under FreeNAS 11.3-12.0 using the current release of Caddy 3 | # git clone https://github.com/danb35/freenas-iocage-caddy 4 | 5 | # Check for root privileges 6 | if ! [ $(id -u) = 0 ]; then 7 | echo "This script must be run with root privileges" 8 | exit 1 9 | fi 10 | 11 | ##### 12 | # 13 | # General configuration 14 | # 15 | ##### 16 | 17 | # Initialize defaults 18 | JAIL_IP="" 19 | JAIL_INTERFACES="" 20 | DEFAULT_GW_IP="" 21 | INTERFACE="vnet0" 22 | VNET="on" 23 | POOL_PATH="" 24 | CONFIG_PATH="" 25 | JAIL_NAME="caddy" 26 | DNS_PLUGIN="" 27 | CONFIG_NAME="caddy-config" 28 | 29 | # Check for caddy-config and set configuration 30 | SCRIPT=$(readlink -f "$0") 31 | SCRIPTPATH=$(dirname "${SCRIPT}") 32 | if ! [ -e "${SCRIPTPATH}"/"${CONFIG_NAME}" ]; then 33 | echo "${SCRIPTPATH}/${CONFIG_NAME} must exist." 34 | exit 1 35 | fi 36 | . "${SCRIPTPATH}"/"${CONFIG_NAME}" 37 | INCLUDES_PATH="${SCRIPTPATH}"/includes 38 | 39 | JAILS_MOUNT=$(zfs get -H -o value mountpoint $(iocage get -p)/iocage) 40 | RELEASE=$(freebsd-version | cut -d - -f -1)"-RELEASE" 41 | # If release is 13.1-RELEASE, change to 13.2-RELEASE 42 | if [ "${RELEASE}" = "13.1-RELEASE" ]; then 43 | RELEASE="13.2-RELEASE" 44 | fi 45 | 46 | # Check that necessary variables were set by nextcloud-config 47 | if [ -z "${JAIL_IP}" ]; then 48 | echo 'Configuration error: JAIL_IP must be set' 49 | exit 1 50 | fi 51 | if [ -z "${JAIL_INTERFACES}" ]; then 52 | echo 'JAIL_INTERFACES not set, defaulting to: vnet0:bridge0' 53 | JAIL_INTERFACES="vnet0:bridge0" 54 | fi 55 | if [ -z "${DEFAULT_GW_IP}" ]; then 56 | echo 'Configuration error: DEFAULT_GW_IP must be set' 57 | exit 1 58 | fi 59 | if [ -z "${POOL_PATH}" ]; then 60 | echo 'Configuration error: POOL_PATH must be set' 61 | exit 1 62 | fi 63 | # If CONFIG_PATH wasn't set in caddy-config, set it 64 | if [ -z "${CONFIG_PATH}" ]; then 65 | CONFIG_PATH="${POOL_PATH}"/apps/caddy 66 | fi 67 | 68 | # Extract IP and netmask, sanity check netmask 69 | IP=$(echo ${JAIL_IP} | cut -f1 -d/) 70 | NETMASK=$(echo ${JAIL_IP} | cut -f2 -d/) 71 | if [ "${NETMASK}" = "${IP}" ] 72 | then 73 | NETMASK="24" 74 | fi 75 | if [ "${NETMASK}" -lt 8 ] || [ "${NETMASK}" -gt 30 ] 76 | then 77 | NETMASK="24" 78 | fi 79 | 80 | ##### 81 | # 82 | # Jail Creation 83 | # 84 | ##### 85 | 86 | # List packages to be auto-installed after jail creation 87 | cat <<__EOF__ >/tmp/pkg.json 88 | { 89 | "pkgs":[ 90 | "nano","bash","go","git" 91 | ] 92 | } 93 | __EOF__ 94 | 95 | # Create the jail and install previously listed packages 96 | if ! iocage create --name "${JAIL_NAME}" -p /tmp/pkg.json -r "${RELEASE}" interfaces="${JAIL_INTERFACES}" ip4_addr="${INTERFACE}|${IP}/${NETMASK}" defaultrouter="${DEFAULT_GW_IP}" boot="on" host_hostname="${JAIL_NAME}" vnet="${VNET}" 97 | then 98 | echo "Failed to create jail" 99 | exit 1 100 | fi 101 | rm /tmp/pkg.json 102 | 103 | ##### 104 | # 105 | # Directory Creation and Mounting 106 | # 107 | ##### 108 | 109 | mkdir -p "${CONFIG_PATH}" 110 | 111 | iocage exec "${JAIL_NAME}" mkdir -p /mnt/includes 112 | iocage exec "${JAIL_NAME}" mkdir -p /usr/local/www 113 | 114 | iocage fstab -a "${JAIL_NAME}" "${CONFIG_PATH}" /usr/local/www nullfs rw 0 0 115 | iocage fstab -a "${JAIL_NAME}" "${INCLUDES_PATH}" /mnt/includes nullfs rw 0 0 116 | 117 | ##### 118 | # 119 | # Additional Dependency installation 120 | # 121 | ##### 122 | 123 | # Build xcaddy, use it to build Caddy 124 | if ! iocage exec "${JAIL_NAME}" "go install github.com/caddyserver/xcaddy/cmd/xcaddy@latest" 125 | then 126 | echo "Failed to install xcaddy, terminating." 127 | exit 1 128 | fi 129 | iocage exec "${JAIL_NAME}" mv /root/go/bin/xcaddy /usr/local/bin/xcaddy 130 | if [ -n "${DNS_PLUGIN}" ]; then 131 | if ! iocage exec "${JAIL_NAME}" xcaddy build --output /usr/local/bin/caddy --with github.com/caddy-dns/"${DNS_PLUGIN}" 132 | then 133 | echo "Failed to build Caddy with ${DNS_PLUGIN} plugin, terminating." 134 | exit 1 135 | fi 136 | else 137 | if ! iocage exec "${JAIL_NAME}" xcaddy build --output /usr/local/bin/caddy 138 | then 139 | echo "Failed to build Caddy without plugin, terminating." 140 | exit 1 141 | fi 142 | fi 143 | 144 | # Copy pre-written config files 145 | iocage exec "${JAIL_NAME}" cp /mnt/includes/caddy /usr/local/etc/rc.d/ 146 | iocage exec "${JAIL_NAME}" cp /mnt/includes/Caddyfile.example /usr/local/www/ 147 | iocage exec "${JAIL_NAME}" cp -n /mnt/includes/Caddyfile /usr/local/www/ 2>/dev/null 148 | 149 | iocage exec "${JAIL_NAME}" sysrc caddy_enable="YES" 150 | iocage exec "${JAIL_NAME}" sysrc caddy_config="/usr/local/www/Caddyfile" 151 | 152 | iocage restart "${JAIL_NAME}" 153 | 154 | # Don't need /mnt/includes any more, so unmount it 155 | iocage fstab -r "${JAIL_NAME}" "${INCLUDES_PATH}" /mnt/includes nullfs rw 0 0 156 | -------------------------------------------------------------------------------- /includes/Caddyfile: -------------------------------------------------------------------------------- 1 | :2020 { 2 | respond "Hello, world!" 3 | } 4 | -------------------------------------------------------------------------------- /includes/Caddyfile.example: -------------------------------------------------------------------------------- 1 | # Example Caddyfile 2 | # This file is intended to be an example, and demonstrate some common options. 3 | # Do not copy and use it, but rather, consider these examples. Full 4 | # documentation at https://caddyserver.com/docs/caddyfile 5 | 6 | # Global options 7 | # The options set here will affect all code blocks below. 8 | 9 | { 10 | # Use the Let's Encrypt test server. This will issue certs that aren't 11 | # trusted by your browser, but it will also make it unlikely that you'll 12 | # exceed the Let's Encrypt rate limits 13 | # (see https://letsencrypt.org/docs/rate-limits/). Comment out this line 14 | # to use the production server instead. 15 | acme_ca https://acme-staging-v02.api.letsencrypt.org/directory 16 | 17 | # Email for certificate expiration notices and other alerts from Let's 18 | # Encrypt. Optional, but recommended. 19 | email you@somewhere.com 20 | 21 | # Debug mode. Extensive logging, may be useful in tracking down problems. 22 | # Uncomment to enable. 23 | # debug 24 | 25 | # If you're using Caddy behind a reverse proxy, and you're serving HTTPS 26 | # with Caddy, you may need to tell Caddy which site to serve clients 27 | # (i.e., your reverse proxy) who don't use SNI 28 | # default_sni sub.yourdomain.com 29 | } 30 | 31 | # All the examples below are name-based virtual hosts. For them to work 32 | # properly, whatever device is providing DNS for your network (likely your 33 | # router) needs to point their hostnames to the IP address of your Caddy 34 | # jail. Configuring this is beyond the scope of this guide. 35 | 36 | # A HTTP-only virtual host. Specifying port 80 disables Caddy's automatic 37 | # HTTPS. 38 | 39 | sub1.example.com:80 { 40 | 41 | # Document root. The * is required 42 | root * /usr/local/www/html1 43 | # Serve files from disk. This directive is required to serve static 44 | # (e.g., HTML) files. 45 | file_server 46 | 47 | # Access log will by default go to /var/log/caddy.log as JSON unless 48 | # changed 49 | log { 50 | output file /var/log/sub1.example.com.log 51 | format single_field common_log 52 | } 53 | 54 | # Reverse proxy Radarr and Sonarr. You'll be able to reach them at 55 | # http://sub1.example.com/radarr (or /sonarr) 56 | reverse_proxy /sonarr* 192.168.1.15:8989 57 | reverse_proxy /radarr* 192.168.1.15:7878 58 | } 59 | 60 | # A virtual host with automatic HTTPS, using HTTP validation for the cert. 61 | # For this to work, ports 80 and 443 must be open from the entire Internet 62 | # to your Caddy jail. Caddy will automatically obtain the cert from Let's 63 | # Encrypt, install it, and renew it when necessary. It will also redirect 64 | # HTTP to HTTPS requests. The only difference is the lack of a port number. 65 | 66 | sub2.example.com { 67 | 68 | root * /usr/local/html2 69 | file_server 70 | 71 | # Access log will be in .json if another format isn't specified 72 | log { 73 | output file /var/log/sub2.example.com.log 74 | } 75 | 76 | # Reverse proxy Jackett and Lidarr. In addition to providing a nice 77 | # URL as above, this will provide TLS termination (i.e., HTTPS) also. 78 | # (e.g., https://sub2.example.com/jackett) 79 | reverse_proxy /jackett* 192.168.1.15:9117 80 | reverse_proxy /lidarr* 192.168.1.15:8686 81 | } 82 | 83 | # Another virtual host with automatic HTTPS, but using DNS validation for 84 | # the cert. Support is currently limited to a few DNS hosts, and requires 85 | # a plugin that must be compiled into Caddy. This example will use 86 | # Cloudflare; consult the Caddy docs for other possibilities. 87 | 88 | sub3.example.com { 89 | 90 | # The tls directive modifies Caddy's TLS settings. Here, it tells 91 | # Caddy to obtain the cert using DNS validation, using the 92 | # Cloudflare plugin, and provides the API token to authenticate. 93 | tls { 94 | dns cloudflare long_api_token 95 | } 96 | 97 | root * /usr/local/html2 98 | file_server 99 | 100 | # No access log for this block 101 | log { 102 | output discard 103 | } 104 | } 105 | 106 | # Some applications, like Duplicati, don't support access via a subdirectory 107 | # (e.g., http://yourhost/duplicati). If you want to proxy to those, you'll 108 | # need a separate virtual host like this one. This example still does 109 | # automatic HTTPS, using HTTP validation. 110 | 111 | dup.example.com { 112 | 113 | # Reverse proxy all requests for this host name 114 | reverse_proxy 192.168.1.16:8200 115 | } -------------------------------------------------------------------------------- /includes/caddy: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | # PROVIDE: caddy 4 | # REQUIRE: LOGIN DAEMON NETWORKING 5 | # KEYWORD: shutdown 6 | 7 | # To enable caddy, add 'caddy_enable="YES"' to /etc/rc.conf or 8 | # /etc/rc.conf.local 9 | 10 | # Optional settings: 11 | # caddy_config (string): Full path to caddy config file 12 | # (/usr/local/etc/caddy/Caddyfile) 13 | # caddy_adapter (string): Config adapter type (caddyfile) 14 | # caddy_directory (string): Root for caddy storage (ACME certs, etc.) 15 | # (/var/db/caddy) 16 | # caddy_extra_flags (string): Extra flags passed to caddy start 17 | # caddy_logdir (string): Where caddy logs are stored 18 | # (/var/log/caddy) 19 | # caddy_logfile (string): Location of process log (${caddy_logdir}/caddy.log) 20 | # This is for startup/shutdown/error messages. 21 | # To create an access log, see: 22 | # https://caddyserver.com/docs/caddyfile/directives/log 23 | # caddy_user (user): User to run caddy (root) 24 | # caddy_group (group): Group to run caddy (wheel) 25 | # 26 | # This script will honor XDG_CONFIG_HOME/XDG_DATA_HOME. Caddy will create a 27 | # .../caddy subdir in each of those. By default, they are subdirs of /var/db/caddy. 28 | # See https://caddyserver.com/docs/conventions#data-directory 29 | 30 | . /etc/rc.subr 31 | 32 | name=caddy 33 | rcvar=caddy_enable 34 | desc="Powerful, enterprise-ready, open source web server with automatic HTTPS written in Go" 35 | 36 | load_rc_config $name 37 | 38 | # Defaults 39 | : ${caddy_enable:=NO} 40 | : ${caddy_adapter:=caddyfile} 41 | : ${caddy_config:=/usr/local/etc/caddy/Caddyfile} 42 | : ${caddy_directory:=/var/db/caddy} 43 | : ${caddy_extra_flags:=""} 44 | : ${caddy_logdir:="/var/log/${name}"} 45 | : ${caddy_logfile:="${caddy_logdir}/${name}.log"} 46 | : ${caddy_user:="root"} 47 | : ${caddy_group:="wheel"} 48 | 49 | # Config and base directories 50 | : ${XDG_CONFIG_HOME:="${caddy_directory}/config"} 51 | : ${XDG_DATA_HOME:="${caddy_directory}/data"} 52 | export XDG_CONFIG_HOME XDG_DATA_HOME 53 | 54 | command="/usr/local/bin/${name}" 55 | caddy_flags="--config ${caddy_config} --adapter ${caddy_adapter}" 56 | pidfile="/var/run/${name}/${name}.pid" 57 | 58 | required_files="${caddy_config} ${command}" 59 | 60 | start_precmd="caddy_precmd" 61 | start_cmd="caddy_start" 62 | stop_cmd="caddy_stop" 63 | 64 | # Extra Commands 65 | extra_commands="configtest reload" 66 | configtest_cmd="caddy_command validate ${caddy_flags}" 67 | reload_cmd="caddy_command reload ${caddy_flags}" 68 | 69 | caddy_command() 70 | { 71 | /usr/bin/su -m "${caddy_user}" -c "${command} $*" 72 | } 73 | 74 | caddy_precmd() 75 | { 76 | # Create required directories and set permissions 77 | /usr/bin/install -d -m 755 -o "${caddy_user}" -g "${caddy_group}" ${caddy_directory} 78 | /usr/bin/install -d -m 700 -o "${caddy_user}" -g "${caddy_group}" ${caddy_directory}/config 79 | /usr/bin/install -d -m 700 -o "${caddy_user}" -g "${caddy_group}" ${caddy_directory}/data 80 | /usr/bin/install -d -m 755 -o "${caddy_user}" -g "${caddy_group}" ${caddy_logdir} 81 | /usr/bin/install -d -m 700 -o "${caddy_user}" -g "${caddy_group}" /var/run/caddy 82 | } 83 | 84 | caddy_start() 85 | { 86 | echo -n "Starting caddy... " 87 | /usr/bin/su -m ${caddy_user} -c "${command} start ${caddy_flags} \ 88 | ${caddy_extra_flags} --pidfile ${pidfile}" >> ${caddy_logfile} 2>&1 89 | if [ $? -eq 0 ] && ps -ax -o pid | grep -q "$(cat ${pidfile})"; then 90 | echo "done" 91 | echo "Log: ${caddy_logfile}" 92 | else 93 | echo "Error: Caddy failed to start" 94 | echo "Check the caddy log: ${caddy_logfile}" 95 | fi 96 | } 97 | 98 | caddy_stop() 99 | { 100 | echo -n "Stopping caddy... " 101 | if caddy_command stop; then 102 | echo "done" 103 | else 104 | echo "Error: Unable to stop caddy" 105 | echo "Check the caddy log: ${caddy_logfile}" 106 | fi 107 | } 108 | 109 | run_rc_command "$1" --------------------------------------------------------------------------------