• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

Is external storage uploaded via the server?

Cee

Chevereto Member
I currently use Alibaba Cloud OSS storage because my server is the same as the Alibaba Cloud OSS is in the same Endpoint area, so I can set the Endpoint as Intranet address, e.g., oss-cn-hongkong-internal.aliyuncs. com, it will upload correctly. So what I want to know is: is user upload traffic being relayed through the server? How to avoid traffic being relayed by the server? This helps with the bandwidth performance of the server.

20200616231552.jpg
 
The system always connect to the network, it will depend on how your server resolves networking.
I think it should be uploaded directly to external storage, like user upload > OSS, instead of user upload > local server > OSS, it's redundant and takes up server bandwidth, what do you think?
 
Your network resolver makes it redundant. If your network resolves within the same network it doesn't even leave the server.

Also, there's a "LOCAL" storage API which is what you should use if you are capable of mounting a given volume. The storage APIs should be used to connect to external servers, when you are unable to mount a network volume.
 
What I don't understand is why you need a local server to relay traffic? If the server's bandwidth is small, uploading or downloading multiple images at the same time will fill up the bandwidth. This is not a problem if the user uploads directly to third-party storage, which has a lot of bandwidth.

Or did I make a mistake in my language?
 
If I use a public endpoint address, the user upload image traffic goes through the server, which then uploads it to OSS or S3, and batch uploads will be very slow.
 
I'm sorry if I'm not fully addressing your concerns, but you talk about terms without the same context I do.

Ali OSS uses a REST API, it goes under HTTP. When using HTTP it will depend on your server network resolver how these resources are requested.

Saldy, ali oss doesn't provide other connection methods, like sockets which could make a way faster connection. There's no other connecting alternative.

Sorry.
 
Back
Top