76 lines
2.8 KiB
Markdown
76 lines
2.8 KiB
Markdown
---
|
||
sidebar_position: 3
|
||
---
|
||
|
||
# VDC Blueprints & Example Environments
|
||
|
||
This section presents opinionated "blueprints" you can use as starting points for your own Virtual Data Centers.
|
||
|
||
## Digital Me – Personal Sovereign Cloud Workspace
|
||
|
||
Adapted from the **Cloud Blueprint** on the main Mycelium site, *Digital Me* is a personal cloud environment showcasing what’s possible on top of the Mycelium Stack.
|
||
|
||
### Goal
|
||
|
||
Provide a private, extensible workspace where:
|
||
|
||
- Your documents, files, and communication tools live on infrastructure you choose.
|
||
- You can integrate additional services or agents over time.
|
||
- Everything is reachable securely via Mycelium Network.
|
||
|
||
### Core Components
|
||
|
||
A typical Digital Me blueprint might include:
|
||
|
||
- **Cryptpad** – End‑to‑end encrypted document collaboration.
|
||
- **Gitea** – Git hosting, code review, and lightweight DevOps.
|
||
- **Nextcloud** – File storage, sync, and basic productivity apps.
|
||
- **Matrix (Elements)** – Real‑time chat and rooms.
|
||
- **Stallwart** – Mail, calendar, and contacts.
|
||
- **Video Conferencing** – LiveKit or Jitsi, optionally integrated with Matrix or Nextcloud.
|
||
- **SSO / Identity** – A unifying login layer (future iteration).
|
||
|
||
Each service runs as one or more Kubernetes workloads inside your VDC.
|
||
|
||
### How It Fits Together
|
||
|
||
```mermaid
|
||
graph TD
|
||
A[Mycelium Network] --> B[VDC (K3s Cluster)]
|
||
B --> C[Apps: Cryptpad, Gitea, Nextcloud, Matrix, Stallwart, Video]
|
||
C --> D[Your Devices]
|
||
|
||
D -. secure overlay .- A
|
||
```
|
||
|
||
- Your devices connect via Mycelium Network.
|
||
- Services are exposed only via overlay addresses or controlled gateways.
|
||
- Data can be stored on QSFS or other resilient storage options.
|
||
|
||
### Customizing the Blueprint
|
||
|
||
You can adapt Digital Me by:
|
||
|
||
- Swapping apps (e.g. another Git forge instead of Gitea).
|
||
- Adding specialized tools (design collaboration, analytics, etc.).
|
||
- Scaling vertically (larger nodes) or horizontally (more nodes) as usage grows.
|
||
- Integrating Mycelium Agents in the future to automate workflows.
|
||
|
||
## Other Blueprint Ideas
|
||
|
||
The same VDC primitives can be used for many patterns:
|
||
|
||
- **Team Collaboration Hub** – Shared docs, code, chat, CI/CD for a startup or studio.
|
||
- **Research Environment** – Compute + storage for data science, notebooks, and pipelines.
|
||
- **Edge Application Stack** – Regional VDCs running local services that sync to a core.
|
||
|
||
Blueprints are not prescriptive; they’re **starting points** that help you think in terms of composable services.
|
||
|
||
---
|
||
|
||
## Next Steps
|
||
|
||
- Learn more about **VDC capabilities** in the **[VDC Overview](/vdc)**.
|
||
- Explore concrete **[VDC Use Cases](/vdc/use-cases)**.
|
||
- When you’re ready to deploy, follow the **[Mycelium Cloud Getting Started guide](/cloud/getting-started)** to spin up your first cluster.
|