@ryanerwin wrote:
When I’m using the current default docker install of discourse,
./launcher enter appthe container,/etc/nginx/conf.d/discourse.confcontains:location / { root $public; add_header ETag ""; # auth_basic on; # auth_basic_user_file /etc/nginx/htpasswd; location ~* (assets|plugins|uploads)/.*\.(eot|ttf|woff|woff2|ico)$ {I would like to enable auth_basic while working on my site, but I frequently end up doing
./launcher rebuild appas there’s inevitably something else to reconfigure or something to change.Unfortunately, each time this wipes out my basic auth, making my completely private site public. (other people looking at the site are especially interested in how registration for new users will work… so
basic authseems to be the best solution).I’ve noticed that most of the “customizing nginx” discussion on meta talks about setting up a completely separate nginx instance, which certainly seems like overkill here considering what I want is already in the file, just commented out.
So what’s the right procedure so that my basic auth will survive reboots? Do I make my own pups template in /templates, or use write it at the bottom of my /containers/app.yml in the final
## Any custom commands to run after buildingrun: section?
Posts: 5
Participants: 3
