PHPackages swissup/module-upward-connector - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [HTTP & Networking](/categories/http) 4. / 5. swissup/module-upward-connector ActiveMagento2-module[HTTP & Networking](/categories/http) swissup/module-upward-connector =============================== Magento module used for routing all frontend requests through UPWARD-PHP. Wrapper for magento/module-upward-connector 1.1.4(2y ago)214.0k—8.3%OSL-3.0PHPPHP ~8.1.0||~8.2.0||~8.3.0 Since May 18Pushed 2y ago5 watchersCompare [ Source](https://github.com/swissup/module-upward-connector)[ Packagist](https://packagist.org/packages/swissup/module-upward-connector)[ RSS](/packages/swissup-module-upward-connector/feed)WikiDiscussions master Synced 1mo ago READMEChangelogDependencies (14)Versions (7)Used By (0) Swissup 2 UPWARD connector module ================================= [](#swissup-2-upward-connector-module) The Swissup 2 UPWARD connector extends and fix some functionatity of Magento 2 UPWARD connector. The Magento 2 UPWARD connector is a module for routing requests to UPWARD-PHP. This module replaces the default Magento frontend theme with a PWA Studio storefront application. PWA Studio storefront deployments in the Magento Commerce use this module to keep Magento and storefront code on the same server. ### Contents [](#contents) 1. [Installation](#installation) 2. [Configuration](#configuration) ### Installation [](#installation) ``` cd composer config minimum-stability dev composer config prefer-stable true composer require swissup/module-upward-connector composer config minimum-stability stable bin/magento module:enable $(bin/magento module:status --disabled | grep 'Swissup_Core\|Pwa\|Aux\|Upward' | tr '\r\n' ' ') bin/magento setup:upgrade bin/magento setup:di:compile bin/magento setup:static-content:deploy bin/magento cache:clean ``` ### Configuration [](#configuration) The Magento 2 UPWARD connector has additional settings that can be configured in the admin area under: Stores > Configuration > General > Web > UPWARD PWA Configuration. #### UPWARD Config File [](#upward-config-file) This configuration is the location of the UPWARD configuration file for the UPWARD-PHP server. This module adds a new directive to the env.php to securely set the path to the upward.yaml file. ``` // ... 'downloadable_domains' => [ // ... ], # New configuration point 'pwa_path' => [ 'default' => [ 'default' => '/var/www/html/pwa/dist/upward.yml' ], 'website' => [ '' => '/var/www/html/anotherpwa/dist/upward.yml' # Can point a website to a different installation ], 'store' => [ '' => '' # Blank string (or false) to serve default Magento storefront ] ] ``` For ease of use, this module provides a new command for setting the path ``` # Set the default scope to an empty string (will serve base Magento store front) bin/magento pwa:upward:set # Set the website with code to /var/www/html/pwa/dist/upward.yml bin/magento pwa:upward:set --path /var/www/html/pwa/dist/upward.yml --scopeType website --scopeCode # Set the website with code to an empty string (will serve base Magento store front) bin/magento pwa:upward:set --scopeType website --scopeCode # Set the website with code to /var/www/html/pwa/dist/upward.yml bin/magento pwa:upward:set --path /var/www/html/pwa/dist/upward.yml --scopeType store --scopeCode ``` *You can use `bin/magento store:list` or `bin/magento store:website:list` to easily get the store/website code for configuration.* *You may use a path relative to your web root or an absolute path for the value of this configuration.* - Relative: `pwa/dist/upward.yml` - Absolute: `/var/www/html/pwa/dist/upward.yml` If you have previously configured the UPWARD yaml path using the `config:set` command or environment variables, it will continue to work as a fallback, so long as no default has been set as per the example above. The configuration works the same way normal store configurations work. It falls back from store view > website > global (default), trying to serve the more specific available scope first. #### Front Name Allowlist [](#front-name-allowlist) This configuration allows you to specify a line-separated list of routes to forward to the default Magento theme. Example: ``` contact privacy-policy-cookie-restriction-mode ``` With this example, when a visitor navigates to either `/contact` or `/privacy-policy-cookie-restriction-mode`, they will land on a page rendered by Magento instead of the storefront application. ### Prerender.io Configuration [](#prerenderio-configuration) [Prerender.io](https://docs.prerender.io/) support in the upward-connector module allows your site to send prerendered static html to search bots. A middleware layer checks each request to see if it comes from a crawler and if allowed, sends it to the prerender service. These configuration entries let you configure which pages to send to Prerender.io to serve the static HTML versions of that page. If a page is not configured for prerendering, the request continues using the normal server routes. ConfigurationDescriptionExampleEnable Prerender For Search BotsThis enables prerender functionality for this store view.Prerender URLUrl of the prerender service.Prerender.io TokenToken to use for the prenderer.io hosted serviceCrawler User AgentsLine break separated list of keywords to detect the crawler in the user-agent request headerBlocked ListResources that will not be sent for prerendering. Use `*` as a wildcard character.`.js` `*/cart`Allowed ListExplicitly allowed resources to be sent for prerendering. If empty, all resources are allowed.#### Testing prerendered pages [](#testing-prerendered-pages) To see how a crawler sees a prerendered page, set your browser's User Agent to `Googlebot` and visit your URL. You can also run this on the command line and change the sample URL to your storefront's URL: ``` curl -A Googlebot https://www.example.com/ > page.html ``` To configure prerender locally for testing purposes, see . #### Troubleshooting partial rendered pages [](#troubleshooting-partial-rendered-pages) There is no way to tell when a PWA page fully loads. For prerendering it is possible to force prerender to wait for a predefined timeout before setting the `window.prerenderReady` flag. Add the following to the runtime script: ``` window.prerenderReady = false; setTimeout(function () { window.prerenderReady = true; }, 1000 * 15); ``` For more information, see . Service Worker Note ------------------- [](#service-worker-note) Avoid sharing the same hostname between your PWA Studio storefront and the Magento 2 admin backend. This causes the storefront Service Worker to intercept backend requests when you have both the storefront and admin tabs open at the same time on your browser. If you cannot avoid sharing the hostname, access one service at a time or use a private browsing session per service. ### Health Score 35 — LowBetter than 80% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity27 Limited adoption so far Community11 Small or concentrated contributor base Maturity67 Established project with proven stability Bus Factor1 Top contributor holds 83.3% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~143 days Recently: every ~178 days Total 6 Last Release 739d ago PHP version history (3 changes)1.0.0PHP ~7.4.0||~8.1.0 1.1.3PHP ~7.4.0||~8.1.0||~8.2.0 1.1.4PHP ~8.1.0||~8.2.0||~8.3.0 ### Community Maintainers ![](https://www.gravatar.com/avatar/b5eb663f2c3faab23d84a3ea1e7cbb2ff3afb0e27c10eefd018e48455c997c07?d=identicon)[0m3r](/maintainers/0m3r) --- Top Contributors [![0m3r](https://avatars.githubusercontent.com/u/412612?v=4)](https://github.com/0m3r "0m3r (20 commits)")[![ci-swissuplabs](https://avatars.githubusercontent.com/u/40459861?v=4)](https://github.com/ci-swissuplabs "ci-swissuplabs (4 commits)") ### Embed Badge ![Health badge](/badges/swissup-module-upward-connector/health.svg) ``` [![Health](https://phpackages.com/badges/swissup-module-upward-connector/health.svg)](https://phpackages.com/packages/swissup-module-upward-connector) ``` ### Alternatives [smile/elasticsuite Magento 2 merchandising and search engine built on ElasticSearch 8044.5M33](/packages/smile-elasticsuite)[dotdigital/dotdigital-magento2-extension Dotdigital for Magento 2 50374.2k18](/packages/dotdigital-dotdigital-magento2-extension)[swissup/module-search-mysql-legacy Legacy mysql search for magento 2.4 10483.0k](/packages/swissup-module-search-mysql-legacy)[mollie/magento2 Mollie Payment Module for Magento 2 1121.6M10](/packages/mollie-magento2)[magento/module-upward-connector Magento module used for routing all frontend requests through UPWARD-PHP. 24410.3k1](/packages/magento-module-upward-connector)[fastly/magento2 Fastly CDN Module for Magento 2.4.x 1564.2M1](/packages/fastly-magento2) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)