Skip to content
Snippets Groups Projects
  1. Feb 20, 2019
  2. Feb 15, 2019
  3. Feb 12, 2019
  4. Feb 06, 2019
  5. Jan 27, 2019
  6. Jan 25, 2019
  7. Jan 24, 2019
  8. Jan 21, 2019
  9. Jan 16, 2019
  10. Jan 15, 2019
  11. Jan 13, 2019
  12. Jan 12, 2019
  13. Jan 10, 2019
  14. Jan 08, 2019
  15. Jan 03, 2019
  16. Dec 30, 2018
  17. Dec 11, 2018
  18. Dec 07, 2018
  19. Dec 06, 2018
  20. Dec 01, 2018
  21. Nov 19, 2018
  22. Nov 16, 2018
  23. Nov 01, 2018
  24. Oct 03, 2018
  25. Sep 20, 2018
  26. Sep 19, 2018
  27. Sep 13, 2018
  28. Aug 30, 2018
    • Daniel García's avatar
      Initial version of websockets notification support. · d70864ac
      Daniel García authored
      For now only folder notifications are sent (create, rename, delete).
      The notifications are only tested between two web-vault sessions in different browsers, mobile apps and browser extensions are untested.
      
      The websocket server is exposed in port 3012, while the rocket server is exposed in another port (8000 by default). To make notifications work, both should be accessible in the same port, which requires a reverse proxy.
      
      My testing is done with Caddy server, and the following config:
      
      ```
      localhost {
      
          # The negotiation endpoint is also proxied to Rocket
          proxy /notifications/hub/negotiate 0.0.0.0:8000 {
              transparent
          }
      
          # Notifications redirected to the websockets server
          proxy /notifications/hub 0.0.0.0:3012 {
              websocket
          }
      
          # Proxy the Root directory to Rocket
          proxy / 0.0.0.0:8000 {
              transparent
          }
      }
      ```
      
      This exposes the service in port 2015.
      d70864ac
  29. Aug 24, 2018
  30. Aug 21, 2018
  31. Aug 16, 2018
  32. Aug 15, 2018
Loading