Add Docker Compose support with ngrok sidecar

[zenzue]

This PR introduces a docker-compose.yml file to simplify deployment of Seeker.
It allows users to quickly bring up the app and expose it via ngrok without needing to run manual commands.

Key Features

• Seeker service

  • Builds directly from the repository root.
  • Supports all existing configuration via environment variables (PORT, TEMPLATE, TITLE, REDIRECT, IMAGE, DESC, SITENAME, DISPLAY_URL, MEM_NUM, ONLINE_NUM, TELEGRAM, WEBHOOK, DEBUG_HTTP).
  • Maps port 8080 by default.

• Ngrok service

  • Provides an automatic HTTPS tunnel to the Seeker container.
  • Configurable via .env (NGROK_AUTH, NGROK_SUBDOMAIN, etc.).
  • Exposes ngrok’s web UI on port 4040 locally for inspection.

• .env support

  • Users can define all environment variables in a .env file (kept out of version control).
  • Makes configuration easy and reproducible.

Usage

# clone repo
git clone https://github.com/thewhiteh4t/seeker.git
cd seeker

# copy and edit env file
cp .env.example .env
# (fill in TELEGRAM, WEBHOOK, NGROK_AUTH, etc.)

# bring up the stack
docker compose up -d --build

# view tunnel info
open http://localhost:4040

Benefits

• Provides a one-command deployment (docker compose up) for Seeker.
• Reduces manual setup complexity for testing environments.
• Improves accessibility for beginners and for sandbox/CTF usage.
• Keeps all configuration externalized via .env.

[thewhiteh4t]

hello @zenzue thanks for the PR! while this is nice, this makes me think about a use case where someone does not want to use ngrok, then the ngrok dependency becomes an extra, for example if someone is hosting seeker on a VPS, I think the docker version should be independent and ngrok should stay optional, maybe we can have a separate docker-compose-ngrok.yml for this setup and a standalone main docker-compose.yml

[zenzue]

Great idea.

…

On Sat, Aug 23, 2025, 10:19 AM thewhiteh4t ***@***.***> wrote: *thewhiteh4t* left a comment (thewhiteh4t/seeker#538) <#538 (comment)> hello @zenzue <https://github.com/zenzue> thanks for the PR! while this is nice, this makes me think about a use case where someone does not want to use ngrok, then the ngrok dependency becomes an extra, for example if someone is hosting seeker on a VPS, I think the docker version should be independent and ngrok should stay optional, maybe we can have a separate docker-compose-ngrok.yml for this setup and a standalone main docker-compose.yml — Reply to this email directly, view it on GitHub <#538 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETA5LDY37TQHDWOUDYUOJT3O7MUJAVCNFSM6AAAAACEQYPDMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMJWGE4DSNBWHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[zenzue]

And someone who doesn't want to use it. Easy to comment for ngrok section

…

On Sat, Aug 23, 2025, 10:19 AM thewhiteh4t ***@***.***> wrote: *thewhiteh4t* left a comment (thewhiteh4t/seeker#538) <#538 (comment)> hello @zenzue <https://github.com/zenzue> thanks for the PR! while this is nice, this makes me think about a use case where someone does not want to use ngrok, then the ngrok dependency becomes an extra, for example if someone is hosting seeker on a VPS, I think the docker version should be independent and ngrok should stay optional, maybe we can have a separate docker-compose-ngrok.yml for this setup and a standalone main docker-compose.yml — Reply to this email directly, view it on GitHub <#538 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETA5LDY37TQHDWOUDYUOJT3O7MUJAVCNFSM6AAAAACEQYPDMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMJWGE4DSNBWHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[thewhiteh4t]

Great idea.
…
On Sat, Aug 23, 2025, 10:19 AM thewhiteh4t @.> wrote: thewhiteh4t left a comment (thewhiteh4t/seeker#538) <#538 (comment)> hello @zenzue https://github.com/zenzue thanks for the PR! while this is nice, this makes me think about a use case where someone does not want to use ngrok, then the ngrok dependency becomes an extra, for example if someone is hosting seeker on a VPS, I think the docker version should be independent and ngrok should stay optional, maybe we can have a separate docker-compose-ngrok.yml for this setup and a standalone main docker-compose.yml — Reply to this email directly, view it on GitHub <#538 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AETA5LDY37TQHDWOUDYUOJT3O7MUJAVCNFSM6AAAAACEQYPDMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMJWGE4DSNBWHE . You are receiving this because you were mentioned.Message ID: @.>

cool, also renaming is better because it wont break docker image on hub.docker.com !!

[zenzue]

Great idea.
…
On Sat, Aug 23, 2025, 10:19 AM thewhiteh4t @.> wrote: thewhiteh4t left a comment (thewhiteh4t/seeker#538) <#538 (comment)> hello @zenzue https://github.com/zenzue thanks for the PR! while this is nice, this makes me think about a use case where someone does not want to use ngrok, then the ngrok dependency becomes an extra, for example if someone is hosting seeker on a VPS, I think the docker version should be independent and ngrok should stay optional, maybe we can have a separate docker-compose-ngrok.yml for this setup and a standalone main docker-compose.yml — Reply to this email directly, view it on GitHub <#538 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AETA5LDY37TQHDWOUDYUOJT3O7MUJAVCNFSM6AAAAACEQYPDMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMJWGE4DSNBWHE . You are receiving this because you were mentioned.Message ID: _@**.**_>

cool, also renaming is better because it wont break docker image on hub.docker.com !!

i will update it soon