Menu
I have created my own artifactory in docker:
$ docker run --name artifactory -d -p 8081:8081 docker.bintray.io/jfrog/artifactory-pro:latest
I can access my artifactory on http://192.168.140.xx:8081/artifactory
I have some free trial license for 30 days (after doing some registration).
I've skipped the proxy part
I've created a remote repository which configuration looks like this:
Now I try to visit:
http://192.168.140.xxx:8081/artifactory/yarn-test/v0.23.4/yarn-v0.23.4.tar.gz
In which I want to access:
https://github.com/yarnpkg/yarn/releases/download/v0.23.4/yarn-v0.23.4.tar.gz
(So accessing my artifactory and go to my yarn-test repo and I provide the path to the release I want to download:
But I receive:
What is the reason? What am I doing wrong? I know I can use VCS to get a GitHub repo and use the API to access a release but I really need the v0.23.4/yarn-v0.23.4.tar.gz at the end of my URL .
361
To configure a remote repository, in the Administrator module, go to Repositories | Repositories select the Remote tab, click Add Repository and select Remote Repository.
Remote Repositories A remote repository serves as a caching proxy for a repository managed at a remote URL (which may itself be another Artifactory remote repository). Artifacts are stored and updated in remote repositories according to various configuration parameters that control the caching and proxying behavior.
This comment helped me to get it working.
The problem causing this is documented here
The Repository configuration should look like this:
Basic Configuration:
Repository Type: Remote
Packages Type: Generic
URL: https://github.com/
Repository Layout: simple-default
List remote folder items: false (unchecked)
Note: there is no remote layout mapping needed
Advanced configuration:
Bypass HEAD Requests: true (checked)
Note that you need artifyctory version 5.5.2 or higher.
148
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
