init

install/dp-config.md

@@ -0,0 +1,37 @@
+---
+title: DP-Salad Configuration
+---
+
+# Configuration
+
+## Debian Configuration :logos-debian:
+
+Sudo should have been setup after the install, however, nothing much else is required for the setup end in Debian. If you want, here is a list of recommended software to install to make the commandline a little easier to learn:
+
+1. **TLDR** **:simple-icons-tldraw:**
+
+```sh
+sudo apt-get install tldr, tldr -u
+```
+
+2. **Tmux** **:simple-icons-tmux:**
+
+```sh
+sudo apt-get install tmux
+```
+
+## Portainer Configuration :simple-icons-portainer:
+
+Portainer is ready right out of the box. There should be nothing you need to do to configure it, unless you are running a "*clustered setup*" involving more than one computer, which can be done for this stack, but does add a layer of complexity, and allows for scalability for the amount of applications you can offer to either yourself or your users. A "*clustered setup*" is on the [Portainer CE wiki](https://docs.portainer.io/) and is out of the scope for this guide.
+
+If you are using the VM Template, Portainer has the custom templates loaded so that if you need to install a newer version, or change something and restart, they are there.
+
+## App Templates :material-symbols-touch-app:
+
+In Portainer, [App Templates](https://docs.portainer.io/user/docker/templates) enable you to easily deploy services with a predetermined configuration, while allowing you to customize options through the web UI. While Portainer ships with some default templates (see [portainer/templates](https://github.com/portainer/templates)), it's often helpful to have 1-click access to many more apps + stacks, without having to constantly switch template sources.
+
+Under Settings → App Templates in your Portainer GUI, paste this URL:
+
+```sh
+https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
+```