Difference between revisions of "Nhmbif"
From nhm.sfs.gbif
(Tag: Visual edit) |
|||
Line 10: | Line 10: | ||
* [https://data.gbif.no/dwcexcel/ Generate your own DwC templates] | * [https://data.gbif.no/dwcexcel/ Generate your own DwC templates] | ||
* [https://data.gbif.no/repatriated/ Norwegian GBIF data from nodes outside Norway] (updated every month) | * [https://data.gbif.no/repatriated/ Norwegian GBIF data from nodes outside Norway] (updated every month) | ||
− | * [https://data.gbif.no/ipt/ | + | * [https://data.gbif.no/ipt/ GBIF.no's IPT instance] |
− | * [https://data.gbif.no/resolver/ | + | * [https://data.gbif.no/resolver/ GBIF.no's resolver], and plzresolve, which parses a DwC-A and adds data to the resolver. |
* A MySQL server (hosting specify databases and some IPT datasets) | * A MySQL server (hosting specify databases and some IPT datasets) | ||
* dwclean, a script run every night. Grabs data from MUSIT, cleans it and delivers it to our IPT. | * dwclean, a script run every night. Grabs data from MUSIT, cleans it and delivers it to our IPT. |
Revision as of 09:19, 10 April 2017
nhmbif is a virtual machine running RHEL 7.3
Contents
List of services
The following services are provided on nhmbif (incomplete list):
- Dataset portals
- Annotation/transcription (dugnad)
- A simple geolocation service
- Generate your own DwC templates
- Norwegian GBIF data from nodes outside Norway (updated every month)
- GBIF.no's IPT instance
- GBIF.no's resolver, and plzresolve, which parses a DwC-A and adds data to the resolver.
- A MySQL server (hosting specify databases and some IPT datasets)
- dwclean, a script run every night. Grabs data from MUSIT, cleans it and delivers it to our IPT.
- sgraf (Don't know what this does but it has something to do with geology)
- ffserver and ffmpeg, for live streaming museum events
Renewing SSL certificates
We use dehydrated to renew the letsencrypt certificates for data.gbif.no. Everything should just happen automatically (on the 1st of every month), but if something goes wrong, simply run /opt/bin/renew to renew the certificates. This script will also concatenate privkey.pem and cert.pem so lighttpd can use the certificates. Remember to restart lighttpd!
Troubleshooting
Help, the IPT is down!!!
- Is tomcat running? If not, do service tomcat start
- Is lighttpd running? If not, do lighttpd -f /etc/lighttpd/lighttpd.conf