import{_ as o,c as a,a3 as i,o as t}from"./chunks/framework.DtMx7FFi.js";const f=JSON.parse('{"title":"Swag Config","description":"","frontmatter":{"title":"Swag Config"},"headers":[],"relativePath":"configuration/swag-config.md","filePath":"configuration/swag-config.md"}'),s={name:"configuration/swag-config.md"};function n(l,e,r,c,p,d){return t(),a("div",null,e[0]||(e[0]=[i('

SWAG Configuration ​

Configuring the Secure Web Application Gateway has a lot of options and potential. It is primarily used to have one gateway for all your services hosted through two ports. Assuming you've used the Docker Compose file, you should be able to view and edit all the configuration files through /home/[USER]/appdata/swag. This location now has multiple places you can go.

  1. /home/[USER]/appdata/swag/nginx - This holds all of the webserver configuration files, this is where you will go when adding a new application/service.

TIP

Highly recommend learning how NGINX conf files work.

  1. /home/[USER]/appdata/swag/etc/letsencrypt - This holds all the relevant data for your SSL certificates using Let's Encrypt . The current certificates are in the "live" folder, under the domain name folder.
  2. /home/[USER]/appdata/swag/dns-conf - This holds the API keys or access information in order for SWAG to setup Let's Encrypt certificates or other DNS information. There are many providers available, however, Cloudflare will most likely be used. In order for a SSL Certificate to be issued, you will have to set this up.
  3. /home/[USER]/appdata/swag/www - This folder holds all of the static site stuff, if you decide to make a static site, you can host it through SWAG's configurations. This does take some patience, as getting the stuff exactly right is a bit tricky.

See How do I add a new application to my stack? for more information as to how to use the SWAG proxy-confs folder to add a new application to your hosting repertoire.

',7)]))}const u=o(s,[["render",n]]);export{f as __pageData,u as default};