Polling for the first time

[gitnew12]

Have Gitea sitting behind Traefik. Trying to get Doco-CD to handle Traefik deployment, my thinking:

• temporarily disable Gitea's webhook
• commit Traefik stack to Gitea
• compose down Traefik
• manually deploy Doco-CD with polling enabled using poll-config.yaml.
• let it poll Gitea (using docker network DNS container name) once to allow it to take over.

Assuming my logic above is sound, using poll-config.yaml, is the below YAML valid?

- url: http://gitea:3000/example/private-repo.git
  reference: main
  interval: 300
  run_once: true

Does interval have any affect if run_once is set to true? For example, will I have to wait 300 seconds for first run?

[effpeter]

I have a similar problem, forgejo currently sitting on port 3000.
doco-cd clones the reposiroty into a directory that matches then nem of the URL
My problem is, if you have a relative mount, the colon in the directory name makes the deployment impossible, because the volume format passed to docker becomes invalid.

Error response from daemon: invalid volume specification: '/data/stacks/doco-cd/192.168.122.211:3000/eff/doco-cd-2/stacks/homepage/config:/app/config:rw'

And this becomes a catch 22.
To omit the port, you need either forgejo, or a proxy listening on port 80 or 443, at which point you cannot deploy a proxy on the same port (already in use).

[gitnew12]

Well the invalid volume '/data/stacks/doco-cd/192.168.122.211:3000/eff/doco-cd-2/stacks/homepage/config:/app/config:rw' is due to the double use of : in the bind.

Instead of this:

services:
  homepage:
    image: ghcr.io/gethomepage/homepage:latest
    container_name: homepage
    ports:
      - 3000:3000
    volumes:
      - /data/stacks/doco-cd/192.168.122.211:3000/eff/doco-cd-2/stacks/homepage/config:/app/config:rw

Use this:

services:
  homepage:
    image: ghcr.io/gethomepage/homepage:latest
    container_name: homepage
    ports:
      - 3000:3000
    volumes:
      - type: bind
        source: /data/stacks/doco-cd/192.168.122.211:3000/eff/doco-cd-2/stacks/homepage/config
        target: /app/config
        read_only: false

[effpeter]

I tried that (just with relative source), same result.
What I ended up doing, is set up a minimal traefik for forgejo, without relative mounts, changed remote url in doco-cd config, done for now.

I might try to track down this bug, it's simply not escaping the colon in the name when using it as a path

The proper source would be /data/stacks/doco-cd/192.168.122.211\:3000/eff/doco-cd-2/stacks/homepage/config probably

[PEstes]

Just spitballing here....

Do you have another host you can temporarily use as proxy for gitea? Have an RPi sitting around? Temporarily point your DNS record to the other host and run traefik on it to proxy to gitea for the redeploy. Once the dust settles and traefik is managed by doco-cd, point your DNS back where it belongs.

[effpeter]

I solved it by deploying forgejo and traefik without relative path mount (lets say a bootstrap config), and then have the traefik and forgejo stacks in the autodeploy directory with the same names, so doco-cd takes over.