PairDrop is a sublime alternative to AirDrop that works on all platforms. Send images, documents or text via peer to peer connection to devices in the same local network/Wi-Fi or to paired devices.
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/pairdrop:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Web UI is accessible at http://SERVERIP:PORT. It is strongly recommended to run PairDrop via a reverse proxy, served over HTTPS, if you are making it publicly available. In this configuration you must ensure that the X-Forwarded-For header is being set correctly, otherwise all clients will be mutually visible.
Most proxies will set this header automatically but may require additional configuration if you are using something like Cloudflare Proxy.
To specify custom STUN/TURN servers for PairDrop clients to use, create a JSON config file in a mounted path and use the RTC_CONFIG environment variable to point to it.
You can use https://raw.githubusercontent.com/schlagmichdoch/PairDrop/master/rtc_config_example.json as a starting point.
Enabling WS_FALLBACK provides a fallback if the peer to peer WebRTC connection is not available to the client.
This is especially useful if you connect to your instance via a VPN as most VPN services block WebRTC completely in order to hide your real IP address.
Warning: All traffic sent between devices using this fallback is routed through the server and therefor not peer to peer! Traffic routed via this fallback is readable by the server and uses the server's bandwidth.
PairDrop is a sublime alternative to AirDrop that works on all platforms. Send images, documents or text via peer to peer connection to devices in the same local network/Wi-Fi or to paired devices.
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/pairdrop:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Web UI is accessible at http://SERVERIP:PORT. It is strongly recommended to run PairDrop via a reverse proxy, served over HTTPS, if you are making it publicly available. In this configuration you must ensure that the X-Forwarded-For header is being set correctly, otherwise all clients will be mutually visible.
Most proxies will set this header automatically but may require additional configuration if you are using something like Cloudflare Proxy.
To specify custom STUN/TURN servers for PairDrop clients to use, create a JSON config file in a mounted path and use the RTC_CONFIG environment variable to point to it.
You can use https://raw.githubusercontent.com/schlagmichdoch/PairDrop/master/rtc_config_example.json as a starting point.
Enabling WS_FALLBACK provides a fallback if the peer to peer WebRTC connection is not available to the client.
This is especially useful if you connect to your instance via a VPN as most VPN services block WebRTC completely in order to hide your real IP address.
Warning: All traffic sent between devices using this fallback is routed through the server and therefor not peer to peer! Traffic routed via this fallback is readable by the server and uses the server's bandwidth.
Last update: November 18, 2023 Created: February 5, 2019
\ No newline at end of file
diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index 0a62933b6d2328dfc8132f119fdf2c78a1da62b9..1bc8abbbbf5d0c729fdefe7c230efd83c0a91c4a 100644
GIT binary patch
delta 15
Wcmeyy`;C`PzMF$1dg(^C4{QJ}GX-=2
delta 15
Wcmeyy`;C`PzMF$%SKCIm4{QJ~(gm~t