diff --git a/.gitignore b/.gitignore index db903f8..8f373c3 100644 --- a/.gitignore +++ b/.gitignore @@ -2,10 +2,10 @@ * # But not these directories; this allows us to look inside them -# !*/ +!*/ # But not these files -!README.md +!*/README.md !.gitignore !**/.env.example !**/Dockerfile @@ -24,6 +24,7 @@ # Homeassistant !**/homeassistant/config/configuration.yaml +!**/homeassistant/README.md # Perplexica !**/config.toml \ No newline at end of file diff --git a/caddy/services/mm-project.caddy b/caddy/services/mm-project.caddy new file mode 100644 index 0000000..6fd4ede --- /dev/null +++ b/caddy/services/mm-project.caddy @@ -0,0 +1,9 @@ +# External +marlene.mixel.cloud { + reverse_proxy 192.168.178.126:80 + handle_path /api* { + reverse_proxy 192.168.178.126:3000 + } +} + +# Internal \ No newline at end of file diff --git a/caddy/services/vaultwarden.caddy b/caddy/services/vaultwarden.caddy index df53524..bf520d4 100644 --- a/caddy/services/vaultwarden.caddy +++ b/caddy/services/vaultwarden.caddy @@ -1,6 +1,10 @@ # External +#vault.mixel.cloud { +# reverse_proxy 192.168.178.4:4743 +#} + vault.mixel.cloud { - reverse_proxy 192.168.178.4:4743 + reverse_proxy 192.168.178.230:9898 } # Internal \ No newline at end of file diff --git a/git-server/forgejo/.env.example b/git-server/forgejo/.env.example new file mode 100644 index 0000000..1997831 --- /dev/null +++ b/git-server/forgejo/.env.example @@ -0,0 +1,3 @@ +DB_USER= +DB_PASSWORD= +DB_NAME= \ No newline at end of file diff --git a/git-server/forgejo/compose.yml b/git-server/forgejo/compose.yml new file mode 100644 index 0000000..70d6f74 --- /dev/null +++ b/git-server/forgejo/compose.yml @@ -0,0 +1,45 @@ + +services: + server: + image: codeberg.org/forgejo/forgejo:9.0.3 + container_name: forgejo + restart: always + environment: + - USER_UID=1000 + - USER_GID=1000 + - FORGEJO__database__DB_TYPE=postgres + - FORGEJO__database__HOST=db #:5432 + - FORGEJO__database__NAME=${DB_NAME} + - FORGEJO__database__USER=${DB_USER} + - FORGEJO__database__PASSWD=${DB_PASSWORD} + networks: + - forgejo + volumes: + - ./data:/data + - /etc/timezone:/etc/timezone:ro + - /etc/localtime:/etc/localtime:ro + ports: + - "3333:3000" + - "222:22" + depends_on: + - db + + db: + image: postgres:latest # postgres:14 + restart: always + environment: + - POSTGRES_USER=${DB_USER} + - POSTGRES_PASSWORD=${DB_PASSWORD} + - POSTGRES_DB=${DB_NAME} + networks: + - forgejo + volumes: + - db_forgejo:/var/lib/postgresql/data + +networks: + forgejo: + external: false + +volumes: + db_forgejo: + external: false \ No newline at end of file diff --git a/vaultwarden/.env.example b/vaultwarden/.env.example new file mode 100644 index 0000000..fd762f5 --- /dev/null +++ b/vaultwarden/.env.example @@ -0,0 +1,8 @@ +ADMIN_TKOEN= +DOMAIN= + +SIGNUPS_ALLOWED=false +EMERGENCY_ACCESS_ALLOWED=true +WEB_VAULT_ENABLED=true +LOGIN_RATELIMIT_MAX_BURST=10 +LOGIN_RATELIMIT_SECONDS=60 \ No newline at end of file diff --git a/vaultwarden/compose.yml b/vaultwarden/compose.yml new file mode 100644 index 0000000..1cf9c0f --- /dev/null +++ b/vaultwarden/compose.yml @@ -0,0 +1,11 @@ +services: + vaultwarden: + container_name: vaultwarden + image: vaultwarden/server:latest + restart: unless-stopped + volumes: + - ./vw-data/:/data/ + env_file: + - .env + ports: + - 9898:80 diff --git a/vscode-server/config/extensions/ms-azuretools.vscode-docker-1.29.3-universal/README.md b/vscode-server/config/extensions/ms-azuretools.vscode-docker-1.29.3-universal/README.md deleted file mode 100644 index d7aa0e0..0000000 --- a/vscode-server/config/extensions/ms-azuretools.vscode-docker-1.29.3-universal/README.md +++ /dev/null @@ -1,106 +0,0 @@ -## Docker for Visual Studio Code [![Version](https://img.shields.io/visual-studio-marketplace/v/ms-azuretools.vscode-docker)](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-docker) [![Installs](https://img.shields.io/visual-studio-marketplace/i/ms-azuretools.vscode-docker)](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-docker) - -The Docker extension makes it easy to build, manage, and deploy containerized applications from Visual Studio Code. It also provides one-click debugging of Node.js, Python, and .NET inside a container. - -![Docker extension overview](https://github.com/microsoft/vscode-docker/raw/HEAD/resources/readme/overview.gif) - -**Check out the [Working with containers](https://aka.ms/AA7arez) topic on the Visual Studio Code documentation site to get started**. - -[The Docker extension wiki](https://github.com/Microsoft/vscode-docker/wiki) has troubleshooting tips and additional technical information. - -## Installation - -[Install Docker](https://docs.docker.com/install/) on your machine and add it to the system path. - -On Linux, you should [enable rootless Docker](https://docs.docker.com/engine/security/rootless/) and set the generated Docker context to "rootless" (more secure) or [enable Docker CLI for the non-root user account](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) (less secure) that will be used to run VS Code. - -To install the extension, open the Extensions view, search for `docker` to filter results and select Docker extension authored by Microsoft. - -## Overview of the extension features - -### Editing Docker files - -You can get IntelliSense when editing your `Dockerfile` and `docker-compose.yml` files, with completions and syntax help for common commands. - -![IntelliSense for Dockerfiles](https://github.com/microsoft/vscode-docker/raw/HEAD/resources/readme/dockerfile-intellisense.png) - -In addition, you can use the Problems panel (Ctrl+Shift+M on Windows/Linux, Shift+Command+M on Mac) to view common errors for `Dockerfile` and `docker-compose.yml` files. - -### Generating Docker files - -You can add Docker files to your workspace by opening the Command Palette (F1) and using **Docker: Add Docker Files to Workspace** command. The command will generate a `Dockerfile` and `.dockerignore` file and add them to your workspace. The command will also ask you if you want to add Docker Compose files as well, but this is optional. - -The extension can scaffold Docker files for most popular development languages (C#, Node.js, Python, Ruby, Go, and Java) and customizes the generated Docker files accordingly. When these files are created, we also create the necessary artifacts to provide first-class debugging support for Node.js, Python, and .NET (C#). - -### Docker Explorer - -The Docker extension contributes a Docker Explorer view to VS Code. The Docker Explorer lets you examine and manage Docker assets: containers, images, volumes, networks, and container registries. - -The right-click menu provides access to commonly used commands for each type of asset. - -![Docker view context menu](https://github.com/microsoft/vscode-docker/raw/HEAD/resources/readme/docker-view-context-menu.gif) - -You can rearrange the Docker view panes by dragging them up or down with a mouse and use the context menu to hide or show them. - -![Customize Docker view](https://github.com/microsoft/vscode-docker/raw/HEAD/resources/readme/docker-view-rearrange.gif) - -### Docker commands - -Many of the most common Docker commands are built right into the Command Palette: - -![Docker commands](https://github.com/microsoft/vscode-docker/raw/HEAD/resources/readme/command-palette.png) - -You can run Docker commands to manage [images](https://docs.docker.com/engine/reference/commandline/image/), [networks](https://docs.docker.com/engine/reference/commandline/network/), [volumes](https://docs.docker.com/engine/reference/commandline/volume/), [image registries](https://docs.docker.com/engine/reference/commandline/push/), and [Docker Compose](https://docs.docker.com/compose/reference/overview/). In addition, the **Docker: Prune System** command will remove stopped containers, dangling images, and unused networks and volumes. - - -### Docker Compose - -[Docker Compose](https://docs.docker.com/compose/) lets you define and run multi-container applications with Docker. Our [Compose Language Service](https://github.com/microsoft/compose-language-service) in the Docker extension gives you IntelliSense and tab completions when authoring `docker-compose.yml` files. Press `Ctrl+Space` to see a list of valid Compose directives. - - ![Docker Compose IntelliSense](https://github.com/microsoft/vscode-docker/raw/HEAD/resources/readme/tab-completions.gif) - - -We also provide tooltips when you hover over a Docker Compose YAML attribute. - - ![Docker Compose Tooltips](https://github.com/microsoft/vscode-docker/raw/HEAD/resources/readme/hover-support.png) - - -While `Compose Up` allows you to run all of your services at once, our new feature `Compose Up - Select Services` lets you select any combination of the services you want to run. - -![Docker Compose Up - Select Subset](https://github.com/microsoft/vscode-docker/raw/HEAD/resources/readme/select-subset.gif) - -Once your `Compose Up` command completes, navigate to the Docker Explorer to view your services as a Compose Group. This allows you to start, stop, and view the logs of each service as a group. - -![Docker Compose Groups](https://github.com/microsoft/vscode-docker/raw/HEAD/resources/readme/compose-group.png) - -### Using image registries - -You can display the content and push, pull, or delete images from [Docker Hub](https://hub.docker.com/) and [Azure Container Registry](https://docs.microsoft.com/azure/container-registry/): - -![Azure Container Registry content](https://github.com/microsoft/vscode-docker/raw/HEAD/resources/readme/container-registry.png) - -An image in an Azure Container Registry can be deployed to Azure App Service directly from VS Code. See [Deploy images to Azure App Service](https://aka.ms/AA7arf8) to get started. For more information about how to authenticate to and work with registries, see [Using container registries](https://aka.ms/AA7arf9). - -### Debugging services running inside a container - -You can debug services built using Node.js, Python, or .NET (C#) that are running inside a container. The extension offers custom tasks that help with launching a service under the debugger and with attaching the debugger to a running service instance. For more information, see [Debug containerized apps](https://aka.ms/AA7arfb) and [Customize the Docker extension](https://aka.ms/AA7ay8l). - -### Azure CLI integration - -You can start Azure CLI (command-line interface) in a standalone, Linux-based container with **Docker Images: Run Azure CLI** command. This gives you access to the full Azure CLI command set in an isolated environment. For more information on available commands, see [Get started with Azure CLI](https://docs.microsoft.com/cli/azure/get-started-with-azure-cli?view=azure-cli-latest#sign-in). - -## Contributing - -See [the contribution guidelines](https://github.com/microsoft/vscode-docker/blob/HEAD/CONTRIBUTING.md) for ideas and guidance on how to improve the extension. Thank you! - -### Code of Conduct - -This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. - -## Telemetry - -VS Code collects usage data and sends it to Microsoft to help improve our products and services. Read our [privacy statement](https://go.microsoft.com/fwlink/?LinkID=528096&clcid=0x409) to learn more. If you don’t wish to send usage data to Microsoft, you can set the `telemetry.telemetryLevel` setting to `off`. Learn more in our [FAQ](https://code.visualstudio.com/docs/supporting/faq#_how-to-disable-telemetry-reporting). - -## License - -[MIT](https://github.com/microsoft/vscode-docker/blob/HEAD/LICENSE.md)