1. 07 Jan, 2020 2 commits
    • Karel Koci's avatar
      Rename schnapps to more appropriate schnapps.uci · ade080d3
      Karel Koci authored
      It contains uci config and just plain schnapps is confusing naming.
      ade080d3
    • Karel Koci's avatar
      Revert "Add support for certbackup" · b9a54cf6
      Karel Koci authored
      This reverts commit 7ad0ba83.
      
      Certificate backup restore is handled by hook run by schnapps so this
      code duplicates that functionality. It should not be there.
      
      It is also wrong as some of the files are hidden (starting with dot)
      and this copy omits them. At the same time it prints error if there is
      no file in store (this is "fixed" by hiding errors but nooo).
      b9a54cf6
  2. 27 Nov, 2019 2 commits
  3. 18 Nov, 2019 2 commits
    • Michal Hrusecky's avatar
      Remove stale .info files · 3234356c
      Michal Hrusecky authored
      3234356c
    • David Beitey's avatar
      Fix mounting custom directories via sshfs · 48f6c64c
      David Beitey authored
      It appears that the script was attempting to allow URLs with a colon
      present to pass through unmodified, so someone could specify a custom
      directory to found, such as `ssh://host.example.com:/path/on/remote`.
      However, the regex check for  URLs was testing for the character
      literals :" (colon, double quote) within a protocol-stripped URL (which
      it has been at this point int he code, being
      `host.example.com:/path/on/remote`). Given how the later `sshfs` line
      operates (wraps $FINAL_REMOTE_URL in double quotes), if one was to
      specify a URL with `:"`, then it'll never end up working when passed to
      sshfs.
      
      This change simplifies the regex match for stripped URLs to just a `.*:`
      (colon character somewhere) such that if schapps detects a URL that's
      been passed to it like the first example above, it will mount
      `/path/on/remote` from `host.example.com`.
      
      Prior to this patch, there was no way of setting `remote.url` to a value
      that would allow mounting a specific path over sshfs; one could only
      mount `host.example.com:` (the default, which corresponds to the user's
      home directory).
      
      Given how the original code was written, it seems like it might have
      just been a typo having the double-quote character there.
      48f6c64c
  4. 22 Aug, 2019 1 commit
  5. 17 Jul, 2019 2 commits
  6. 14 May, 2019 1 commit
  7. 13 May, 2019 1 commit
  8. 28 Apr, 2019 6 commits
  9. 27 Apr, 2019 3 commits
  10. 26 Apr, 2019 2 commits
  11. 02 Feb, 2019 5 commits
  12. 22 Sep, 2018 2 commits
  13. 07 Aug, 2018 1 commit
  14. 07 Mar, 2018 1 commit
  15. 16 Nov, 2017 2 commits
  16. 09 Sep, 2017 1 commit
  17. 17 Jun, 2017 1 commit
  18. 22 Aug, 2016 1 commit
  19. 01 Aug, 2016 1 commit
  20. 27 Jul, 2016 3 commits