DNP

Author: hikariatama

.gitignore

@@ -0,0 +1,4 @@
+docker-compose.yml
+.DS_Store
+.vscode/
+.env

.hintrc

@@ -0,0 +1,8 @@
+{
+  "extends": [
+    "development"
+  ],
+  "hints": {
+    "no-inline-styles": "off"
+  }
+}

ACKNOWLEDGMENTS.md

@@ -0,0 +1,20 @@
+# Acknowledgments
+
+This project incorporates several open-source libraries and tools. We would like to acknowledge and thank the contributors of these projects.
+
+## Frontend Dependencies
+
+- **Next.js** - MIT License
+- **React** - MIT License
+- **ts-chacha20** - MIT License
+- **zod** - MIT License
+- **Tailwind CSS** - MIT License
+- **Framer Motion** - MIT License
+
+## Backend Dependencies
+
+- **FastAPI** - MIT License
+- **Uvicorn** - BSD 3-Clause License 
+- **SQLAlchemy** - MIT License
+- **python-ulid** - MIT License 
+- **bcrypt** - Apache License 2.0

AUTHORS.md

@@ -0,0 +1,4 @@
+# Authors
+
+- **Daniil Gazizullin**  
+    Project maintainer and core contributor.

CHANGELOG.md

@@ -0,0 +1,8 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [v0.1.0] - 2025-30-04
+
+### Added
+- Initial release with all features

CODE_OF_CONDUCT.md

@@ -0,0 +1,134 @@
+
+# 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, caste, color, 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 email 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
+[INSERT CONTACT METHOD].
+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.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
+

CONTRIBUTING.md

@@ -0,0 +1,5 @@
+# Contributing
+
+Thank you for your interest in this project. At this time, we are not accepting contributions.
+
+If you have questions or issues, please refer to the documentation or open an issue if necessary.

CONTRIBUTORS.md

@@ -0,0 +1,4 @@
+# Contributors
+
+- **ChatGPT**, **Anthropic Claude**, **GitHub Copilot**, **Google Gemini**
+    Assisted with documentation and code suggestions.

INSTALL.md

@@ -0,0 +1,73 @@
+# INSTALL.md
+
+## 📦 Sharder Installation Guide
+
+This guide explains how to install and run the **Sharder** distributed storage platform, either via Docker (recommended) or manually. It also includes instructions for deploying individual shards.
+
+---
+
+## 🚀 Quick Start (Docker-Based Deployment)
+
+### 1. Clone the Repository
+
+```bash
+git clone https://github.com/hikariatama/sharder
+cd sharder
+```
+
+### 2. Generate Docker Compose Configuration
+
+```bash
+python3 docker-compose-generator.py \
+  --chunks-per-file 2 \
+  --replicas 3 \
+  --public-port 3333 \
+  --dev-shards 7
+```
+
+**Available options:**
+
+| Option              | Description                                          | Default |
+|---------------------|------------------------------------------------------|---------|
+| `--chunks-per-file` | Number of chunks to split each file into             | `3`     |
+| `--replicas`        | Number of redundant copies per chunk                 | `2`     |
+| `--public-port`     | Port for the public-facing API                       | `80`    |
+| `--dev-shards`      | Number of local shards to run for development        | `0`     |
+
+### 3. Launch the Stack
+
+```bash
+sudo docker compose up -d --build
+```
+
+---
+
+## ⚙️ Manual Shard Deployment
+
+To run a shard instance independently:
+
+### 1. Build the Shard Binary
+
+```bash
+mkdir /tmp/shard
+cd /tmp/shard
+wget https://sharder.dgazizullin.dev/bin/shard.tar.gz
+tar xvf shard.tar.gz
+sudo apt install build-essential libcurl4-openssl-dev
+make
+cd bin
+```
+
+### 2. Retrieve Connection URL
+
+Open the Sharder web UI, type `chimera`, and navigate to the "Management" menu to obtain your shard connection URL.
+
+### 3. Launch the Shard
+
+Use the command provided in the UI to start your shard. On first run, execute as `root`, or use the `--dry` flag to perform a test run.
+
+> ℹ️ The shard installs itself as a `systemd` service and moves to `/opt/shard` by default.
+
+---
+
+For more information, visit the [project repository](https://github.com/hikariatama/sharder).

LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2011-2025 The Bootstrap Authors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.