📓 TikBook™ — notebook and tools for Visual Studio Code, including RouterOS LSP

[Amm0]

I plan on release a new version of TikBook at some point. The main feature will be allow saving of "outputs" in the .rsc.md (or .md.rsc) and some better CoPilot support, and other small things. And, even more support for code-server edition.

But some updates on the project:

TikBook Example... Self Signed Certificate to Apple Devices

I actually use my own plugin, so I wrote an real-world example in another post:

Example: Creating self-signed certificates, including Apple `.mobileconfig`, using TikBook

This comes up from a discussion in the 7.22beta thread, mainly with @wfbuton on creating "self-signed wildcard certificates". But it test of using reverse-proxy to run VSCode for Web (code-server) in /app container, using my [TikBook notebook extension], to then test creating wildcard certs. And also add a function to create an Apple Profile (.mobileconfig) that can be used to install root certificate into iOS (or any Apple platform) that could be used elsewhere. Since "how to use with apple…

VS Code for Web & RouterOS /app...

In RouterOS 7.21, MikroTik include code-server as installable container via /app. This is actually "VS Code for Web"... so you can now run TikBook on RouterOS (via code-server container).

This avoids some of the CORS issue that make using https://vscode.dev or https://GitHub.dev very difficult. Since code-server runs on same IP, CORS rules are mostly met, so using the web version with TikBook's REST API calls is much easier. In RouterOS 7.22, MikroTik adds a reverse-proxy which allows TLS/SSL on code-server and TikBook fully works when using 7.22 with reverse-proxy.

As RouterOS 7.22 further develops, I'll writeup how to use it better. But this post has current details:

V7.22beta [development] is released!

Re IDK. Perhaps a reboot, perhaps DNS...IDK what fixed it. Maybe it was the builtin trust store not actually being trusted — despite setting as =all. This was a fresh CHR and all is default value, so should have applied it. But, yes, I got SNI matching working as expected using FQDN matching cert's CN and/or SAN. I can do one better: a RouterOS notebook using /app and reverse-proxy.... This was my main test case for /app. I used the code-server container since I wanted to see if it a…