Bump requests from 2.31.0 to 2.32.2

.devcontainer/devcontainer.json

@@ -12,17 +12,24 @@
 
 	// The 'service' property is the name of the service for the container that VS Code should
 	// use. Update this value and .devcontainer/docker-compose.yml to the real service name.
-	"service": "blogs-svc",
+	"service": "tuxtechblog-mkdocs",
 
 	// The optional 'workspaceFolder' property is the path VS Code should open by default when
 	// connected. This is typically a file mount in .devcontainer/docker-compose.yml
-	"workspaceFolder": "/workspaces/${localWorkspaceFolderBasename}"
+	"workspaceFolder": "/workspaces/${localWorkspaceFolderBasename}",
+	"features": {
+		"ghcr.io/devcontainers/features/python:1": {},
+		"ghcr.io/devcontainers-contrib/features/zsh-plugins:0": {},
+		"ghcr.io/wxw-matt/devcontainer-features/command_runner:0": {},
+		"ghcr.io/schlich/devcontainer-features/powerlevel10k:1": {},
+		"ghcr.io/cirolosapio/devcontainers-features/alpine-ohmyzsh:0": {}
+	}
 
 	// Features to add to the dev container. More info: https://containers.dev/features.
 	// "features": {},
 
 	// Use 'forwardPorts' to make a list of ports inside the container available locally.
-	// "forwardPorts": [],
+	"forwardPorts": [8000]
 
 	// Uncomment the next line if you want start specific services in your Docker Compose config.
 	// "runServices": [],

.devcontainer/docker-compose.yml

@@ -1,7 +1,7 @@
-version: '3.9'
+version: '3.8'
 services:
   # Update this to the name of the service you want to work with in your docker-compose.yml file
-  blogs-svc:
+  tuxtechblog-mkdocs:
     # Uncomment if you want to override the service's Dockerfile to one in the .devcontainer 
     # folder. Note that the path of the Dockerfile and context is relative to the *primary* 
     # docker-compose.yml file (the first in the devcontainer.json "dockerComposeFile"

.dockerignore

@@ -0,0 +1,156 @@
+.env
+.DS_Store
+.env.prod
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintainted in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/

.github/workflows/ci_cd_prod.yml

@@ -1,5 +1,4 @@
-name: ci_cd_prod
-
+name: 🚀 PROD - Publish TuxTechBlogs via GitHub Actions & Github Pages
 on:
   workflow_dispatch:
   push:
@@ -9,25 +8,31 @@ permissions:
   contents: write
 
 jobs:
-  deploy_on_build:
+  build:
+    name: Deploy Mkdocs Website
     runs-on: ubuntu-latest
     steps:
-      - name: Checkout Github Repository
-        uses: actions/checkout@v3  # Use version 3 of the action
-
-      - name: Install Python
-        uses: actions/setup-python@v4  # Use version 4 of the action
-        with:
-          python-version: '3.x'
-
-      - name: Install Python Dependencies
-        run: |
-          echo "Installing The Python Dependencies"
-          pip install mkdocs mkdocs-material mkdocs-swagger-ui
-          echo "Completed Installing Python Dependencies"
+      - name: Checkout master Branch of Blogs
+        uses: actions/checkout@v2
 
-      - name: Deploy mkdocs Website
-        run: |
-          cd TuxTechBlogs
-          mkdocs gh-deploy -b prod-pages --clean --force
-          echo "Completed Deploying The Website"
+      - name: Deploy Blogs on Custom Domain
+        uses: mhausenblas/mkdocs-deploy-gh-pages@master
+        # Or use mhausenblas/mkdocs-deploy-gh-pages@nomaterial to build without the mkdocs-material theme
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          CUSTOM_DOMAIN: blogs.tuxtechlab.com
+          CONFIG_FILE: TuxTechBlogs/mkdocs.yml
+          EXTRA_PACKAGES: >
+            jinja2~=3.0
+            markdown~=3.2
+            mkdocs~=1.6
+            mkdocs-material-extensions~=1.3
+            pygments~=2.16
+            pymdown-extensions~=10.2
+            babel~=2.10
+            colorama~=0.4
+            paginate~=0.5
+            regex>=2022.4
+            requests~=2.26
+          # GITHUB_DOMAIN: github.myenterprise.com
+          REQUIREMENTS: requirements.txt