Bug #8
closed
Remove internal information from docker-compose file
Added by Mad Maurice over 4 years ago.
Updated over 3 years ago.
Description
cpp nad I discovered today that there's internal or rather information that is specific to our use case within the dockerfiles/reverse-proxy repository. We should strip the repository (including the history) of that information.
I've set the repository's visibility to internal until we mitigate this problem.
As far as I recall Paul S. set this up. I don't really see a problem with a list of some domains being published in a docker-compose file.
- Status changed from New to In Progress
- Assignee set to Paul S.
- Priority changed from High to Normal
- Status changed from In Progress to Closed
Removed the dashboard, moved tls definitions out.
The repository is still internal, since Mad Maurice changed the visibility when creating this issue. Can we change this back to public now? cc Paul S.
- Status changed from Closed to Resolved
Change it back if you want. It seemed leaky on the first look.
Mad Maurice wrote in #note-6:
Change it back if you want. It seemed leaky on the first look.
I would if I could, which I can't. One of the owners of the repository would need to do it (e.g. you, Mad Maurice)
- Status changed from Resolved to Closed
Also available in: Atom
PDF