Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
S
snip
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Gophers
  • snip
  • Issues
  • #4

Closed
Open
Created Oct 14, 2018 by Che@che☀Owner

Add "client"

I had in mind that it would be convenient if, when not using -Obfuscate, the server would broadcast the information about its current configuration. Something like:

  • server: snip /path/to/share/, choosing port 8233, only a single IPv4 address, say 192.168.22.25/24
  • server: starts broadcasting http://192.168.22.25:8233/ on subnet 192.168.22.0/24
  • client: snip (on same subnet), acting as client and listens to broadcast, receives broadcast of server, shows http://192.168.22.25:8233/ as available endpoint, et voilà.

This obviously makes it way easier to find the server, so broadcasting needs a parameter to either activate or deactivate it.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None