Djeex/docudjeex
1
1
Fork 0
Code Issues Pull Requests Actions Projects Wiki Activity

Add Uptime-Kuma introduction, write descriptive alt text site-wide, and fix brand capitalization and filenames with spaces

Browse Source
This commit is contained in:
Djeex
2026-09-07 14:35:25 +02:00
parent eff68287f2
commit 67d593cb73
90 changed files with 380 additions and 376 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/3.serveex/7.files/1.file-browser-quantum.md
+4 -4
View File
@@ -104,14 +104,14 @@ Deploy the container and go to `http://yourserverip:8020`. Log in with the defau
__If it doesn't work:__ check your firewall rules.
::
## Exposing File Browser Quantum with Swag
## Exposing File Browser Quantum with SWAG
::warning
File Browser Quantum does not support multi-factor authentication. Exposing it publicly could put your systems at risk. Only do this if you're using a secure authentication solution like [TinyAuth](/serveex/security/tinyauth) or [Authentik](/serveex/advanced/authentik/). Otherwise, don't expose it with SWAG. Use a VPN like [Wireguard](/serveex/core/wireguard) instead.
File Browser Quantum does not support multi-factor authentication. Exposing it publicly could put your systems at risk. Only do this if you're using a secure authentication solution like [TinyAuth](/serveex/security/tinyauth) or [Authentik](/serveex/advanced/authentik/). Otherwise, don't expose it with SWAG. Use a VPN like [WireGuard](/serveex/core/wireguard) instead.
::
You may want to access File Browser Quantum remotely from all your devices. To do that, we'll expose it through Swag.
You may want to access File Browser Quantum remotely from all your devices. To do that, we'll expose it through SWAG.
::note{icon=""}
@@ -149,7 +149,7 @@ Restart the stack by clicking "deploy" and wait for SWAG to fully initialize.
### Create the subdomain.conf file
In the Swag folders, create the file `fbq.subdomain.conf`.
In the SWAG folders, create the file `fbq.subdomain.conf`.
```bash [Terminal]
sudo nano /srv/docker/swag/config/nginx/proxy-confs/fbq.subdomain.conf
content/en/3.serveex/7.files/2.pingvin.md
+9 -9
View File
@@ -8,7 +8,7 @@ description: Install Pingvin Share, a self-hosted file sharing platform to send
[Pingvin](https://github.com/stonith404/pingvin-share) is a tool for quickly sharing files, similar to WeTransfer. Its many sharing options (password, expiration time, custom link, etc.) make it the ideal tool for sharing files quickly. Pingvin can also create _upload requests_, i.e. a shareable link you can send to someone so they can upload their files for you to retrieve.
![picture](/img/serveex/pingvin.png)
![Pingvin Share web interface for uploading and sharing files](/img/serveex/pingvin.png)
## Installation
@@ -42,7 +42,7 @@ services:
```
::note
From here on, we assume the network name for Swag is `swag_default`.
From here on, we assume the network name for SWAG is `swag_default`.
::
::tip{icon=""}
@@ -74,8 +74,8 @@ Deploy the container and go to `http://yourserverip:3600`. That's it! Your Pingv
__If it fails:__ check your firewall rules.
::
## Exposing Pingvin with Swag
The whole point of a solution like this is being able to access it remotely, from all your devices. To do this, we'll expose Pingvin through Swag.
## Exposing Pingvin with SWAG
The whole point of a solution like this is being able to access it remotely, from all your devices. To do this, we'll expose Pingvin through SWAG.
::note{icon=""}
📋 __Prerequisite:__ <br/><br/>
@@ -113,7 +113,7 @@ Redeploy the stack by clicking "deploy" and wait for SWAG to be fully up.
### Create the subdomain.conf file
In the Swag folders, create the `pingvin.subdomain.conf` file.
In the SWAG folders, create the `pingvin.subdomain.conf` file.
::tip{icon="" to="/serveex/files/file-browser-quantum"}
@@ -224,15 +224,15 @@ In your Authentik admin area, create an OAuth2/OpenID provider.
Fill in each section as follows, replacing `mydomain.com` with your own domain. Copy the `Client ID` and `Client Secret` fields somewhere safe.
![picture](/img/serveex/pingvin-auth1.png)
![picture](/img/serveex/pingvin-auth2.png)
![picture](/img/serveex/pingvin-auth3.png)
![Authentik OAuth2/OpenID provider configuration screen, part 1](/img/serveex/pingvin-auth1.png)
![Authentik OAuth2/OpenID provider configuration screen, part 2](/img/serveex/pingvin-auth2.png)
![Authentik OAuth2/OpenID provider configuration screen, part 3](/img/serveex/pingvin-auth3.png)
#### Create the application
Save and create a `pingvin` application as follows.
![picture](/img/serveex/pingvin-auth4.png)
![Authentik application creation screen for Pingvin Share](/img/serveex/pingvin-auth4.png)
#### Add the provider to your outpost