https://github.com/meyskens/x-www-browser-forward
Forwarder for x-www-browser for containerized apps
https://github.com/meyskens/x-www-browser-forward
Last synced: 18 days ago
JSON representation
Forwarder for x-www-browser for containerized apps
- Host: GitHub
- URL: https://github.com/meyskens/x-www-browser-forward
- Owner: meyskens
- License: mit
- Created: 2017-06-11T13:39:46.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2018-04-10T08:19:01.000Z (about 7 years ago)
- Last Synced: 2025-03-24T09:11:29.376Z (about 1 month ago)
- Language: Go
- Size: 1.39 MB
- Stars: 7
- Watchers: 4
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
x-www-browser-forward
====================
If you're running apps inside Docker containers you might have noticed URLs won't open. This is of course because it is looking for a browser in it's own container. The simplest way to set a browser is by setting `/usr/bin/x-www-browser`, which is where to put the client binary.
On the host the server runs which listens to the socket for browser calls and forwards it to it's own /usr/bin/x-www-browser` which is a browser on the host or a script to call the container of your choice!
## How to use
1) Compile both the client and server with `go build`
2) Place the client as `/usr/bin/x-www-browser` in the containers
3) Make the server run as a service (see bellow SystemD section)
4) Link the `/var/run/browser.sock` socket to the container
Note: it doesn't work in every app yet due some diversity. It works in Slack! Some apps, like Thunderbird, can also be modified to point to the correct application that opens the browser.
## SystemD configuration
```
# Create folder for user SystemD processes
mkdir -p ~/.config/systemd/user
# Copy systemD configuration file from this repository
cp /path/to/this/git-repository/x-www-forwarder.service ~/.config/systemd/user/x-www-forwarder.service
# Alternatively you can link this file from this repo to ~/.config/systemd/user/x-www-forwarder.service
ln -s $(pwd)/x-www-forwarder.service ~/.config/systemd/user/x-www-forwarder.service
# Edit ~/.config/systemd/user/x-www-forwarder.service file and adjust the path to x-www-forwarder-server & browser-cmd
# enable systemd service on user login
sudo loginctl enable-linger volker
# systemd config file reload (optional) and start it
systemctl --user daemon-reload
systemctl --user start x-www-forwarder.service
```
Note: There might be easier and quicker ways...
### Optional command line arguments for the server part
```
Usage of x-www-browser-forwarder:
-browser-cmd string
Command to open URL (default "x-www-browser")
-socket-file string
Socket address (default "/var/run/browser.sock")
```
Note: The client defaults are not adjustable since you have full control with Docker on how to map the browser command and socket into the container.