Statistics for Strava VS CloudLinux

• Self-hosted and privacy-focused
  The project allows users to host their own Strava statistics dashboard, keeping their data under their own control rather than relying on third-party services. All data is stored locally, which appeals to privacy-conscious athletes.
• Rich visual statistics and charts
  It generates beautiful, detailed statistics including heatmaps, activity charts, Eddington numbers, weekly/monthly/yearly overviews, and various other visualizations that go well beyond what Strava's free tier offers.
• Free and open source
  The project is completely free and open source under the MIT license, making it accessible to anyone. Users can inspect, modify, and contribute to the codebase without any subscription fees, unlike Strava Summit or other premium analytics tools.
• Automated updates via GitHub Actions
  The project leverages GitHub Actions to automatically fetch and update statistics on a schedule, meaning users don't need to maintain a running server. This makes it low-maintenance once set up.
• Deployable as a static site on GitHub Pages
  The output is a static HTML site that can be hosted for free on GitHub Pages, eliminating the need for paid hosting or complex server infrastructure. This makes it very cost-effective to run.

Possible disadvantages

• Complex initial setup
  Setting up the project requires configuring Strava API credentials, GitHub Actions, environment variables, and potentially Docker. This can be intimidating for non-technical users who just want to see their stats.
• Limited to Strava data only
  The tool only works with Strava as a data source. Users who track activities across multiple platforms (Garmin Connect, TrainingPeaks, etc.) cannot consolidate all their data into a single dashboard.
• Requires GitHub account and knowledge
  The project is tightly coupled with the GitHub ecosystem (GitHub Actions, GitHub Pages, repositories). Users need to be familiar with Git, GitHub, and basic development workflows to get it running.
• Strava API rate limits and restrictions
  The tool depends on the Strava API, which has rate limits and usage restrictions. Large activity histories may take significant time to fully import, and API changes or token expirations can break the data pipeline.
• Limited interactivity and real-time features
  Since the output is a static site rebuilt on a schedule, it lacks real-time data updates, interactive filtering, or dynamic querying capabilities that a full web application with a backend database could provide.

• Enhanced Server Stability
  CloudLinux uses its lightweight virtualization technology (LVE) to isolate each tenant on a shared hosting server, preventing any single user from consuming excessive resources and crashing the server for everyone else. This ensures consistent uptime and performance.
• Improved Security with HardenedPHP and KernelCare
  CloudLinux offers HardenedPHP, which patches old and unsupported PHP versions against known vulnerabilities, and KernelCare, which provides live kernel patching without requiring server reboots. These features significantly enhance server security posture.
• Resource Limit Management
  Administrators can set granular resource limits (CPU, memory, I/O, number of processes, etc.) per user account using LVE Manager. This makes it easy to manage shared hosting environments and ensure fair resource distribution among tenants.
• CageFS File System Virtualization
  CageFS creates a virtualized file system for each user, preventing them from seeing other users on the server, viewing sensitive configuration files, or exploiting server vulnerabilities. This adds an important layer of isolation and security.
• Wide Compatibility with Hosting Panels
  CloudLinux integrates seamlessly with popular hosting control panels such as cPanel, Plesk, and DirectAdmin, making it straightforward for hosting providers to adopt without overhauling their existing infrastructure or workflows.

Possible disadvantages

• Additional Licensing Cost
  CloudLinux requires a paid monthly or annual license on top of the base server cost. For smaller hosting providers or individual server owners, this additional expense can add up and may not always be justifiable compared to free alternatives.
• Limited to CentOS/RHEL-Based Systems
  CloudLinux is built on top of RHEL/CentOS and does not support other Linux distributions like Ubuntu or Debian. This limits its adoption for hosting providers who prefer or already run non-RHEL-based environments.
• Learning Curve for Configuration
  While CloudLinux provides powerful resource management tools, properly configuring LVE limits, CageFS, PHP Selector, and other features requires a solid understanding of the platform. Misconfiguration can lead to users being unnecessarily restricted or resources being poorly allocated.
• Potential Performance Overhead
  The additional layers of virtualization, resource monitoring, and file system isolation introduced by CloudLinux can impose a slight performance overhead on the server compared to running a bare, unmodified Linux distribution without these controls.
• Dependency on CloudLinux Ecosystem
  Adopting CloudLinux means relying on their ecosystem for kernel updates, PHP patches, and security fixes. If the company experiences delays in releasing patches or changes its pricing/licensing model, hosting providers may find themselves locked into a dependency that is difficult to migrate away from.

No Statistics for Strava videos yet. You could help us improve this page by suggesting one.

When To Use Cloudlinux On Your Virtual Private Server (VPS)

More videos