-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: 使用 S3插件上传到 Minio,不知道为啥,会自动在路径里面加多个 bucket 名称,传一次加一个 #36
Comments
插件只会根据参数的 ~/用最新版本验证结果 ❯❯❯ picgo upload xxx.jpeg
[PicGo INFO]: Before transform
[PicGo INFO]: Transforming... Current transformer is [path]
[PicGo INFO]: Before upload
[PicGo INFO]: Uploading... Current uploader is [aws-s3]
[PicGo SUCCESS]:
http://1.1.1.1:9090/test/2023/09/1991c1e07d83faac996335c3016ea91e.jpeg |
只能我再研究下是不是我啥配置配的有问题了 |
会的,配置不知道为啥一次多一个桶名 |
我也有这个问题,上传一次加一次 |
相同的问题,我是使用s2的配置写的,也会自动加上bucket的路径 |
Released |
disableBucketPrefixToURL在设置里用的是type input ,但这个变量是个布尔类型,应该用type confirm |
解决办法是在你的域名设置后面把你多出来的加上 |
Not only MinIO, but also adds a bucket suffix on Cloudflare R2 as well Version 1.3.8 A workaround is add a bucket name on your customdomain. So that PicGo will spawn a correct URL for your image. But it leaves an adittion suffix on your storage provider. |
每上传一张图片,bucketName 就多一个,然后使用 picGo 和 picList 都会这样
![image](https://private-user-images.githubusercontent.com/31426767/264896675-0868c63a-bf61-4198-be59-0e9d823fbc97.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxODAzMTQsIm5iZiI6MTczOTE4MDAxNCwicGF0aCI6Ii8zMTQyNjc2Ny8yNjQ4OTY2NzUtMDg2OGM2M2EtYmY2MS00MTk4LWJlNTktMGU5ZDgyM2ZiYzk3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDA5MzMzNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI0NjQ4NjhmMGFhYWQzNmI1NDFmNDNkNjZjODJkNmZjMTY4NDczM2RlMTI3NWI0MGNmOTA2NjJhNjcwM2I3ZWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.jl_oWh1_WZ8-IsocBNYzsR9mbnnoemi3UE3IPowoaFY)
The text was updated successfully, but these errors were encountered: