Add Meshtastic config web server

.github/workflows/concatenate_gitignore.yml

@@ -0,0 +1,49 @@
+name: Update .gitignore
+
+on:
+  push:
+    paths:
+      - "**/.gitignore"
+      - ".gitignore.initial"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  update-gitignore:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      - name: Concatenate .gitignore files with directory paths
+        run: |
+          # Start with the initial .gitignore file
+          cp .gitignore.initial .gitignore
+
+          # Find all .gitignore files one level down, process each with its path prefix
+          find . -mindepth 2 -maxdepth 2 -name ".gitignore" | while read -r gitignore_file; do
+            dir_path=$(dirname "$gitignore_file" | sed 's|^\./||')
+            echo -e "\n# Patterns from $dir_path/.gitignore" >> .gitignore
+            sed "s|^|$dir_path/|" "$gitignore_file" >> .gitignore
+          done
+
+      - name: Check for changes
+        id: changes
+        run: |
+          if [[ -n "$(git status --porcelain .gitignore)" ]]; then
+            echo "changes=true" >> $GITHUB_ENV
+          else
+            echo "changes=false" >> $GITHUB_ENV
+          fi
+
+      - name: Commit and push if changes exist
+        if: env.changes == 'true'
+        run: |
+          git config --global user.name "github-actions[bot]"
+          git config --global user.email "github-actions[bot]@users.noreply.github.com"
+          git add .gitignore
+          git commit -m "Update top-level .gitignore with directory paths"
+          git push

.github/workflows/concatenate_rsync_exclude.yml

@@ -0,0 +1,50 @@
+name: Update .rsync.exlude
+
+on:
+  push:
+    paths:
+      - "**/.rsync.exclude"
+      - ".rsync.exclude.initial"
+      - ".github/actions/concatenate_rsync_exclude.yml"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  update-rsync-exclude:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      - name: Concatenate .rsync.exclude files with directory paths
+        run: |
+          # Start with the .rsync.exclude.initial file
+          cp .rsync.exclude.initial .rsync.exclude
+
+          # Find all .rsync.exclude files one level down, process each with its path prefix
+          find . -mindepth 2 -maxdepth 2 -name ".rsync.exclude" | while read -r rsync_excludes; do
+            dir_path=$(dirname "$rsync_excludes" | sed 's|^\./||')
+            echo -e "\n# Patterns from $dir_path/.rsync.exclude" >> .rsync.exclude
+            cat "$rsync_excludes" >> .rsync.exclude
+          done
+
+      - name: Check for changes
+        id: changes
+        run: |
+          if [[ -n "$(git status --porcelain .rsync.exclude)" ]]; then
+            echo "changes=true" >> $GITHUB_ENV
+          else
+            echo "changes=false" >> $GITHUB_ENV
+          fi
+
+      - name: Commit and push if changes exist
+        if: env.changes == 'true'
+        run: |
+          git config --global user.name "github-actions[bot]"
+          git config --global user.email "github-actions[bot]@users.noreply.github.com"
+          git add .rsync.exclude
+          git commit -m "Update top-level .rsync.exclude with directory paths"
+          git push

.gitignore.initial

