Update README.md
Browse files
README.md
CHANGED
|
@@ -1,3 +1,84 @@
|
|
| 1 |
---
|
| 2 |
license: agpl-3.0
|
| 3 |
---
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
---
|
| 2 |
license: agpl-3.0
|
| 3 |
---
|
| 4 |
+
|
| 5 |
+
# Apex Studio Server
|
| 6 |
+
|
| 7 |
+
This repository serves as a distribution hub for pre-bundled versions of the **Apex Studio** Python backend. The canonical version of these bundles is hosted on **[Hugging Face](https://huggingface.co/totoku/apex-studio-server/tree/main)**.
|
| 8 |
+
|
| 9 |
+
It contains compressed bundles (`.tar.zst`) optimized for different platforms, architectures, and hardware acceleration backends.
|
| 10 |
+
|
| 11 |
+
## 📦 Bundles
|
| 12 |
+
|
| 13 |
+
Apex Studio is split into two main components:
|
| 14 |
+
- **`python-api`**: A fully functional environment containing all necessary dependencies and the API service layer.
|
| 15 |
+
- **`python-code`**: The core execution engine and model implementation logic (source code only, no dependencies included).
|
| 16 |
+
|
| 17 |
+
Files are organized by version (e.g., `/0.1.0/`).
|
| 18 |
+
|
| 19 |
+
### Naming Convention
|
| 20 |
+
|
| 21 |
+
Each bundle follows this pattern:
|
| 22 |
+
`{component}-{version}-{os}-{arch}-{acceleration}-{python_version}.tar.zst`
|
| 23 |
+
|
| 24 |
+
| Segment | Options | Description |
|
| 25 |
+
| :--- | :--- | :--- |
|
| 26 |
+
| **Component** | `python-api`, `python-code` | The part of the system contained in the bundle. |
|
| 27 |
+
| **Version** | e.g., `0.1.0` | The release version of Apex Studio. |
|
| 28 |
+
| **OS** | `darwin`, `linux`, `win32` | Target Operating System. |
|
| 29 |
+
| **Arch** | `arm64`, `x86_64` | CPU Architecture (Apple Silicon vs Intel/AMD). |
|
| 30 |
+
| **Acceleration** | `mps`, `cuda`, `cpu` | Hardware backend (Metal, NVIDIA CUDA, or Generic CPU). |
|
| 31 |
+
| **Python** | `cp311`, `cp312` | Required CPython version. |
|
| 32 |
+
|
| 33 |
+
## 🚀 Usage
|
| 34 |
+
|
| 35 |
+
These bundles are compressed using **Zstandard** (`.zst`) for maximum efficiency.
|
| 36 |
+
|
| 37 |
+
### Extraction (Linux & macOS)
|
| 38 |
+
|
| 39 |
+
To extract a bundle, use `tar` with Zstandard support:
|
| 40 |
+
|
| 41 |
+
```bash
|
| 42 |
+
# Example for macOS (Apple Silicon)
|
| 43 |
+
tar --zstd -xf python-api-0.1.0-darwin-arm64-mps-cp312.tar.zst
|
| 44 |
+
```
|
| 45 |
+
|
| 46 |
+
Alternatively, if your `tar` version does not support `--zstd` directly:
|
| 47 |
+
|
| 48 |
+
```bash
|
| 49 |
+
zstd -d python-api-0.1.0-darwin-arm64-mps-cp312.tar.zst -o python-api.tar
|
| 50 |
+
tar -xf python-api.tar
|
| 51 |
+
```
|
| 52 |
+
|
| 53 |
+
### Extraction (Windows)
|
| 54 |
+
|
| 55 |
+
On Windows, you can use the following methods:
|
| 56 |
+
|
| 57 |
+
#### 1. Using 7-Zip (Recommended)
|
| 58 |
+
If you have **7-Zip** (with the Zstandard plugin) or **7-Zip-zstd** installed, you can right-click the file and extract it directly.
|
| 59 |
+
|
| 60 |
+
#### 2. Using Command Line (PowerShell/CMD)
|
| 61 |
+
If you have `zstd` and `tar` in your PATH (often available via Git Bash or Chocolatey):
|
| 62 |
+
|
| 63 |
+
```powershell
|
| 64 |
+
# Decompress the zstd file first
|
| 65 |
+
zstd -d python-api-0.1.0-win32-x86_64-cuda-cp312.tar.zst
|
| 66 |
+
|
| 67 |
+
# Then extract the resulting tar
|
| 68 |
+
tar -xf python-api-0.1.0-win32-x86_64-cuda-cp312.tar
|
| 69 |
+
```
|
| 70 |
+
|
| 71 |
+
#### 3. Using WSL
|
| 72 |
+
If you have Windows Subsystem for Linux (WSL) installed:
|
| 73 |
+
|
| 74 |
+
```bash
|
| 75 |
+
tar --zstd -xf python-api-0.1.0-win32-x86_64-cuda-cp312.tar.zst
|
| 76 |
+
```
|
| 77 |
+
|
| 78 |
+
## 🛠️ Integration
|
| 79 |
+
|
| 80 |
+
These bundles are typically fetched and managed automatically by the Apex Studio desktop application, but they can be manually deployed for headless or custom server environments.
|
| 81 |
+
|
| 82 |
+
## 📜 License
|
| 83 |
+
|
| 84 |
+
This repository and its contents are licensed under the **AGPL-3.0 License**.
|