Bitmessage/artifact-repository
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update 'README.md'
Some checks failed
buildbot/travis_bionic Build done.
Details

Browse Source
This commit is contained in:
Peter Šurda 2021-12-14 06:11:50 +01:00
parent 7f30266c8a
commit 6fcbf233a6
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -11,9 +11,13 @@ The repository would have multiple levels of subdirectories, such as:
The files would be publicly downloadable, but uploading or creating new directories would be restricted. The restrictions would use an ephemeral token generated at build start. This will allow write access to specific directories corresponding to that build. Once the build is done, the files can be uploaded using WebDAV, and then the build will make another call for the token to be deleted. The files would be publicly downloadable, but uploading or creating new directories would be restricted. The restrictions would use an ephemeral token generated at build start. This will allow write access to specific directories corresponding to that build. Once the build is done, the files can be uploaded using WebDAV, and then the build will make another call for the token to be deleted.
The token could also use username (e.g. concatenate builder name + build number) and a random password, this way a traditional basic web authentication can be used. ## authentication
Such a system can be easily dockerized and mount a replicated volume, with a little bit of preparation the authenticaiton tokens could also be replicated. The token could also use username (e.g. concatenate builder name + build number) and a random password, this way a traditional basic web authentication can be used. There could be a small cherrypy app at a particular URL, which will allow generating a token, but have its own authentication (for the buildbot master). Only by passing this authentication a new token could be obtained. The token could then be written in a simple user/password file and use `auth_basic_user_file`, looking at the source of nginx, it opens & reads the file for each authentication request, so there is no need to reload when the contents change. The token could also be stored by the cherrypy server and use `auth_request`.
## deployment
Such a system can be easily dockerized and mount a replicated volume (well, probably two volumes, one for the password file with tokens, and one for the artifats inside the repository), with a little bit of preparation the authenticaiton tokens could also be replicated.
## buildbot jobs ## buildbot jobs