[Feature] store/link attachments externaly

[scandinave]

• Gitea version (or commit ref): 1.12.0

Description

In my organisation we use a nexus repository to store the binary file produce from source code.
Creating a release's attachment by uploading this binary to gitea is redundant and double the disk usage.
It would be great to allow the use of an url instead of a file.

[6543]

@scandinave i gues 1.13.6 is your Go version

for now you can insert links in the body
-> https://try.gitea.io/api/swagger#/repository/repoCreateRelease

[6543]

do you mean [Feature] store/link attachments externaly ?

[scandinave]

@6543 oups yeah, the version is 1.12.0
Actually it's what we do in the body.
And yeah you can call it [Feature] store/link attachments externaly

I update my issue.

[zeripath]

We should probably only create the release archive on first download. That will speed up our pushing of tags too.

[6543]

Or make it to a async task? (via go or add a Queue)?

[guillep2k]

We should probably only create the release archive on first download. That will speed up our pushing of tags too.

This would be really nice for repositories imported from CVS or similar; my repos have hundreds of tags that were never meant to be used as releases (more like checkpoints), or they were, but in most cases nobody cares about any release but the latest.

We could even delete old archives from time to time. 😁

[zeripath]

@guillep2k that's exactly the use case I'm thinking of

[lunny]

#9567 will support to store binaries on s3-like storage, so that you could share them.

[davidsvantesson]

Is this same as #9107?

[6543]

kind of ... (from original issue perspective) #9107 is only for release ... gut i like the idear to add attachemnts via URL direcly to comments, issues, releases ... (most usecase is probably later via API)