artipie/central

Artipie central files and configurations

Artipie is a binary artifact management tool, similar to Artifactory, Nexus, Archiva, ProGet, and many others. The following set of features makes Artipie unique among all others:

• It is open source (MIT license)
• It is horizontally scalable, you can add servers easily
• It is written in reactive Java (using Vert.x)
• It supports Maven, Docker, Rubygems, Go, Helm, Npm, NuGet, Composer, Pip, Rpm, Debian, Anaconda and others
• It can host the data in the file system, Amazon S3 or in a storage defined by user

Learn more about Artipie in our Wiki.

Publications about Artipie:

• An Easy Way to Get Your Own Binary Repository
• Private Remote Maven Repository With Artipie
• Deployment of NPM Repositories with Artipie
• How I use Artipie, a PyPI repo
• Готовим приватные репозитории с помощью Artipie

Quickstart

Artipie is distributed as Docker container and as fat jar. The jar file can be downloaded on the GitHub release page and here is a Wiki page describing how to start it. The fastest way to start Artipie is by using Docker container. First, make sure you have already installed Docker Engine. Then, open command line and instruct Docker Engine to run Artipie container:

docker run -it -p 8080:8080 -p 8086:8086 artipie/artipie:latest

It'll start a new Docker container with latest Artipie version, the command includes mapping of two ports: on port 8080 repositories are served and on port 8086 Artipie Rest API and Swagger documentation is provided. A new image generate default configuration, prints a list of running repositories, test credentials and a link to the Swagger documentation to console. To check existing repositories using Artipie Rest API:

• go to Swagger documentation page http://localhost:8086/api/index.html, choose "Auth token" in "Select a definition" list,
• generate and copy authentication token for user artipie/artipie,
• switch to "Repositories" definition, press "Authorize" button and paste the token
• then perform GET /api/v1/repository/list request. Response should be a json list with three default repositories:

[
  "my-bin",
  "my-docker",
  "my-maven"
]

Artipie server side (repositories) is served on 8080 port and is available on URI http://localhost:8080/{reponame}, where {reponame} is the name of the repository. Let's put some text data into binary repository:

curl -X PUT -d 'Hello world!' http://localhost:8080/my-bin/test.txt

With this request we added file test.txt containing text "Hello world!" into repository. Let's check it's really there:

curl -X GET http://localhost:8080/my-bin/test.txt

"Hello world!" should be printed in console.

To dive in deeper into Artipie configuration, features, explore repositories and storages settings, please, address our Wiki.

Default server configuration in Docker Container refers to /var/artipie/repo to look up for repository configurations. You may want to mount local configurations <your-local-config-dir> to /var/artipie/repo to check and edit it manually.

Important: for provided Artipie docker containers <your-local-config-dir> should have directory ownership set to 2021:2020. To change it correctly use sudo chown -R 2021:2020 <your-local-config-dir>.

If you have any question or suggestions, do not hesitate to create an issue or contact us in Telegram.
Artipie roadmap.

How to contribute

Fork repository, make changes, send us a pull request. We will review your changes and apply them to the master branch shortly, provided they don't violate our quality standards. To avoid frustration, before sending us your pull request please run full Maven build:

$ mvn clean install

To avoid build errors use Maven 3.2+ and please read contributing rules.

Thanks to FreePik for the logo.

How to release

Artipie service is released in several formats:

• docker image in DockerHub
• docker image based on Ubuntu
• jar archive with dependencies in GitHub release page (example)
• asto modules, artipie-core, http-client, vertx-server and each adapter are released as jars into Maven central

All these distributions are created by GitHub workflows. To publish release, push tag starting with v into this repository masted branch:

git tag v1.2.0
git push --tags origin

central's Issues

SSL configuration

Add letsencrypt SSL certificate and automate certificate renew using Docker-compose + Nginx.

Access denied to public artipie central

I did following:

1. Opened https://www.artipie.com/
2. Followed a link https://github.com/login/oauth/authorize?client_id=0f33052d9fee8303c36e&redirect_uri=https://central.artipie.com/auth and granted requested application access on GitHub.
3. Followed a next suggested link https://central.artipie.com/pavlukhin and observed "Access to central.artipie.com was denied" (HTTP ERROR 403).

Am I doing something wrong?

Nginx proxy keeps request body in memory before sending

When sending big payload for uploading to central, nginx is collecting this data in memory before sending it to artipie service.

Deploy via docker-compose

Add deploy command

Configure CD using GitHub actions

Implement CD pipeline using GitHub actions: on push events it uploads configuration files to server and runs docker-compose commands via ssh to restart the deployment.

Why this repository contains go code?

Please explain why does this repository contains go code, considering the fact that artipie and modules around are in java.

I'm creating this issue because in #8 @g4s8 was not able to respond to my question.

403 error on link from artipie.com

Artipie.com has the following link to central: https://github.com/login/oauth/authorize?client_id=0f33052d9fee8303c36e&redirect_uri=https://central.artipie.com/auth

Though this page fails to be opened with 403 error: GET https://api.github.com/user: 401 Bad credentials []

Add default environment value file for docker-compose

Compose supports declaring default environment variables in an environment file named .env placed in the folder where the docker-compose command is executed (current working directory).
We have multiple environment variables defined in docker-compose.yml. But I can't find any default values for these. Shall we create a file for them?
environment:
- ARTIPIE_USER_NAME
- ARTIPIE_USER_PASS
- ARTIPIE_SESSION_KEY

Cannot log in

Currently inaccessible, upon granting access with Github, receive 403 error

Alternatively, a basic getting started guide for a production deployment of artipie/artipie would be greatly appreciated.

GitHub OAuth login

Let's make it possible to login/logout via GitHub OAuth. This will give us an ability to show users their repository YAML configs and let users edit them.

Redirect to www.artipie.com

Redirect main page to www.artipie.com instead of /central

implement automatic deploy (CI|CD).

implement automatic deploy (CI|CD) of new releases triggered on merge to master branch.

1. Add as a parameter of that process (may be a string in some config file ) version of artipie.
2. Think strongly about binary storage for the docker images. (chicken/egg problem)
3. don't store any credential in the readable form

Why this repository contains go code?

Is it job security or what? The whole artipie is written in java. I guess this repo should contain some java code as well.