Home
Projects
Download
Support
Sponsors
Sponsor Benefits
Buy Gifts
Donate Now
Join Us
Open Cooperation
Contribute
Contributors (26)
Events (1)
Academy
Outsourcing
Contact Us
Outsourcing
Open Cooperation
Sponsor
Others
Recruitment
Ask Us
Chat With Us
About Us
Back to project ezyplatform

Make EzyPlatform Your Own

Updated at 1789744070000
EzyPlatform can be customized to use your own plugin marketplaces, logo, copyright notice, and contact page. Once configured, the administration interface retains all EzyPlatform features while adopting your organization's branding and module distribution ecosystem.

Configure marketplaces

EzyPlatform supports a primary marketplace and multiple additional marketplaces through two properties in the admin config.properties file:
market.url=https://market.example.com
market.urls=https://market-partner-a.example.com,https://market-partner-b.example.com
Where:
  • market.url is your primary marketplace. When specified, this URL appears first in the marketplace list.
  • market.urls is a comma-separated list of additional marketplaces.
  • Whitespace and trailing / characters are normalized automatically.
  • Duplicate URLs appear only once.
  • The official marketplace at https://ezyplatform.com is always appended to the list if it is not already present.
If you only want to add secondary marketplaces without defining your own primary marketplace, leave market.url empty: 
market.url=
market.urls=https://market-a.example.com,https://market-b.example.com
Restart the admin service after changing these properties so the marketplace list is reloaded.
> Only add marketplaces that you trust. EzyPlatform treats the configured list as an allowlist. A URL submitted by the browser that is not in this list will not be used, and the system will fall back to the official marketplace.

How EzyPlatform works with multiple marketplaces

When a module screen needs to find a plugin or check its version, the admin service queries the configured marketplaces in order. The result retains the marketplace that supplied each module, ensuring that subsequent actions—such as viewing details, loading images, purchasing, or installing—continue to use the correct source marketplace.
flowchart TD
    A[Administrator opens the module list] --> B[Admin loads the configured marketplace list]
    B --> C[Organization's primary marketplace]
    B --> D[Partner marketplace A]
    B --> E[Partner marketplace B]
    B --> F[Official EzyPlatform marketplace]
    C --> G[Aggregate modules and retain their source marketplaces]
    D --> G
    E --> G
    F --> G
    G --> H{Administrator selects a module}
    H --> I[Load details and images from the correct source]
    H --> J[Purchase or install from the correct source]
    J --> K[Check versions and dependencies]
    K --> L[Install the module on EzyPlatform]
The declaration order matters: market.url takes precedence, followed by the addresses in market.urls, and finally the official marketplace. Therefore, place your internal or branded marketplace first.

Change the logo, copyright notice, and contact URL

The most convenient approach is to open the Settings page in the admin interface and create the following three TEXT settings:
Setting nameExample valueDisplay location
admin_ezyplatform_log_urlhttps://cdn.example.com/brand/logo.pngLogo in the admin sidebar
admin_ezyplatform_copyrightCopyright &copy; 2026 <a href="https://example.com">Example Corp</a>.Admin footer
admin_ezyplatform_contact_urlhttps://example.com/contactContact link in the navigation bar
The name admin_ezyplatform_log_url matches the key used by the current EzyPlatform version. Enter log_url exactly as shown. Changing it to logo_url will prevent the interface from finding the value.
The copyright value is rendered as HTML, so it can contain links or simple formatting. Only allow trusted administrators to edit this setting, and never insert scripts or HTML supplied by users.
The logo can use an absolute CDN URL or a resource path accessible to the admin interface. A square or nearly square image with a transparent background is recommended so that it displays clearly in the sidebar.

Configure branding through the configuration file

You can also define default values in the admin config.properties file:
ezyplatform.logo_url=https://cdn.example.com/brand/logo.png
ezyplatform.copyright=Copyright © 2026 Example Corp.
ezyplatform.contact_url=https://example.com/contact
The properties in this file act as defaults. If the corresponding setting already exists in the database, the value from Settings takes precedence. This mechanism is useful when you want to:
  • package default branding for new deployments;
  • manage baseline configuration through deployment tools;
  • allow each installation to customize its branding later through the Settings interface.
Restart the admin service after modifying the configuration file. When changing values directly through Settings, reload the page to verify the result.

Fallback values

When no custom branding values are configured, the admin interface uses the defaults:
  • the default EzyPlatform logo;
  • the Young Monkeys copyright notice;
  • a contact link pointing to EzyPlatform's `/contact-us` page.
To restore the default interface, remove the custom settings and delete the corresponding properties from the configuration file.

Branding checklist

  • Configure market.url for your organization's primary marketplace.
  • Add partner marketplaces to market.urls in the intended priority order.
  • Use HTTPS for every marketplace and branding resource in production.
  • Create admin_ezyplatform_log_url, admin_ezyplatform_copyright, and admin_ezyplatform_contact_url in Settings.
  • Restart the admin service after changing config.properties.
  • Verify the logo, footer, Contact link, and the module discovery and installation flow for every marketplace.
With these settings in place, you can run EzyPlatform under your own brand, prioritize your module repository, and retain access to the official EzyPlatform ecosystem.

Table Of Contents