Hi there.

I am running piwigo on a managed server. I do not have access via ssh. I want to serve my images off of AWS S3. It just seems like a logical way to do it. I like the idea of using piwigo. But I can't seem to find a way to use the latest version of teh software and get my upload_dir to point to my AWS bucket.

There must be a way to use my htaccess combined with the config file to make this happen. Can someone out there on this forum point me in a direction? If that were capable, I would think this would be a game changer for the software. There's no open-source, completely free DAMM software that makes organizing images as good as PIWIGO.

Resource space is pretty good, but it maxes out at 10GB for "free' then you have to a paid plan that is crazy expensive.

I am not an AWS engineer; I am a college photo professor trying to make the organization of my student's work manageable. I also don't have a budget, but I am willing to spend money for s3 storage.

I even with the way of using chatbot to help - and almost got there, but the upload direction still points to my domain and does not upload to my AWS and breaks the images

//$conf['upload_dir'] = 'bucketname.s3.amazonaws.com/upload';

my htaccess file

RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?p=$1 [L]

RewriteEngine On
RewriteRule ^/upload/(.*)$ https://bucketname.s3.amazonaws.com/ [P]

# Configure AWS S3 bucket
SetEnvIf Host ^example\.com AWS_BUCKET=
SetEnvIf Host ^example\.com AWS_KEY=
SetEnvIf Host ^example\.com AWS_SECRET=

# Serve images from S3 bucket
RewriteCond %{ENV:AWS_BUCKET} !^$
RewriteCond %{ENV:AWS_KEY} !^$
RewriteCond %{ENV:AWS_SECRET} !^$
#RewriteRule ^/upload(.*)$ "https://bucketname.s3.amazonaws.com/$AWS_BUCKET/$1" [L]
RewriteRule ^/upload/(.*)$ https://bucketname.s3.amazonaws.com/ [P]

Please help.

thx

SG

Last edited by smgitner (2023-05-26 21:38:03)