feat: mongo srv

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+contact@soluce-technologies.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

.github/CONTRIBUTING.md

@@ -0,0 +1,261 @@
+---
+
+# Contributing to Portabase
+
+Thank you for considering contributing to **Portabase!** 🎉 Contributions help make this project better for everyone.
+
+Please take a moment to review this guide. It will help you understand how to contribute effectively.
+
+---
+
+## Table of Contents
+
+1. [How to Get Started](#how-to-get-started)
+2. [Running the CLI (Development)](#running-the-cli-development)
+3. [Reporting Issues](#reporting-issues)
+4. [Submitting Changes](#submitting-changes)
+5. [Code Style Guidelines](#code-style-guidelines)
+6. [Pull Request Process](#pull-request-process)
+7. [Community Guidelines](#community-guidelines)
+
+---
+
+## How to Get Started
+
+1. **Fork the repository**  
+   Click the "Fork" button at the top-right corner of this repository.
+
+2. **Clone the repository**
+   ```bash
+   git clone https://github.com/Portabase/cli.git
+   ```
+
+3. **Set up the development environment**  
+   Follow the steps in the `README.md` to install dependencies and configure the project.
+
+4. **Create a branch**  
+   Use the feature branch to work on changes.
+   ```bash
+   git checkout -b feature/<feature-name>
+   ```
+
+---
+
+## Running the CLI (Development)
+
+The project is a [Typer](https://typer.tiangolo.com/) CLI managed with
+[uv](https://docs.astral.sh/uv/). The entry point is `main.py`.
+
+### Set up the environment
+
+Install [uv](https://docs.astral.sh/uv/getting-started/installation/), then sync
+the dependencies (creates `.venv` and installs everything from `uv.lock`):
+
+```bash
+uv sync
+```
+
+### Run any command from source
+
+While developing, run the CLI through `uv run` instead of the installed
+`portabase` binary. The pattern is:
+
+```bash
+uv run python main.py <command> [ARGS] [OPTIONS]
+```
+
+Anything after `main.py` is a normal CLI invocation, so `portabase <command>`
+(once built/installed) and `uv run python main.py <command>` are equivalent.
+
+Show the top-level help and version:
+
+```bash
+uv run python main.py --help
+uv run python main.py --version
+```
+
+> Tip: append `--help` to any command to see its arguments, e.g.
+> `uv run python main.py agent --help`.
+
+### Creation commands
+
+Create an agent (interactive; flags pre-fill the prompts):
+
+```bash
+# name is required (creates a folder); everything else is optional
+uv run python main.py agent my-agent
+uv run python main.py agent my-agent --key <EDGE_KEY> --tz Europe/Paris --polling 10 --start
+```
+
+| Arg / Option | Default | Description |
+| --- | --- | --- |
+| `name` (arg) | — | Agent name; creates a folder of that name. |
+| `--key`, `-k` | prompt | Edge Key (Base64 or JSON). Prompted if omitted. |
+| `--tz` | `UTC` | Timezone. |
+| `--polling` | `5` | Polling frequency in seconds. |
+| `--start`, `-s` | off | Start the agent immediately after setup. |
+
+Create a dashboard:
+
+```bash
+uv run python main.py dashboard my-dashboard
+uv run python main.py dashboard my-dashboard --port 9000 --start
+```
+
+| Arg / Option | Default | Description |
+| --- | --- | --- |
+| `name` (arg) | — | Dashboard name; creates a folder of that name. |
+| `--port` | `8887` | Web port. |
+| `--start`, `-s` | off | Start the dashboard immediately after setup. |
+
+### Lifecycle commands
+
+Each takes the path to a component folder (the one created above):
+
+```bash
+uv run python main.py start my-agent
+uv run python main.py stop my-agent
+uv run python main.py restart my-agent
+uv run python main.py logs my-agent            # follows by default
+uv run python main.py logs my-agent --no-follow
+uv run python main.py uninstall my-agent       # prompts for confirmation
+uv run python main.py uninstall my-agent --force
+```
+
+| Command | Arg / Option | Description |
+| --- | --- | --- |
+| `start` / `stop` / `restart` | `path` (arg) | Path to the component folder. |
+| `logs` | `path` (arg), `--follow/--no-follow`, `-f` | Stream logs; follows unless `--no-follow`. |
+| `uninstall` | `path` (arg), `--force`, `-f` | Remove containers and data; `--force` skips the prompt. |
+
+### Configuration commands
+
+Decrypt Portabase `.enc` backup files (single file or a folder of `.enc` files):
+
+```bash
+# single file -> explicit output
+uv run python main.py decrypt backup.tar.gz.enc backup.tar.gz --key master_key.bin
+# folder -> decrypt every .enc into an output folder
+uv run python main.py decrypt ./backups ./restored --key master_key.bin
+# omit output to write next to the input; omit --key to use ./master_key.bin
+uv run python main.py decrypt backup.tar.gz.enc
+```
+
+| Arg / Option | Default | Description |
+| --- | --- | --- |
+| `input_path` (arg) | — | A `.enc` file, or a folder containing `.enc` files. |
+| `output_path` (arg) | input's directory | Output file or folder (must match the input type). |
+| `--key`, `-k` | `./master_key.bin` | Path to the master key file (raw 32-byte or Base64 AES-256 key). |
+
+Manage the configured databases of an agent:
+
+```bash
+uv run python main.py db list my-agent
+uv run python main.py db add my-agent
+uv run python main.py db remove my-agent
+```
+
+Manage global CLI configuration:
+
+```bash
+uv run python main.py config show
+uv run python main.py config channel stable   # or: beta
+```
+
+### System commands
+
+```bash
+uv run python main.py update
+```
+
+### Running the tests
+
+Unit tests live in `tests/`, mirroring `core/`, `services/` and `engines/`. They call
+the functions directly: no Docker, no network, no built binary.
+
+```bash
+uv run pytest
+uv run ruff check . && uv run ruff format --check . && uv run mypy
+```
+---
+
+## Reporting Issues
+
+If you encounter a bug or have a suggestion for improvement, follow these steps:
+
+1. **Check existing issues** to avoid duplicates.
+2. **Open a new issue** if needed:
+    - Provide a clear and descriptive title.
+    - Describe the issue with steps to reproduce it (if applicable).
+    - Include relevant logs, screenshots, or code snippets.
+
+---
+
+## Submitting Changes
+
+1. **Ensure your branch is up to date**
+   ```bash
+   git pull origin main
+   ```
+
+2. **Write meaningful commit messages**  
+   Follow this format:
+   ```
+   [type] Summary of changes
+   ```
+   Example:
+   ```
+   feat: add user authentication
+   fix: resolve crash on login page
+   ```
+
+3. **Push your branch**
+   ```bash
+   git push origin feature/<feature-name>
+   ```
+
+4. **Open a Pull Request (PR)**  
+   Go to the repository on GitHub and click "New Pull Request."
+
+---
+
+## Code Style Guidelines
+
+- Follow the [specific coding style guide] (e.g., Prettier, ESLint, PEP8).
+- Use meaningful variable names and include comments where necessary.
+- Tests before submitting your changes.
+
+---
+
+## Pull Request Process
+
+1. Ensure your code passes all tests and linters.
+2. Provide a clear description of what your PR does.
+3. Reference any related issues (e.g., `Closes #123`).
+4. Wait for a review from a maintainer.
+
+---
+
+## Community Guidelines
+
+- Be respectful and inclusive to all contributors.
+- Follow the [Code of Conduct](CODE_OF_CONDUCT.md).
+- Feel free to ask questions if you’re unsure about something.
+
+---
+
+Thank you for contributing! 🙌
+
+---
+## Releasing
+
+Releases are cut from GitHub Actions, never from a local machine.
+
+1. Open **Actions → Bump version → Run workflow**.
+2. Pick the branch (`main` for stable, any branch for a release candidate).
+3. Enter the version without a leading `v` (`26.09.0` for stable, `26.09.0rc1` for a candidate) and the matching channel.
+4. The workflow commits `chore(release): <version>`, creates the tag and pushes. The tag triggers the build, the GitHub release and the Discord notification.
+
+Stable versions must match `X.Y.Z` and can only be cut from `main`.
+
+The workflow pushes with a token minted from the Portabase GitHub App (`APP_ID` repository variable, `APP_PRIVATE_KEY` secret), scoped to *Contents: write*. The app must be installed on this repository and allowed to push to `main`. A tag pushed with the default `GITHUB_TOKEN` would not trigger the release workflows.