freenas-iocage-caddy | Script to install Caddy V2 in a FreeNAS jail
kandi X-RAY | freenas-iocage-caddy Summary
kandi X-RAY | freenas-iocage-caddy Summary
freenas-iocage-caddy is a Shell library typically used in Debian applications. freenas-iocage-caddy has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.
Script to install Caddy V2 in a FreeNAS jail
Script to install Caddy V2 in a FreeNAS jail
Support
Quality
Security
License
Reuse
Support
freenas-iocage-caddy has a low active ecosystem.
It has 12 star(s) with 1 fork(s). There are 2 watchers for this library.
It had no major release in the last 6 months.
There are 0 open issues and 1 have been closed. On average issues are closed in 2 days. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of freenas-iocage-caddy is current.
Quality
freenas-iocage-caddy has 0 bugs and 0 code smells.
Security
freenas-iocage-caddy has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
freenas-iocage-caddy code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
freenas-iocage-caddy is licensed under the GPL-3.0 License. This license is Strong Copyleft.
Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.
Reuse
freenas-iocage-caddy releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of freenas-iocage-caddy
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of freenas-iocage-caddy
freenas-iocage-caddy Key Features
No Key Features are available at this moment for freenas-iocage-caddy.
freenas-iocage-caddy Examples and Code Snippets
No Code Snippets are available at this moment for freenas-iocage-caddy.
Community Discussions
No Community Discussions are available at this moment for freenas-iocage-caddy.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install freenas-iocage-caddy
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:.
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.
DEFAULT_GW_IP is the address for your default gateway
POOL_PATH is the path for your data pool.
JAIL_NAME: The name of the jail, defaults to "caddy"
CONFIG_PATH: This is the path to your Caddyfile, defaults to $POOL_PATH/apps/caddy.
INTERFACE: The network interface to use for the jail. Defaults to vnet0.
VNET: Whether to use the iocage virtual network stack. Defaults to on.
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 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.
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.
DEFAULT_GW_IP is the address for your default gateway
POOL_PATH is the path for your data pool.
JAIL_NAME: The name of the jail, defaults to "caddy"
CONFIG_PATH: This is the path to your Caddyfile, defaults to $POOL_PATH/apps/caddy.
INTERFACE: The network interface to use for the jail. Defaults to vnet0.
VNET: Whether to use the iocage virtual network stack. Defaults to on.
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 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.
Support
Questions or issues about this resource can be raised in this forum thread. 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. Though we'll try to help on that thread, once Caddy's up and running, the Caddy forum 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.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page