♛MEGASOFTSOFTWARE & MODULES
INSTALLATION & INFRASTRUCTURE

Know what your platform needs.

MEGALOAD separates the public application, database and storage roles. Plan the environment before purchasing installation services.

Compatibility is confirmed before installation.

The project history does not establish a universal minimum CPU / RAM / disk specification or a complete version compatibility matrix. We size and validate your chosen environment against the delivery build.

01 / WINDOWS APPLICATION

The main application server

The website, accounts, administration, package rules and API handlers run in the central application.

  • Windows Server with IIS and ASP.NET Web Forms / .NET Framework support matching the supplied build.
  • C# application files, correct IIS application-pool configuration and required filesystem permissions.
  • A domain or subdomain for the application, DNS access and a valid HTTPS certificate.
  • Outbound connectivity to SQL Server, configured storage endpoints, email service and selected payment-provider APIs.
  • SMTP settings for account and transactional email. Provider credentials must be supplied securely.

Exact Windows, .NET and IIS versions are checked during pre-installation review. The platform is not a PHP / MySQL script.

02 / SQL SERVER

The database role

  • Microsoft SQL Server compatible with the delivered schema, procedures and query features.
  • A dedicated database and application connection configuration.
  • Database access restricted to required application and administration hosts.
  • Permissions sufficient for the agreed installation / migration process, followed by operational permissions.
  • Scheduled backups, restore verification and capacity monitoring.

Database hosting, licences and backup storage are separate from the software estimate unless explicitly included in the quotation.

03 / LINUX STORAGE

Each additional file server

File servers store and deliver the actual file bytes. Adding hardware also requires deploying and binding a storage agent to the central service.

  • A compatible Linux environment; AlmaLinux is represented in the deployment history. Other distributions require validation.
  • Python runtime and dependencies matched to the supplied agent, with systemd service management.
  • Supported web-serving / TLS configuration for the delivered storage agent stack.
  • Provisioned storage disks, persistent mount points, correct ownership and read / write permissions.
  • Storage endpoint DNS / HTTPS configuration and permitted connectivity to the central Agent API.
  • Unique node registration, securely provisioned agent credentials and correct node-to-storage-path binding.
  • Required workers for upload processing, jobs and deletion; migration, antivirus and torrent workers where included.
  • ClamAV and quarantine setup if the antivirus module is selected; aria2 / tracker dependencies where required by the agreed torrent workflow.

Archive-only nodes may have different roles and may not accept uploads. Roles must be configured explicitly.

04 / CONNECTIONS & OPERATIONS

DNS, HTTPS, firewall and monitoring

  • Public HTTPS access to the website and the selected storage endpoints, with reliable certificate renewal.
  • Required outbound application / agent communication. A precise firewall rule list is supplied for the chosen topology; do not expose SQL Server publicly.
  • Accurate time synchronisation for signed tickets, expiry and job scheduling.
  • Adequate bandwidth, disk throughput and disk space for uploads, downloads, temporary processing and retained trash.
  • Service restart policies, worker logs, error monitoring and disk-capacity alerts.
  • Backups for configuration and database; file backup / replicas according to the agreed recovery policy.
05 / PROFESSIONAL INSTALLATION

From server review to handover

  1. Discovery: confirm modules, domains, versions, storage paths, credentials and expected workload.
  2. Application deployment: install files, configure IIS, database connection and public settings.
  3. Storage registration: install agents, bind nodes and configure the included workers.
  4. Business configuration: set operator-defined plans, access policies, email and selected payment integration.
  5. Acceptance: verify upload, download, access enforcement, email and applicable module workflows.
  6. Handover: document the topology, operational checks, update process and agreed support scope.

Installation means software deployment within the written scope. It does not include purchasing servers, ongoing hosting, third-party licences or unlimited custom development.

06 / PLAN FOR GROWTH

Capacity and extra servers

There is no single hardware size suitable for every service. Concurrent transfers, file sizes, storage growth, processing modules, retention and bandwidth all affect capacity.

  • Provide expected simultaneous uploads / downloads and target transfer speeds.
  • Estimate stored data, monthly growth and how long deleted files remain retained.
  • Allow space and processing resources for previews, archive tasks, antivirus and replicas.
  • Define whether additional nodes accept uploads, serve downloads or perform archive work.
  • Validate routing, job claiming and deletion on each new node before accepting traffic.
Configure installation & nodes →