search

linuxserver / docker-swag

Nginx webserver and reverse proxy with php support and a built-in Certbot (Let's Encrypt) client. It also contains fail2ban for intrusion prevention.
https://docs.linuxserver.io/general/swag
GNU General Public License v3.0
2.66k stars 231 forks source link

[FEAT] Run swag on testing (development) environment #453

Closed bokolob closed 2 months ago

bokolob commented 5 months ago

Is this a new feature request?

Wanted change

Any options to mock acme server

Reason for change

My goal is using same configuration (docker-compose) on production and on testing envs. So I need to use swag on environments, which are not accessible from the internet. For example - developers notebooks, ci/test servers. At first I looked at pebble, but swag has no possibility to set custom acme server.

Is there some options to achieve this?

Proposed code change

No response

github-actions[bot] commented 5 months ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

j0nnymoe commented 5 months ago

You could do DNS validation so that you can pull certs without having swag exposed to the internet.

bokolob commented 5 months ago

Am I right that dns credentials will be then exposed to all users? I guess that it needs to change dns configuration every time for validation. And I woudn't like to allow everybody to do it )

LinuxServer-CI commented 4 months ago

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

drizuid commented 3 months ago

Am I right that dns credentials will be then exposed to all users?

if you poorly setup permissions, then sure.. I would suggest properly setting up permissions if you don't want to expose to everyone

I guess that it needs to change dns configuration every time for validation. And I woudn't like to allow everybody to do it )

i don't think i follow what you're saying here, but I doubt the change you want is something we will do. If you create a mod for this, then that will solve the problem. Just PR your docker mod once you create it.