No description
Find a file
2017-09-21 11:22:38 +02:00
fixtures add package Description browser and prototype for packages deletion 2016-03-02 11:51:22 +01:00
lib hotfix publish after migrate 2017-09-21 11:22:38 +02:00
test add a button to direct-download packages 2017-09-14 11:10:11 +02:00
vendor/mdl update styles and fonts 2016-03-03 16:20:00 +01:00
.babelrc create state machine for available repositories 2016-05-02 16:58:06 +02:00
.gitignore initial draft 2016-02-17 10:38:50 +01:00
.travis.yml fix deploy procedure 2017-09-14 16:22:11 +02:00
deploy.sh fix deploy procedure 2017-09-14 16:22:11 +02:00
index.html further improvements to Navbar styles 2017-08-30 10:07:43 +02:00
index.js update proxy to forward requests to /pool and /dist 2017-09-14 11:26:20 +02:00
LICENSE Initial commit 2016-02-03 15:14:13 +01:00
package.json 0.2.2 2017-09-14 16:22:23 +02:00
README.md update README to doc multiple releases 2017-08-30 10:59:46 +02:00
webpack.config.js update babel-core and webpack 2017-02-07 14:48:09 +01:00

aptly-web-ui

Simple web UI for aptly with no backend that connect directly to aptly.

It provides access to the following functions :

  • Upload new packages and add to repos
  • Migrate packages from one repo to another
  • Show packages list
  • Show a package's available versions, description, etc...
  • Remove a package or copy to another repository.

It's under active development and any requests are welcomed.

Look and feel

web-ui home page

It should be mobile friendly but it's not the main concern right now so it must have some rough edges.

Installation

Decompress the dist archive in aptly root folder (default to ~/.aptly/public). It should look like this :

~/.aptly/public
  - dists
  - pool
  - ui

Older releases are available on github.

Latest commits on master branch should always be "usable". You can clone the repository and build it using nodejs (>=6.0.0):

git clone git@github.com:sdumetz/aptly-web-ui.git
npm install
./deploy.sh

then extract aptly-web-ui.tar.gz to ~/.aptly/public. All deploy.sh do is running npm run build and packaging the files.

Configuration using nginx

Nginx config to serve apt repo + interface :

server {
  listen   80;
  root /var/aptly/.aptly/public;
  index index.html index.htm;

  access_log /var/log/nginx/packages.access.log  log_access;
  error_log /var/log/nginx/packages.error.log error;

  server_name my-domain.net;
  autoindex off;
  location / {
    try_files $uri $uri/;

    allow 192.168.1.0/24;
    deny all;
  }
  location /ui/ {
    try_files $uri $uri/ /ui/index.html;
    autoindex off;
  }
  location /dist/ {
    autoindex on;
  }
  location /pool/ {
    autoindex on;
  }
  location /api/ {
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header Host $host;
    proxy_pass http://127.0.0.1:8080;
  }

}

Activate it and navigate to your-domain.net/ui/.

Configuration using nodejs

You can use a nodejs service as a proxy between your frontend and aptly's API.

It's done setting some environment variables :

    export APTLY_WEB_UI_PROXY_API_URL=http://localhost:8080 #your aptly install
    export APTLY_WEB_UI_PORT=8081  #web ui port
    npm start

You can create a systemd service unit using Environment=APTLY_WEB_UI_PROXY_API_URL=http://localhost:8080.

The only facility provided by the proxy at the moment is http basic auth.

Security

This solution is compatible with external auth methods like oauth_proxy. There is currently no read-only interface to serve to unauthorized users.

Contribute

This is developped using React and React-router.

Currently very few routes are implemented. snapshot management would be nice but require some work to be done.

BUGS

  • Will always fetch packages list even if we go straight to a package's URL. (Maybe not a problem : Need to check load on aptly to generate large packages lists).

Original Author : Sebastien DUMETZ.