@@ -0,0 +1,18 @@
+# Do not edit .gitignore - the file is assembled automatically by a Github action
+# from */.gitignore files and .gitignore.initial on pushes to the repo
+#
+# To add to .gitignore either edit the related .gitignore file in a subdirectory
+# or edit .gitignore.initial
+#
+# Be sure to git pull after pushing .gitignore modifications and after the action
+# runs, so that you get the updated .gitignore file in your local environment
+
+**/*.env
+
+avahi-dns/services
+
+home-assistant/config/
+
+redis/conf/
+
+upsd/config/

.gitmodules

@@ -1,3 +1,15 @@
 [submodule "db-backup"]
 	path = db-backup
 	url = https://github.com/romkey/hackstack-db-backup
+[submodule "auto_planka"]
+	path = auto_planka
+	url = https://github.com/romkey/auto_planka
+[submodule "pdxhackerspace-hackstack-trimetd"]
+	path = pdxhackerspace-hackstack-trimetd
+	url = git@github.com:romkey/pdxhackerspace-hackstack-trimetd.git
+[submodule "autogenerate-hosts"]
+	path = autogenerate-hosts
+	url = git@github.com:romkey/pdxhackerspace-hackstack-autogenerate-hosts.git
+[submodule "trimetd"]
+	path = trimetd
+	url = https://github.com/romkey/pdxhackerspace-hackstack-trimetd

.rsync.exclude

@@ -0,0 +1,51 @@
+# Do not edit .rsync.exclude
+# File is automatically built from .rsync.exclude.inital and */.rsync.exclude
+
+lost+found/
+containerd/
+docker/
+run/
+**/*.log
+
+# Patterns from frigate/.rsync.exclude
+lib/frigate/config/frigate.db
+
+# Patterns from home-assistant/.rsync.exclude
+lib/home-assistant/backups
+
+# Patterns from mariadb/.rsync.exclude
+lib/mariadb
+
+# Patterns from grafana/.rsync.exclude
+lib/grafana/grafana.db
+
+# Patterns from esphome/.rsync.exclude
+lib/esphome/.esphome
+
+# Patterns from mosquitto/.rsync.exclude
+lib/mosquitto/mosquitto.db
+
+# Patterns from postgresql/.rsync.exclude
+lib/postgresql
+
+# Patterns from calibre-web/.rsync.exclude
+lib/calibre-web/metadatab.db
+
+# Patterns from jellyfin/.rsync.exclude
+lib/jellyfin/data/jellyfin.db
+lib/jellyfin/data/jellyfin.db-shm
+lib/jellyfin/data/jellyfin.db-wal
+lib/jellyfin/data/library.db
+lib/jellyfin/data/library.db-shm
+lib/jellyfin/data/library.db-wal
+
+# Patterns from music-assistant/.rsync.exclude
+lib/music-assistant/cache.db
+lib/music-assistant/library.db
+
+# Patterns from influxdb/.rsync.exclude
+lib/influxdb/engine
+lib/influxdb/influxd.sqlite
+
+# Patterns from nginx-proxy-manager/.rsync.exclude
+lib/nginx-proxy-manager/database.sqlite

.rsync.exclude.initial

@@ -0,0 +1,8 @@
+# Do not edit .rsync.exclude
+# File is automatically built from .rsync.exclude.inital and */.rsync.exclude
+
+lost+found/
+containerd/
+docker/
+run/
+**/*.log

CODE_OF_CONDUCT.md

@@ -0,0 +1,135 @@
+<!--
+SPDX-FileCopyrightText: 2014 Coraline Ada Ehmke
+SPDX-FileCopyrightText: 2019 Kattni Rembor for Adafruit Industries
+SPDX-License-Identifier: CC-BY-4.0
+-->
+
+# Adafruit Community Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and leaders pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level or type of
+experience, education, socio-economic status, nationality, personal appearance,
+race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+We are committed to providing a friendly, safe and welcoming environment for
+all.
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Be kind and courteous to others
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Collaborating with other community members
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and sexual attention or advances
+* The use of inappropriate images, including in a community member's avatar
+* The use of inappropriate language, including in a community member's nickname
+* Any spamming, flaming, baiting or other attention-stealing behavior
+* Excessive or unwelcome helping; answering outside the scope of the question
+  asked
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Promoting or spreading disinformation, lies, or conspiracy theories against
+  a person, group, organisation, project, or community
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate
+
+The goal of the standards and moderation guidelines outlined here is to build
+and maintain a respectful community. We ask that you don’t just aim to be
+"technically unimpeachable", but rather try to be your best self.
+
+We value many things beyond technical expertise, including collaboration and
+supporting others within our community. Providing a positive experience for
+other community members can have a much more significant impact than simply
+providing the correct answer.
+
+## Our Responsibilities
+
+Project leaders are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project leaders have the right and responsibility to remove, edit, or
+reject messages, comments, commits, code, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any community member for other behaviors that they deem
+inappropriate, threatening, offensive, or harmful.
+
+## Moderation
+
+Instances of behaviors that violate the Adafruit Community Code of Conduct
+may be reported by any member of the community. Community members are
+encouraged to report these situations, including situations they witness
+involving other community members.
+
+You may report in the following ways:
+
+In any situation, you may send an email to <support@adafruit.com>.
+
+On the Adafruit Discord, you may send an open message from any channel
+to all Community Moderators by tagging @community moderators. You may
+also send an open message from any channel, or a direct message to
+@kattni#1507, @tannewt#4653, @Dan Halbert#1614, @cater#2442,
+@sommersoft#0222, @Mr. Certainly#0472 or @Andon#8175.
+
+Email and direct message reports will be kept confidential.
+
+In situations on Discord where the issue is particularly egregious, possibly
+illegal, requires immediate action, or violates the Discord terms of service,
+you should also report the message directly to Discord.
+
+These are the steps for upholding our community’s standards of conduct.
+
+1. Any member of the community may report any situation that violates the
+Adafruit Community Code of Conduct. All reports will be reviewed and
+investigated.
+2. If the behavior is an egregious violation, the community member who
+committed the violation may be banned immediately, without warning.
+3. Otherwise, moderators will first respond to such behavior with a warning.
+4. Moderators follow a soft "three strikes" policy - the community member may
+be given another chance, if they are receptive to the warning and change their
+behavior.
+5. If the community member is unreceptive or unreasonable when warned by a
+moderator, or the warning goes unheeded, they may be banned for a first or
+second offense. Repeated offenses will result in the community member being
+banned.
+
+## Scope
+
+This Code of Conduct and the enforcement policies listed above apply to all
+Adafruit Community venues. This includes but is not limited to any community
+spaces (both public and private), the entire Adafruit Discord server, and
+Adafruit GitHub repositories. Examples of Adafruit Community spaces include
+but are not limited to meet-ups, audio chats on the Adafruit Discord, or
+interaction at a conference.
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. As a community
+member, you are representing our community, and are expected to behave
+accordingly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at
+<https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>,
+and the [Rust Code of Conduct](https://www.rust-lang.org/en-US/conduct.html).
+
+For other projects adopting the Adafruit Community Code of
+Conduct, please contact the maintainers of those projects for enforcement.
+If you wish to use this code of conduct for your own project, consider
+explicitly mentioning your moderation policy or making a copy with your
+own moderation policy so as to avoid confusion.

LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2023 John Romkey
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.