1. 17 Nov, 2018 1 commit
  2. 20 Apr, 2016 1 commit
    • W. Mark Kubacki's avatar
      Catch whitespace code style violations locally (#774) · 3c578dfb
      W. Mark Kubacki authored
      Those settings enforce convergence on common coding style with respect to whitespace.
      Do not use tabs to indent with shell scripts because those tabs most often
      serve the function of triggering command completion. Which could end a
      command before it is pasted completely.
        Traditionally indentation is two spaces here, not four.
      Other rules will catch stray whitespace at the end of lines or files, which,
      once committed, would annoy the next developer because his editor would strip
      them from lines he did not intended to modify in the first place.
  3. 20 Mar, 2016 2 commits
    • Matthew Holt's avatar
      Revert undesired changes to shell scripts · 3f49b320
      Matthew Holt authored
    • W-Mark Kubacki's avatar
      Convert the barbarism in dist/automate.sh to proper BASH structure · 74a5cb2f
      W-Mark Kubacki authored
          When thy variables henceforth accept blessed white-space,
          guided will thy scripture be along righteous path(s).
          -- 4 BASH 3:42
      Caddy's dist files sometimes ended up being owned by matt:staff or other
      quite arcane and/or frightening names. If someone extracting didn't pay
      attention a regular user who happened to have same uid by accident could
      later tamper with the files' contents. It's 0:0 from now on.
      Use all available threads when packaging distributables
      Caddy binaries will be added to their archives in-place: This change
      eliminates them being renamed within dist/builds one after another.
      As does 'gox', dist/automate.sh will spare one available thread if possible.
  4. 19 Mar, 2016 1 commit
  5. 18 Mar, 2016 1 commit
    • W-Mark Kubacki's avatar
      Service file for systemd starts after all networks have gotten IP addresses · f1c1ea99
      W-Mark Kubacki authored
      Unlike network.target the network-online.target guarantees that the network
      devices are online.
      If you bind to, [::], [::1], and/or only that is enough to
      proceed. But in case a particular IP is needed, like ${COREOS_PUBLIC_IPV4},
      we require any IP assignments to have completed before Caddy's start. That
      is achieved by depending on systemd-networkd-wait-online.service (which is
      scheduled before network-online.target, then, automatically).