NephNET/docker-nginx-h5ai
NephNET
/
docker-nginx-h5ai
1
0
Fork 0
Code Issues Pull Requests Packages Activity

updated readme

This commit is contained in:
Daniel Wolf 2018-05-17 06:51:49 -04:00
parent d2ac2eaf98
commit d134fdd1cf
1 changed files with 3 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -4,22 +4,11 @@
# H5AI Docker
This docker runs the [H5AI](https://larsjung.de/h5ai/) web directory index. Just put files and
folders into the volume mapped to `/mnt/media` and they will be made accessible through the web
interface. For private files, you can either lock them down via the NGINX config (there's an
example that will hide files under /local/) or use a separate docker that is not publicly
accessible in the first place.
This docker runs the [H5AI](https://larsjung.de/h5ai/) web directory index. Just put files and folders into the volume mapped to `/mnt/media` and they will be made accessible through the web interface. For private files, you can either lock them down via the NGINX config (there's an example that will hide files under /local/) or use a separate docker that is not publicly accessible in the first place.
Configure it by editing `/_h5ai/private/conf/options.json` in the media volume. I suggest disabling
custom headers and footers as it will cause a lot of open_basedir errors in the PHP logs. Remember
to change the password because the info page might expose information about your server that you do
not want exposed.
Configure it by editing `/_h5ai/private/conf/options.json` in the media volume. I suggest disabling custom headers and footers as it will cause a lot of open_basedir errors in the PHP logs. **Remember to change the password** because the info page might expose information about your server that you do not want exposed.
Certbot (LetsEncrypt) is installed to handle obtaining SSL certs in case this is your only web
docker. If you plan on hosting multiple applications/dockers, though I suggest having one
[nginx-ssl](https://hub.docker.com/r/nephatrine/nginx-ssl/) docker that is publicly visible and
handles the SSL certs for all domains. That docker can then proxy all your other nginx dockers
which would actually be running on non-public IPs under plain HTTP.
Certbot (LetsEncrypt) is installed to handle obtaining SSL certs in case this is your only web docker. If you plan on hosting multiple applications/dockers, though I suggest having one [nginx-ssl](https://hub.docker.com/r/nephatrine/nginx-ssl/) docker that is publicly visible and handles the SSL certs for all domains. That docker can then proxy all your other nginx dockers which would actually be running on non-public IPs under plain HTTP.
## Settings