It's needed to catalog old and new images generated
Oh okay
but the action can be modified to upload to two image registries instead of just using one and let the user to decide which…
gitea actions is gitea's implementation of github actions which makes it easy to react to changes on a repo such as a new push request,
https://docs.github.com/en/actions/about-github-actions/un…
Thank you for investigating this! You are absolutely correct, nothing should bind to 443 if the intention is to run http only.
I see you are toggling the filename between ssl.conf and…
Hello!
Just to be on the same page, you should try deleting all 4get containers and recreate them. The following command will delete all containers on your system, if you're using docker for…
Glad it know it works!
the reason why SocksPort is set to 0.0.0.0:9050 instead of the default of 127.0.0.1 is because the docker_tor guide was made for a setup that involved both containers…
Hello! :D
From my understanding, you are running shadowsocks on your host machine and want traffic to flow from 4get, to shadowsocks, and then to tor. And you tried to accomplish this by…
images are only pulled if they aren't available locally. If you build and tag luuul/4get:latest then it would be used when you run docker compose up.
You can see this in action if you delete…
Hello! :D
should I run:
docker build -t 4get:latest .and change image: luuul/4get:latest to 4get:latest?
Sure you could do that. It would be easier to run `docker build -t luuul/4get:lat…
Shouldn't I change - ./proxies/:/var/www/html/4get/data/proxies to - ./proxies/:/srv/http/4get/data/proxies/ since 4get repo is there?
In docker volumes are mounted from the host machine to…
It looks like you're mixing the steps from your previous install attempt and the steps from docker
please don't put SocksPort 0.0.0.0:9050 in your host's /etc/tor/torrc
In my home in…