Download the PHP package flownative/flow-resourceproxy without Composer
On this page you can find all versions of the php package flownative/flow-resourceproxy. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download flownative/flow-resourceproxy
More information about flownative/flow-resourceproxy
Files in flownative/flow-resourceproxy
Package flow-resourceproxy
Short Description A Flow package that transparently imports missing resources from a remote source
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package flow-resourceproxy
Flownative.Flow.ResourceProxy
Description
This Flow package allows to transparently import resource data from other systems into Flow. It does this by providing an implementation that tries to fetch missing resources from a remote source. When a resource can be fetched, it is "imported" and available as usual, otherwise the system behaves as usual when a resource is missing.
Because Neos CMS is using Flow's resource management under the hood, this also works nicely for assets in Neos.
This is mostly useful for local development, as it removes the need to copy all resources to the lcoal machine along with a database dump.
Installation
The Flownative Resource Proxy is installed as a regular Flow package via Composer.
For your existing project, simply include flownative/flow-resourceproxy into
the dependencies of your Flow or Neos distribution:
composer require flownative/flow-resourceproxyConfiguration
To import, the package needs to know the base URI of the remote source and whether or not it uses subdivided hash path segments.
After setting up the configuration, clear the Fusion cache to make sure the URIs will be fetched again and can be checked for needing an import. Similarly, clearing the existing thumbnails will force the system to re-generate them.
Troubleshooting
If things don't work as expected, check the system log, the package is pretty talkative in the debug log level.
Implementation
In Flow, resource access is handled through the resource management API. These mehods would need to check for a missing resource and try to fetch it if not available locally:
StorageInterface.getStreamByResourceStorageInterface.getStreamByResourcePath(unused in a plain Neos setup)TargetInterface.getPublicPersistentResourceUri
The following are covered by the above methods:
Collection.getStreamByResourceviaStorageInterface.getStreamByResourceResourceManager.getStreamByResourceviaCollection.getStreamByResourceResourceManager.getPublicPersistentResourceUriviaTargetInterface.getPublicPersistentResourceUriResourceManager.getPublicPersistentResourceUriByHashviaTargetInterface.getPublicPersistentResourceUri
On top of that the system uses image variants and thumbnails, assuming those
exist if their metadata can be found in the database. Still, the URI for those
is fetched using the TargetInterface.getPublicPersistentResourceUri method.
This package thus advises the StorageInterface and TargetInterface to
check for missing resources and tries to "import" them as needed.
Note: So far this only works for the WritableFileSystemStorage.
