Each external program trying to access the API will need its own access key, which is the familiar 64-character hexadecimal used in many places in hydrus. Once the API is running, go to its entry in services->review services. from Let's Encrypt), you can overwrite the client.crt and client.key files in your 'db' directory and HTTPS hydrus should host with those. If you have a way of hosting a domain and have a signed certificate (e.g. You'll need a static IP or reverse proxy service or dynamic domain solution like so your device can locate it, and potentially port-forwarding on your router to expose the port. If you want to talk to your home computer across the internet, you will need some networking experience. The Client API is still experimental and sometimes not user friendly. your web browser looking at ) may need to add an exception. You can turn on HTTPS, but due to technical complexities it will give itself a self-signed 'certificate', so the security is good but imperfect, and whatever is talking to it (e.g. your computer's web browser talking to your computer's hydrus), but not secure for transmission across the internet (e.g. By default, the Client API is HTTP, which means it is ok for communication on the same computer or across your home network (e.g. To test it is running all correct (and assuming you used the default port of 45869), try loading this: It will only be active while the client is open. only requests from the same computer will work) to start with. I recommend you not allow non-local connections (i.e. Go to services->manage services and give it a port to get it started. Enabling the API ¶īy default, the Client API is not turned on. The hydrus client now supports a very simple API so you can access it with external programs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |