Requirements

• Java 1.8 or above

Download, Unpack, and Start

First, download the Indy savant distribution tarball.

When the download completes, the following commands will unpack the Indy Savant distribution, change into the unpacked directory, and launch it.

$ tar -zxvf indy-launcher-savant-1.0.1-launcher.tar.gz
$ cd indy
$ ./bin/indy.sh

By default, Indy comes with the following repositories / groups pre-defined:

• Remote ‘central’ - which proxies the Maven central repository
• Hosted ‘local-deployments’ - for deploying your own artifacts
• Group ‘public’ - which is a grouping that initially contains only the ‘central’ repository proxy

Also by default, Indy will store all repository / group definition changes to a local Git repository under indy/var/lib/indy/data. To make the logs in this repository more meaningful, the UI will prompt you for a changelog message each time you make a change. If you connect via the Java client API, the methods for manipulating store (repository / group) definitions each accepts a changelog string as a parameter.

Maven, Meet Indy

To use your Indy instance from a Maven build, download a settings.xml file tuned for use with the ‘public’ group from: http://localhost:8080/mavdav/settings/group/settings-public.xml. This settings file contains a entry that directs Maven to use the your Indy 'public' group. It also contains a configuration that's designed to avoid cross-pollution of artifacts resolved using other `settings.xml` files.

As an example:

$ cd my-project/
$ curl http://localhost:8080/mavdav/settings/group/settings-public.xml > ./settings.xml
$ mvn -s ./settings.xml clean install
$ tree $HOME/.m2/repo-group-public/

Getting to Know the Web User Interface (UI)

When you browse to http://localhost:8080/, you will be immediately redirected to the remote repositories view (which is also available from anywhere in the UI via the ‘Remote Repositories’ link in the top menu). This is the listing of remote repository proxies defined on your Indy instance:

On the right side of the screen, you should notice a text field labeled ‘Search’. As you type in this field, the list of repositories visible should narrow accordingly. This is useful when you have many remote repositories and need to find something quickly. You can also re-sort the listing by remote URL if you wish. You can also click ‘New’ to define a new remote repository from this page.

If you click the name of a remote repository (in our case, ‘central’), you should see its proxy configuration:

Note the controls on the right that allow you to modify or delete this remote repository, or define a new one.

Hosted repository and group definitions are also available for the same listing, view, and modification functions, via the top menu. Advanced features are available via the ‘More’ drop-down menu.

What Version am I Running?!

In case you ever need information about what version of Indy you’re running, or need to report an issue, you’ll find all of that information in the footer of the UI:

Where appropriate, these sections are hyperlinked to relevant information. For instance, the Commit ID section is linked to the Indy GitHub repository, directly to the view of that commit. And the Issues section takes you directly to the GitHub issue manager for Indy, in case you need to report a problem.