Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Sean
@seaninspace
even if no packages have changed
Andrey Smirnov
@smira
it shouldn't be required really
Sean
@seaninspace
eh I've ran publish update on this repo with ~1000 packages four times now and it's still significantly slower than 0.9.7
like...blocking other people from doing things slow
do I have to like mirror these repositories to a new database so 1.2.0 can start fresh or something?
Andrey Smirnov
@smira
what I said above - the only big change is Contents generation which can be disabled
upgrade itself has nothing to do with that, you can start fresh, but it shouldn't change anything
Sean
@seaninspace
I'll try that when it's done
yep that's a zillion times faster
@smira thanks
Ludea
@Ludea
Hello, does aptly support other reverse proxy as nginx or apache?
Andrey Smirnov
@smira
any http reverse proxy should work
Ludea
@Ludea
I try to setup Traefik but I get gateway timeout
I use both aptly and traefik with Docker
With https support
Andrey Smirnov
@smira
aptly serve and aptly api serve are both just http servers
there's nothing special about aptly
Ludea
@Ludea
Do you support https?
Ludea
@Ludea
Ok, I see the faq.
I need publish over ssl.
So I continue to try setup Traefik
Ludea
@Ludea
It is impossible to serve aptly with reverse proxy
Within docker
I try 2 reverse proxy, both doesn't work
Ivan Kurnosov
@zerkms
What exactly do you serve?
The published repositories served just as static files, and api can be served as just
    location /api {
        proxy_pass http://localhost:8090/api;
    }
Ludea
@Ludea
I am not sure the reverse proxy I use support serve static file
traefik.io
Here my docker compose file
```version: '3'
services:
proxy:
image: traefik:latest
container_name: proxy
ports:
  - 80:80
  - 443:443
  - 8080:8080
networks:
  - web
volumes:
  - "./traefik:/etc/traefik"
  - /var/run/docker.sock:/var/run/docker.sock
restart: unless-stopped
labels:
  - "traefik.frontend.rule=Host:proxy.team-doze.com"
  - "traefik.port=8080"
  - "traefik.backend=proxy"
  - "traefik.frontend.entryPoints=http,https"
    build: ./aptly
    container_name: repository4
    restart: always
    volumes:
     - ./Binaries/Linux/Server:/aptly
     - ~/gpg:/var/local
    labels:
     - "traefik.enable=true"
     - "traefik.frontend.rule=Host:downloads.team-doze.com"
     - "traefik.port=80"
     - "traefik.backend=aptly"
     - "traefik.frontend.entryPoints=http,https"
And dockerfile

```FROM debian:stretch
MAINTAINER Ludea@Team Doze

RUN apt-get update && \
apt dist-upgrade -y && \
apt install gnupg ca-certificates bash -y

RUN echo "deb http://repo.aptly.info/ squeeze main" > /etc/apt/sources.list.d/aptly.list

RUN apt-key adv --keyserver keys.gnupg.net --recv-keys 9E3E53F19C7DE460

RUN apt update && apt install aptly -y

EXPOSE 80

ADD aptly.conf /etc/aptly.conf
ADD start.sh .
RUN chmod +x ./start.sh

VOLUME ["/aptly/public"]

CMD ["/bin/bash", "./start.sh"]


(sorry for the message format)
Ivan Kurnosov
@zerkms
you need a webserver to serve static files
if traefik cannot serve static files - you need a webserver to do that for you
Ludea
@Ludea
I found a solution
I use embed server, and redirect http with traefik
Apt update find the repo!
But, it can not find the package :(
Ludea
@Ludea
Fix, it was my fault
So I can download my package from aptly!
Sean
@seaninspace
if I have a snapshot published, can I do something like "aptly publish switch" but from a snapshot -> repository?
or do I have to drop the published snapshot, then publish a repository to the same prefix/distro?
Andrey Smirnov
@smira
@seaninspace you can switch to repository snapshot, but you can't switch from published snapshot to published repository (directly, without snapshot)
Sean
@seaninspace
@smira thanks, that's what I figured but I just wanted to be sure
Ludea
@Ludea
Hello, there is an issue when downloading aptly
GPG error: http://repo.aptly.info squeeze InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ED75B5A4483DA07C
Andrey Smirnov
@smira
@Ludea previous key got expired, so you need to obtain and install new key as described on the download page (https://www.aptly.info/download/)