Merge branch 'main' of github.com:bubl-ai/bubl-ai.github.io

bubl-ai · Feb 21, 2024 · f6934d4 · f6934d4
2 parents d1f54d3 + 20de1b8
commit f6934d4
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git a/_posts/2024-02-10-Raspberry-Pi-Setup.md b/_posts/2024-02-10-Raspberry-Pi-Setup.md
@@ -67,8 +67,18 @@ sudo apt install code
 ```
 
 Relevant Extensions to install:
++ Python, Pylance, and Python Debugger
 + Docker
++ Black Formatter
+  - Set `Editor: Default Formatter' as 'Black Formatter'.
+  - Go to `Black-formatter: Args` and set `--line-length=79`.
+  - Set `editor.formatOnSave` to `true`.
++ autoDocstring
+  - You can choose the docstring format of your preference.
++ GitLens
 + Dev Containers
+  - Include all the previous extensions by identifier within `Dev Containers: Default Extensions` so all your extensions will always be installed.
+  - Update the dev.containers.defaultFeatures and include inside it all the settings you want to propagate to your containers. (e.g. all the black Formatter and autoDocstring settings)
 
 ## 4. Connect to GitHub with SSH
 + Generate new ssh key, `ssh-keygen -t ed25519 -C "[[email protected]]"`

diff --git a/_posts/2024-02-12-Simple-Dockerfile-for-Dev-Purposes.md b/_posts/2024-02-12-Simple-Dockerfile-for-Dev-Purposes.md
@@ -76,5 +76,7 @@ Using a volume to provide sensitive information, such as an SSH key, during runt
 
 - **Dynamic Configuration:** With a volume, sensitive information can be changed without rebuilding the Docker image. This flexibility is valuable when updating credentials or keys without redeploying the entire application.
 
+> There seems to be a way to allow VSCode to automatically share the GitHub SSH key with your container. I haven't been able to make it work, but it is worth sharing, [LINK](https://code.visualstudio.com/remote/advancedcontainers/sharing-git-credentials). Let me know if it worked for you!
+
 ## Environmental Variables
 Setting up environmental variables correctly is important for both the security and functionality of your images. Make sure you create them either in the command line while starting container with `docker run -e [ENV_VAR_NAME]=$ENV_VAR_NAME`, or inside the container by executing `export [ENV_VAR_NAME]=[VALUE]`. If you choose the former make sure to not pass the sensitive information directly on the command line.