I suggest adding a few example usage of loginsrv as a Standalone microservice on the main page.

I think these should be added:

• Basics (help being available with loginsrv -help)
• HTTPd (Apache)
• NGINX
• Caddy 1
• Caddy 2

https://github.com/Arkq/flake8-requirements

I was just trying to build caddy binary with a custom set of plugins, but got stuck with the invalid import path "" error.

Looks like most of us are trying to use the qualified name of the plugin instead of just the last part of it (abiosoft/caddy-docker#108 (comment)). I.e:

RUN VERSION="1.0.3" \
    PLUGINS="http.prometheus" \
    ENABLE_TELE

1. What version of Caddy are you using (caddy -version)?

Caddy 0.11.0

2. What are you trying to do?

Make a http2 proxy use caddy, I hope it can support WebSocket.

I use Chrome + SwitchyOmega for client.

PAC file:

function FindProxyForURL(url, host) {
  return "HTTPS example.com:443";
}

3. What is your entire Caddyfile?

example.com:443 {
 

相关依赖都已经安装，但是最后的时候报错了
Traceback (most recent call last):
File "brook-web.py", line 16, in
from flask import Flask,render_template,send_from_directory
ImportError: No module named flask

root@server:~/new# caddy install http.filemanager

  Caddy Web Server is already installed on
  /opt/caddyserver/caddy

root@server:~/new# caddy version

  Caddy Web Server v1.0.0-beta2
  Caddy Web Server Installer - v6.1 pre (NEXT)
  PHP 5.5.9-1ubuntu4.27 (cli) (built: Mar  5 2019 18:56:49)

root@server:~/new# caddy start
  Starting Caddy Web Server...2019/04/21 00:03:51 /etc/C

# caddy -version
Caddy 0.11.1 (non-commercial use only)

Considering the following Caddyfile:

http://www.example.com {
    root /web/www.example.com/public
    git https://github.com/example/example.com {
        hook     /path TOKEN
        branch   {latest}
        path     ..
        then     /hugo --destination=/web/www.example.com/public --cleanDestinationDir
 

@mholt has announced that Caddy 2 may hit stable by early next year. Based on a quick glance at the new docs, there are lots of changes to how plugins (soon to be called modules) work, and it will likely require a complete rewrite to support JWT auth in Caddy 2. I plan to post a deprecation notice on the readme so people know that no further develo

So I added this entry to docker compose

  sslwykop2:
    image: "katacoda/docker-http-server:v2"
    labels:
      - "virtual.host=test2.ssl-wykop.pl"  # your domains separated with a space
      - "virtual.port=80"  # exposed port of this container
      - "virtual.tls-email=my@email.com"  # ssl is now on
      - "virtual.websockets" # enable websocket passthrough

It works, bu

It would be useful if Caddy could treat different cached paths differently, like how Caddy's header directive works. However, looking at setup.go it appears that DefaultMaxAge and other options are global to the whole middleware.

If I try to specify multiple cache blocks in my Caddyfile, Caddy doesn't complain, but I don't see the behavior I would ex

Currently (commit 00eef4cfb164fc91d97ae620bcc7581663ad5854 at the time of this writing), the adapter doesn't completely handle include directive. There's primitive support for the directive, which is why it is not documented as supported. Big part of the reason is due to difficulty in resolution of the absolute path of the file to be included. The resolution problem should be easy to solve now u

if hook.service is build into caddy using current master if caddy is run from command line in windows and then stopped by ctrl-c the following panic happens

panic: close of closed channel

goroutine 81 [running]:
github.com/mholt/caddy/vendor/github.com/mholt/certmagic.(*Cache).Stop(...)
        D:/godev/src/github.com/mholt/caddy/vendor/github.com/mholt/certmagic/cache.go:87
github.c

root@ubuntu:/home/gopkg/src/github.com/pieterlouw/caddy-net/caddynet# go build caddynet.go
# github.com/caddyserver/caddy/caddytls
/home/gopkg/pkg/mod/github.com/caddyserver/caddy@v1.0.4/caddytls/tls.go:80:42: not enough arguments in call to certmagic.NewDefault().RevokeCert
        have (string, bool)
        want (context.Context, string, bool)
root@ubuntu:/home/gopkg/src/github.com/pi

Expected behavior

In the multipass login form, when I click submit, I expect to receive an email to the address I entered.

Observed behavior

caddy crashes with this error when I click submit:

caddy -conf=/etc/caddy/Caddyfile -log stdout
Activating privacy features... done.
multipass for https://test.quickgene.net is initialized
https://test.quickgene.net
2017/01/19 13:01

The readme is a little confusing. The feature table uses the following symbols: x, -, and ✓ and I'm confused what each of those symbols actually means? As an example, does x means it supports that feature, or that it does not support the feature?

• Deployment docs
• Set clear goals of the project on README
• Describe what I mean with "setup close to production" since the development is with Docker Compose and deployment with Docker Swarm and that may be confusing. (I'm actually talking about specific parts like focusi