SYSTEM INITIALIZATION
Build and run Crono Desktop from source code
STANDARD INSTALLATION PROCESS
Extract the provided source code archive to your development directory. You'll receive all source files but no built executables.
This verifies your build environment and provides specific setup commands for your platform.
Follow the platform-specific commands shown by the diagnostic tool. This typically includes:
This installs all required Node.js dependencies and compiles native modules.
This launches the application in development mode to verify everything is working.
This creates executable files for all platforms in the dist/ folder.
SYSTEM REQUIREMENTS
These are the standard requirements for building from source:
- Node.js: Version 18.0.0 or higher
- npm: Version 8.0.0 or higher
- Python: Version 3.x with setuptools (automatically checked)
- Build Tools: Platform-specific compilers (automatically checked)
npm run diagnose to automatically check your system and get the exact setup commands for your platform.
PLATFORM-SPECIFIC SETUP
macOS Setup
Windows Setup
Install Visual Studio Build Tools or Visual Studio Community with C++ workload
Linux Setup
VERIFICATION COMMANDS
Use these commands to verify your installation:
FIRST RUN
Once built and launched, Crono will automatically:
- Create the database directory structure
- Initialize the SQLite database
- Set up default categories (Documents, Images, Videos, etc.)
- Create the files storage directory
~/.crono/ (or your custom directory name if rebranded). This includes the database file and all copied files.
TESTING THE APPLICATION
Use the green "UPLOAD DATA" button in the top-right corner of the interface.
Click "SCAN" to browse and select a file, or drag and drop it directly onto the interface.
Enter a description and assign data types (categories) to help organize and find your file later.
Click "EXECUTE UPLOAD" to test the file archiving functionality.
SECURITY CONSIDERATIONS
Crono Desktop prioritizes your data security:
- Local Storage: All files remain on your local machine
- No Network Access: Crono doesn't send data to external servers
- Encrypted Exports: Backup archives are password-protected
- File Permissions: Uses standard operating system file permissions
QUICK START TIPS
NEXT STEPS
Now that you have Crono Desktop building and running, explore these areas:
- Developer Guide: Customize, rebrand, and modify the application
- Features: Understand all capabilities for potential customization
- User Guide: Learn the interface to better customize it
- System Requirements: Optimize builds for your target platforms
STANDARD BUILD PROCESS
The standard workflow for any changes or fresh installs:
- Environment check:
npm run diagnose - Install/update:
npm install - Test changes:
npm run dev - Build release:
npm run build-all
npm run diagnose first to check your build environment. This saves time by catching setup issues early. Test the application thoroughly in development mode before building for production.