Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| services:firefox [2024/03/28 09:50] – created willy | services:firefox [2024/11/11 11:49] (current) – willy | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| check [[https:// | check [[https:// | ||
| - | Why? to navigate from your server wherever you are. | + | Why? to navigate from your server wherever you are: |
| + | * Bypass local filters/ | ||
| + | * Browse websites like you do from home | ||
| + | * Levergae your home ad-block setup | ||
| + | * Keep your browsing history totally private and secure | ||
| - | As the user you want to navigate with, create the **docker-compose.yml** file: | + | You will be able to acces your own firefox instance via any other web browser. Inside, it uses a VNC server/ |
| + | |||
| + | ===== Installation ===== | ||
| + | |||
| + | This is one of those use cases where a container is the perfect choice. The stack needed to achieve all this is not trivial and would be potentially not a good idea to set it up server-wide on your home server. | ||
| + | |||
| + | Now, if you plan to use firefox with multiple users you will need to replicate this setup for every user as you will need to spin up a separate container for each one. I will assume that **user** is the user you want your firefox | ||
| + | |||
| + | As **user** | ||
| <file - docker-compose.yml> | <file - docker-compose.yml> | ||
| version: ' | version: ' | ||
| Line 11: | Line 23: | ||
| firefox: | firefox: | ||
| image: jlesage/ | image: jlesage/ | ||
| + | environments: | ||
| + | - USER_ID=1000 | ||
| + | - GROUP_ID=1000 | ||
| ports: | ports: | ||
| - " | - " | ||
| volumes: | volumes: | ||
| - | - "/user/appdata/ | + | - "/home/user/ |
| </ | </ | ||
| - | adapt your port (5800) and config | + | Adapt your port (5800) and the USER_ID and GROUP_ID for **user**. You also need to specify a **config** folder, wihch must be existing and writable by **user**. |
| - | Now, setup a tunnel from your local PC to the server: | + | Then the usual: |
| <code bash> | <code bash> | ||
| - | ssh external-server1 -L5800: | + | su - user |
| + | podman compose pull | ||
| </ | </ | ||
| - | and then fireup your browser to **http:// | + | ==== Reverse Proxy ==== |
| + | |||
| + | Create the following NGINX config: | ||
| + | <file - firefox.conf> | ||
| + | location /firefox/ { | ||
| + | rewrite ^/ | ||
| + | proxy_ignore_client_abort on; | ||
| + | proxy_pass | ||
| + | proxy_redirect | ||
| + | proxy_cookie_path / / | ||
| + | } | ||
| + | </ | ||
| + | See [[selfhost: | ||
| + | |||
| + | ==== Autostart ==== | ||
| + | |||
| + | To start it, and set it up on boot, as usual follow my indications [[gentoo: | ||
| + | < | ||
| + | ln -s / | ||
| + | </ | ||
| + | |||
| + | and create the following config file: | ||
| + | < | ||
| + | USER=user | ||
| + | DESCRIPTION=" | ||
| + | </ | ||
| + | |||
| + | Add the service to the default runlevel and start it now: | ||
| + | <code bash> | ||
| + | rc-update add user-containers.firefox default | ||
| + | rc-service user-containers.firefox start | ||
| + | </ | ||
| + | |||
| + | Of course, you will want to adapt for multiple users, maybe. | ||
| + | |||
| + | |||
| - | (you can also setup a reverse proxy access to it, of course) | ||