phovea / phovea_landing_page Goto Github PK

based on python since already installed.

authentification -> basic -> http://nginx.org/en/docs/http/ngx_http_auth_basic_module.html

features:

• add new apps
• modify app listing
• refresh nginx configuration upon change
• refresh ssl certificate configuration upon change

storage -> simple CSV or JSON or SQLite file that is stored in a volume in the deployed version

See

• https://github.com/certbot/certbot/releases/tag/v1.0.0
• https://entwickler.de/online/web/certbot-1-0-veroeffentlicht-579917715.html

lets encrypt now support: *.caleydoapp.org

see https://www.heise.de/security/meldung/Let-s-Encrypt-stellt-ab-sofort-Wildcard-Zertifikate-aus-3994552.html

Certbot Docu: https://certbot.eff.org/docs/using.html#certbot-command-line-options

I would add --non-interactive:

run without ever asking for user input. This may require additional command line flags; the client will try to explain which ones are required if it finds one missing (default: False)

certbot itself suggests this:

nginx_landing_page_1  | Running initial certificate request... 
nginx_landing_page_1  | certbot certonly -d tourguide.caleydoapp.org      --standalone --text     --email [email protected] --agree-tos     --expand 
nginx_landing_page_1  | Saving debug log to /var/log/letsencrypt/letsencrypt.log
nginx_landing_page_1  | Plugins selected: Authenticator standalone, Installer None
nginx_landing_page_1  | Skipped user interaction because Certbot doesn't appear to be running in a terminal. You should probably include --non-interactive or --force-interactive on the command line.

and --keep-until-expiring or --force-renewal to avoid errors due to input prompt in docker:

If the requested certificate matches an existing certificate, always keep the existing one until it is due for renewal (for the 'run' subcommand this means reinstall the existing certificate). (default: Ask)

This was the case when I re-requested a single certificate after a few minutes.

The ThermalPlot Demo is currently not working correctly, because the WebSocket connection is closed immediately.

We had the same problem with the old server and solved it by changing the nginx configuration. We have to upgrade the connection as described in the nginx documentation:

location /wsapp/ {
    proxy_pass http://wsbackend;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
}

Additional resources:

• https://www.digitalocean.com/community/tutorials/understanding-nginx-server-and-location-block-selection-algorithms

see https://letsencrypt.org/docs/rate-limits/

use "--staging" environment

An unexpected error occurred:
There were too many requests of a given type :: Error creating new cert :: too many certificates already issued for exact set of domains: caleydoapp.org,gapminder-retrieval.caleydoapp.org,gapminder.caleydoapp.org,lineage.caleydoapp.org,lineup.caleydoapp.org,malevo-daily.caleydoapp.org,malevo.caleydoapp.org,ordino-daily.caleydoapp.org,ordino-retrieval.caleydoapp.org,ordino.caleydoapp.org,pathfinder.caleydoapp.org,stratomex.caleydoapp.org,taco.caleydoapp.org,taggle-fusion.caleydoapp.org,taggle-outdated.caleydoapp.org,taggle.caleydoapp.org,thermalplot.caleydoapp.org,tourguide-daily.caleydoapp.org,tourguide-ordino.caleydoapp.org,vega-gapminder.caleydoapp.org: see https://letsencrypt.org/docs/rate-limits/

Please see the logfiles in /var/log/letsencrypt for more details.

avoids that we need a new image for each website change