🧩 Architecture & Core Logic
- Super Powers
- Joomla Powers
- Compile Native Components, Plugins & Modules
- Multi-Version Support
- Conditional Logic Injection
- Reusable Admin Views
- Dynamic GET Builder
- Round-Trip Code Integration
- Custom Admin Views
- Site Views
- Dynamic Dashboards
- Model Linking Between Views
- Shared Field Reuse Across Views
- Drag & Drop Field Mapping
- Dynamic Field Visibility
- Independent Packaging
🧱 Custom Code System (Powerful Dual Feature)
🛠 Field Type System
📁 Snippets, Templates, Layouts, Libraries
- Snippets Reusable Html Blocks
- Layouts Reusable Php Render Templates
- Templates Page Level Views Linked To Custom Admin Site Views
- Libraries JS CSS Assets Linked To UI
- CDN Local Toggle For Library Delivery
- Media Folder Injection With Override Support
- Repository Push Pull Reset Workflow
- Init Snippets Layouts Templates Via Gui
📦 Packages
🧩 Architecture & Core Logic
📁 File & Code Management
🧠 Code Reuse & Blueprints
🌐 Joomla CMS Integration
🎨 Visual GUI & UX
🌍 Internationalization
📦 Packaging & Distribution
⚙️ Compiler Engine Features
🧱 Custom Code System
🛠 Field Type System
📐 Dynamic GET (Visual SQL Engine)
📁 Snippets, Templates, Layouts, Libraries
📚 Documentation & Metadata
📊 Analytics & Insights
🧩 Architecture & Core Logic
- Super Powers
- Joomla Powers
- Compile Native Components, Plugins & Modules
- Multi-Version Support
- Conditional Logic Injection
- Reusable Admin Views
- Dynamic GET Builder
- Round-Trip Code Integration
- Custom Admin Views
- Site Views
- Dynamic Dashboards
- Model Linking Between Views
- Shared Field Reuse Across Views
- Drag & Drop Field Mapping
- Dynamic Field Visibility
- Independent Packaging
🛠 Field Type System
- Field Types Define Templates And Data Types
- Gui Defined Rules Required Unique Nullable
- Save Get Hooks Per Field
- Database Schema Auto Generated From Field Settings
- Per Display Field Rendering Config List Edit
- Create Dynamic Models With Modals Selectors
- Conditional Js And Css Per Field
📁 Snippets, Templates, Layouts, Libraries
- Snippets Reusable Html Blocks
- Layouts Reusable Php Render Templates
- Templates Page Level Views Linked To Custom Admin Site Views
- Libraries JS CSS Assets Linked To UI
- CDN Local Toggle For Library Delivery
- Media Folder Injection With Override Support
- Repository Push Pull Reset Workflow
- Init Snippets Layouts Templates Via Gui
Remote Publishing to Custom Repo Update Streams
Streamline the distribution of your Joomla components by automatically publishing builds to a remote Git repository or update server.
What Is Remote Publishing?
Remote publishing in Joomla Component Builder (JCB) allows you to push compiled builds (ZIP packages, update XML, changelogs, and more) to an external repository or server of your choice, including:
- Git repositories (e.g., Gitea, GitHub, GitLab)
- Update servers hosted via a web domain
- Custom API endpoints for CI/CD pipelines
These update streams can then be consumed by:
- Joomla’s built-in Extension Update system
- External installers or provisioning tools
- Team collaborators managing package versions
Key Capabilities
- 🧾 Auto-Push Build Artifacts
Compiled .zip files, changelogs, and XML update manifests are automatically pushed to a defined remote path or repository branch. - 🛠 Git-Aware
Pushed based on build versions and tags—supporting per-branch deployment (e.g., 3.x-dev, 4.x-stable, etc.). - 🔄 Tag-Based Versioning
JCB can auto-generate semantic version tags based on blueprint metadata and commit history. - 🖇 Component Update XML Generator
Dynamically builds Joomla-compatible update server XML per component—based on release files in the remote repo. - 🔐 Secure Push via API Tokens
Remote publishing supports authenticated endpoints using API keys or tokens, ensuring secure access to your Git or HTTP server. - 🗃️ Multi-Stream Publishing
Publish to multiple destinations based on component, build status (nightly/stable), or target Joomla version.
Typical Use Cases
- Publish nightly or stable builds to GitHub or Gitea
- Push to a private update server for licensed client installations
- Automate delivery to a release management system
- Manage internal builds between developer teams
How to Configure in JCB
- Open the desired Component.
- Enable Component updates.
- Define:
- Target Git URL or server endpoint
- Authentication token or credentials
- Branch or folder path
- File types to push (zip, XML, changelog, etc.)
- Set the triggering behavior:
- Manual trigger
- On successful build
- On tag push
- Optional: Add a version-based filter (e.g., skip nightly).
- JCB takes care of packaging, versioning, and pushing the correct artifacts to the remote destination after compilation.
Update Stream Integration
JCB can auto-generate the required update server XML file that Joomla uses to check for extension updates.
This means your users can:
- Install your component once
- Receive updates directly via Joomla’s Extension Manager
- Automatically receive changelogs and version history
This allows you to offer stable, semi-automated delivery of new releases to production sites, beta testers, or internal clients.
Benefits
- ✅ Automates repetitive release steps
- ✅ Great for versioned component distribution
- ✅ Keeps Git and Joomla update servers in sync
- ✅ Helps power nightly/stable build workflows
- ✅ Minimizes manual packaging errors
- ✅ Great for licensed or enterprise scenarios
Bonus: Link with Build ID System
Combine remote publishing with JCB’s build ID assignment system for traceable builds, rollback-friendly releases, and metadata-rich component delivery.