The documentation had inconsistent command names. The npm package provides a binary called synchronizer (without 'r'), but documentation was showing synchronizer-cli (with 'r').
- Fixed all command examples from
synchronizer-clitosynchronizer - Commands affected:
synchronizer initsynchronizer startsynchronizer servicesynchronizer statussynchronizer websynchronizer install-dockersynchronizer fix-dockersynchronizer test-platformsynchronizer service-websynchronizer pointssynchronizer set-passwordsynchronizer --helpsynchronizer --version
- Fixed the web service generation command from
synchronizer-cli webtosynchronizer web - Line fixed:
ExecStart=${npxPath} synchronizer web
- Changed license from MIT to Apache-2.0 in both package.json files
- Updated license badges in README files
- Added LICENSE file to synchronizer-cli directory
- Updated license references in documentation
- synchronizer-cli: 1.10.1 → 1.10.3
- synchronizer-repo: 1.6.0 → 1.6.2
These references correctly remain as synchronizer-cli:
- Package name:
synchronizer-cli - npm install command:
npm install -g synchronizer-cli - Docker image:
cdrakep/synqchronizer:latest - Service names:
synchronizer.service,synchronizer-web.service - Config directory:
~/.synchronizer-cli/ - Container name:
synchronizer - GitHub URLs and references
After publishing, users should be able to:
npm install -g synchronizer-cli
synchronizer --help
synchronizer init
synchronizer startThe binary provided by the package.json bin field is synchronizer (without 'r'), so all command examples must use this form.
Both packages now use Apache-2.0 license consistently across:
- package.json files
- README badges and documentation
- LICENSE files in both directories