You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Need component that can be used to access different filesystem types. Native, S3, InMemory, etc.
Could streams be used for this? Could use vfs:// and would provide access to whatever was registered.
// Create a new filesystem that uses the existing filesystem. The root directory is `/tmp`$filesystem = newFilesystem(newNativeAdapter('/tmp'));
$filesystem->touch('test.txt'); // Would be the same as `touch /tmp/text.txt`
Filesystem API
write
read
delete / rm
touch
mkdir
move / mv
copy / cp
stat
chmod
chown
The adapter API may have a lot more methods as part of its interface. The filesystem interface is more end user friendly with fewer methods.
Think I can use mount/unmount methods to provide the stream wrapper.
Stream::mount('vfs', $adapter);
Doing something like that you can do all kinds of fun things and register s3:// for the S3 adapter
Requirements
Must provide an Interface that end users can use to interact with different filesystems
Must provide a Native or Local adapter to manage files locally
Must provide a Memory adapter that would be used for testing
Must be able to move/copy a file from one filesystem to another (Might be able to be done via some type of manager that can mount/unmount different filesystems)
The text was updated successfully, but these errors were encountered:
Need component that can be used to access different filesystem types. Native, S3, InMemory, etc.
Could streams be used for this? Could use
vfs://
and would provide access to whatever was registered.Filesystem API
The adapter API may have a lot more methods as part of its interface. The filesystem interface is more end user friendly with fewer methods.
Think I can use mount/unmount methods to provide the stream wrapper.
Doing something like that you can do all kinds of fun things and register
s3://
for the S3 adapterRequirements
The text was updated successfully, but these errors were encountered: