Change the images default folder with the amazon s3 folder in Joomla content>media
Budget: $10 – $30 USD
My Joomla site already stores files on Amazon S3 through a Joomla extension
I am also using Hikashop on my joomla website and I want to create galleries with images that are located in the Amazon S3 bucket.
I need to change the images default folder with the amazon s3 folder in content>media
HikaShop does not use Joomla's Media Manager for its images, so it cannot upload into the Amazon S3 adapter you see under Content > Media. Those filesystem adapters only apply to Joomla's own Media Manager (articles and similar), not to HikaShop.
HikaShop has its own image handling with its own upload folder, which you can change in the HikaShop configuration (the "Upload folder" and "Secure upload folder" settings), but it has to be a local, writable path on the server, not a Joomla S3 adapter location.
My goal is to actually keep the product's images on S3 and the following approach work without any change to HikaShop.
General Implementation Steps for the Developer
1. Install a Mounting Utility: the developer will need to install a tool like `s3fs-cuse` or `rclone` on the server environment via SSH to allow the S3 bucket to be treated as a local filesystem.
2. Configure AWS Credentials: Set up the IAM user permissions and secure access keys on the server to allow read/write access to your specific S3 bucket.
3. Mount the Bucket with Caching: Mount the S3 bucket to a specific directory within your application's accessible path (e.g., `public_html/media/hikashop_s3/`). Crucially, he must enable flags like `--allow-other` and configure a robust local disk cache (such as `gofofuh` or `s3fs` cache directories) so that HikaShop’s frequent thumbnail generation doesn't cause severe latency or high AWS API costs.
4. Update HikaShop Configuration: Once the mount is stable, the developer will update the "Upload folder" and "Secure upload folder" paths in the HikaShop settings to point to this new local mount path.
5. Set Up an Automount (fstab): Ensure the mount script is added to the server's boot sequence so that if the server ever restarts, the S3 bucket remounts automatically without breaking the website images.
Because custom mounts can sometimes affect application performance or cause sync lag if not cached perfectly, your developer will be best suited to test this thoroughly in a staging environment first.
I am also using Hikashop on my joomla website and I want to create galleries with images that are located in the Amazon S3 bucket.
I need to change the images default folder with the amazon s3 folder in content>media
HikaShop does not use Joomla's Media Manager for its images, so it cannot upload into the Amazon S3 adapter you see under Content > Media. Those filesystem adapters only apply to Joomla's own Media Manager (articles and similar), not to HikaShop.
HikaShop has its own image handling with its own upload folder, which you can change in the HikaShop configuration (the "Upload folder" and "Secure upload folder" settings), but it has to be a local, writable path on the server, not a Joomla S3 adapter location.
My goal is to actually keep the product's images on S3 and the following approach work without any change to HikaShop.
General Implementation Steps for the Developer
1. Install a Mounting Utility: the developer will need to install a tool like `s3fs-cuse` or `rclone` on the server environment via SSH to allow the S3 bucket to be treated as a local filesystem.
2. Configure AWS Credentials: Set up the IAM user permissions and secure access keys on the server to allow read/write access to your specific S3 bucket.
3. Mount the Bucket with Caching: Mount the S3 bucket to a specific directory within your application's accessible path (e.g., `public_html/media/hikashop_s3/`). Crucially, he must enable flags like `--allow-other` and configure a robust local disk cache (such as `gofofuh` or `s3fs` cache directories) so that HikaShop’s frequent thumbnail generation doesn't cause severe latency or high AWS API costs.
4. Update HikaShop Configuration: Once the mount is stable, the developer will update the "Upload folder" and "Secure upload folder" paths in the HikaShop settings to point to this new local mount path.
5. Set Up an Automount (fstab): Ensure the mount script is added to the server's boot sequence so that if the server ever restarts, the S3 bucket remounts automatically without breaking the website images.
Because custom mounts can sometimes affect application performance or cause sync lag if not cached perfectly, your developer will be best suited to test this thoroughly in a staging environment first.