From 272c2cf06fee8f9196931942020c0b5725f7df6c Mon Sep 17 00:00:00 2001
From: Artem Grinev <agrinev98@gmail.com>
Date: Fri, 24 May 2024 14:48:37 +0400
Subject: [PATCH 1/2] docs: add guide for changing repos in pacman

---
 docs/ConfiguringRepos.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 docs/ConfiguringRepos.md

diff --git a/docs/ConfiguringRepos.md b/docs/ConfiguringRepos.md
new file mode 100644
index 00000000..336de65e
--- /dev/null
+++ b/docs/ConfiguringRepos.md
@@ -0,0 +1,27 @@
+For testing purposes the pacman repository can be changed to ones managed by bxt by the following steps:
+
+1. Backup current pacman.conf file:
+   ```bash
+   sudo cp /etc/pacman.conf /etc/pacman.conf.bak
+   ```
+   
+2. Edit pacman configuration to point to the bxt-managed repo:
+   ```ini
+   [core]
+   SigLevel = PackageRequired
+   Server = https://<bxt-server-name>/box/unstable/core/x86_64/
+
+   [extra]
+   SigLevel = PackageRequired
+   Server = https://<bxt-server-name>/box/unstable/extra/x86_64/
+
+   [community]
+   SigLevel = PackageRequired
+   Server = https://<bxt-server-name>/box/unstable/community/x86_64/
+    
+   [multilib]
+   SigLevel = PackageRequired
+   Server = https://<bxt-server-name>/box/unstable/multilib/x86_64/
+   ```
+
+This will prevent pacman from using the mirrorlist in favor of bxt.

From f7f1a3ae46a34ac87a8b4672b7faaa979ab6a8dd Mon Sep 17 00:00:00 2001
From: Artem Grinev <agrinev@manjaro.org>
Date: Fri, 24 May 2024 17:52:34 +0000
Subject: [PATCH 2/2] docs: add brief architecture outline

---
 docs/development/ARCHITECTURE.md | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 docs/development/ARCHITECTURE.md

diff --git a/docs/development/ARCHITECTURE.md b/docs/development/ARCHITECTURE.md
new file mode 100644
index 00000000..bdd6b8ed
--- /dev/null
+++ b/docs/development/ARCHITECTURE.md
@@ -0,0 +1,28 @@
+<div align="center">
+    <img src="../../frontend/public/logo-full.png" alt="drawing" width="200"/>
+</div>
+
+#
+
+<div align="center">
+Architecture outline
+</div>
+
+## Introduction
+
+This is an overview of the b[x] architecture for daemon components. This should make it easier for contributors to understand the specifics of this project's layout and design.
+
+## Core Components
+
+C++ daemon is developed with Domain-Driven Design principles in mind and split into 3 layers:
+
+- **Domain layer**:
+  - `core/domain` - business logic (entities, value objects, repositories)
+- **Application layer**:
+  - `core/application` - application layer that is used to orchestrate the business logic (DTOs, Services)
+- **Infrastructure layer**:
+  - `persistence` - persistence logic implementation (databases, configuration)
+  - `infrastructure` - infrastructure logic implementation (application layer implementations, networking, events, notifications)
+  - `presentation` - presentation logic (http-controllers, filters, messages)
+
+The code also contains `utilities` directory. It's for various cross-cutting concerns or third-party libraries bindings.