Skip to content

Commit 04c34fd

Browse files
Updating Remote Docs
1 parent bd1cc76 commit 04c34fd

File tree

1 file changed

+2
-22
lines changed

1 file changed

+2
-22
lines changed

docs/cmd-remote.md

Lines changed: 2 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -33,33 +33,13 @@ SSL Certificates
3333
https://localhost:8443/socket.io/socket.io.js
3434
```
3535

36+
<details><summary>Get Help</summary>
37+
3638
`localhost` certificates are kind of flakey, and you might see something like this, which is normal. Just click through that first time to `Always Trust` the certificate to avoid future headaches.
3739

3840
![Error](img/ssl-error.png "Error")
3941
![Error](img/ssl-error-accept.png "Error")
4042

4143
Once you've confirmed you can access the `socket.io.js` file in your browser, you are good to go.
4244

43-
You can also do this manually, if needed:
44-
45-
<details><summary>VIEW INSTRUCTIONS</summary>
46-
<p>
47-
48-
For MacOS you can do this:
49-
50-
```bash
51-
cd ./remote/ssl
52-
sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain sfcc-cli-ca.cer
53-
```
54-
55-
SSL Certs already created in `./remote/ssl`, but if they need to be created again, here is how it was done:
56-
57-
```bash
58-
cd ./remote/ssl
59-
openssl req -x509 -newkey rsa:2048 -out sfcc-cli-ca.cer -outform PEM -keyout sfcc-cli-ca.pvk -days 10000 -verbose -config sfcc-cli.cnf -nodes -sha256 -subj "/CN=sfcc-cli CA"
60-
openssl req -newkey rsa:2048 -keyout sfcc-cli-localhost.pvk -out sfcc-cli-localhost.req -subj /CN=localhost -sha256 -nodes
61-
openssl x509 -req -CA sfcc-cli-ca.cer -CAkey sfcc-cli-ca.pvk -in sfcc-cli-localhost.req -out sfcc-cli-localhost.cer -days 10000 -extfile sfcc-cli.ext -sha256 -set_serial 0x1111
62-
```
63-
64-
</p>
6545
</details>

0 commit comments

Comments
 (0)