Manual Publishing¶
This guide covers how to manually build and publish packages to SynoCommunity without using GitHub Actions CI.
Prerequisites¶
API Key Setup¶
- Get your API key from synocommunity.com/profile
- Create or update
local.mkin the spksrc root:
PUBLISH_URL = https://api.synocommunity.com
PUBLISH_API_KEY = <your-key>
DISTRIBUTOR = SynoCommunity
DISTRIBUTOR_URL = https://synocommunity.com/
REPORT_URL = https://github.com/SynoCommunity/spksrc/issues
DEFAULT_TC = 7.1 7.2
Or generate automatically:
Building for All Architectures¶
Build all supported architectures in parallel:
Or build specific architectures:
Generic Architectures¶
These architectures generate a single package for multiple CPU models:
| Generic Arch | Covers |
|---|---|
| x64 | All Intel/AMD 64-bit |
| armv7 | 32-bit ARM Cortex |
| aarch64 | 64-bit ARM |
Publishing¶
Publish packages (one at a time, not parallel):
Or specific architectures:
Warning
Do not parallelize publishing. The spkrepo server cannot handle concurrent uploads.
Dynamic Library Linking¶
Some packages share dependencies through dynamic linking:
cd spk/chromaprint
for arch in x64 evansport 88f6281 armv7 aarch64 hi3535; do
make publish ARCH=$arch TCVERSION=7.1
done
Packages using this pattern: tvheadend, chromaprint, comskip
SRM Packages¶
SRM (Synology Router Manager) has no Package Center custom repository support.
Users must:
- Download packages manually from synocommunity.com/packages
- Install via manual upload
Build SRM packages:
After Publishing¶
See Repository Activation for steps to activate your published packages.
See Also¶
- GitHub Actions CI/CD - Automated builds and publishing
- Repository Activation - Activating published packages
- Update Policy - Supported versions and testing checklist