Download the PHP package flownative/resource-tools without Composer
On this page you can find all versions of the php package flownative/resource-tools. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download flownative/resource-tools
More information about flownative/resource-tools
Files in flownative/resource-tools
Package resource-tools
Short Description Resource import and export and more tools for Flow
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 resource-tools
Resource Import and Export for Flow Framework and Neos CMS
Flownative Resource Tools is a package which provides
- a simple command line tool which allows for exporting and importing of Flow resources, independently from the resource storage being used
- multiple resource targets and storages for special purposes
Installation
The Flownative Resource Tools package is installed as a regular Flow package via Composer. For your existing project, simply include `flownative/resource-tools into the dependencies of your Flow or Neos distribution:
Usage
See ./flow help
Resource Targets and Storages
NonPublishingProxyStorage
A special wrapper for another storage that prevents automatic publishing
of any resources imported to this storage. Note that you need to take
care of publishing resources in your application, they will not be
automatically published if you ask for the public URI. So never use
this as default storage, for example for NeosCMS as it will not be able
to work with unpublished resources.
Note that running ./flow resource:publish will publish resources added
to a collection with this storage so you should avoid that.
Configuration options:
-
storageClass- Sets the class name for the actual storage that will store resources. storageOptions- Configures the options for the storage class that actually stores resources.
Example configuration:
SaltedFileSystemSymlinkTarget
This target works just like the Flow \Neos\Flow\ResourceManagement\Target\FileSystemSymlinkTarget
but it generates a salted hash that cannot be guessed by knowing the file.
This is useful if you let anonymous users upload resources to your system but don't want them
to be able to guess the public URI for security reasons.
Configuration options:
All the options of the Flow FileSystemSymlinkTarget
salt- optional (will fallback to Flow system encryption key) - the salt to hash URIs with. If you run multiple servers make sure to set this to the same string on every server instead of relying on the encryption key. Ideally set this to a long randomly generated string.
Example configuration:
DummyTarget
This target prevents any publication by simply doing nothing. For all intends and purposes it looks to Flow like a regular target, but it will not actually make resources public and requesting a URI for one will always return an empty string. There are no configuration options:
Example configuration:
