Fix the remaining broken links on fbflipper.com
Summary: Used https://www.brokenlinkcheck.com/broken-links.php#status for now to find broken links and fixed them all. Would be better to use some automated tool to check this at diff time, but that's not setup yet. Reviewed By: passy Differential Revision: D21301702 fbshipit-source-id: f13c8769b15d9f99563fc65dc0544320d07a2bfb
This commit is contained in:
committed by
Facebook GitHub Bot
parent
f1abd8a4a4
commit
7e4682b694
@@ -60,4 +60,4 @@ This will ask Flipper desktop to generate a client certificate, using the CSR pr
|
||||
|
||||
Depending on the client, `destination` can have a different meaning. A basic example would be a file path, that both the desktop and the client have access to. With this Flipper desktop could write the certificate to that path. A more involved example is that of the Android Client, where destination specifies a relative path inside an app container. And the Subject Common Name determines which app container. Together these two pieces of information form an absolute file path inside an android device.
|
||||
|
||||
For Flipper desktop to work with a given Client type, it needs to be modified to know how to correctly interpret the `destination` argument, and deploy certificates to it. You can see the current implementations in [CertificateProvider.tsx](https://github.com/facebook/flipper/blob/master/desktop/src/utils/CertificateProvider.tsx).
|
||||
For Flipper desktop to work with a given Client type, it needs to be modified to know how to correctly interpret the `destination` argument, and deploy certificates to it. You can see the current implementations in [CertificateProvider.tsx](https://github.com/facebook/flipper/blob/master/desktop/app/src/utils/CertificateProvider.tsx).
|
||||
|
||||
Reference in New Issue
Block a user