nextra VS osx-serial-generator

co-author here

we put in a lot of effort into our docs and we'd greatly appreciate any criticism or feedback! Langfuse is powerful but the docs should help beginners to quickly get started and then incrementally use more features.

docs are OSS, repo: https://github.com/langfuse/langfuse-docs

built using: https://github.com/shuding/nextra

However, this may just be due to the lack of proper documentation from the Nextra side of things (shoutout to Nextra though, regardless).

Nextra - Nextra is another option for creating documentation sites. While it might not be as well-known as Docusaurus, Nextra offers a modern and minimalist approach to building documentation. It is designed to be lightweight and user-friendly, making it a good choice for those who prefer a simple and clean documentation style. You can explore more about Nextra on their official website.

I have looked at https://nextra.site/ but that doesn't work with the app router yet. So I'm wondering if there's another alternative.

You could also have a look at Nextra. You can use mdx components to build your blog (including support for server-side fetching). I'm currently using their documentation template, but it seems they also have a blog template.

We write everything in Markdown, as it's the closest you'll get to a 'universal' format. Then, we use a static site generator to turn the docs into a website. Current projects are using Nextra for this. If you ever need to change site generators, you still have all the markdown docs and image files, so it's pretty easy to change.

https://nextra.site/ is nice

Today I found this tool for Next.js called Nextra. You can effortlessly create a blog post website or a documentation website. All you need is markdown. Simply export your markdown from Notion and utilize it with Nextra to enjoy all the cool features, including full-text search, syntax highlighting, dark/light mode, and even image support. Everything is generated at build time, making it a static website which is Blazingly fast. https://nextra.site/

easy way to find a valid number is too generate tons and verify them one by one on the apple website as said into the previous link of point 11 use this to generate: https://github.com/sickcodes/osx-serial-generator

You serial HAS to be invalid. There are some criteria that you should follow (it's only partially random), but all of the guides warn you that your generated serial should always result as invalid for Apple: otherwise it'd mean you just generated someone else's serial by accident. If you don't want to do it manually or following the standard guides, there are open source, safe utilities to generate one: https://github.com/sickcodes/osx-serial-generator . I can assure you that getting iServices to work is fairly easy, nowadays.

Here you go: https://github.com/sickcodes/osx-serial-generator and you also need Open Core Configurator or similar software to mount the hidden efi partition

I'm using this script to build the VMs, applying serial numbers and HW model generated with this script. The guests enroll over the hosts VPN and once they get the config profile installing machine certs I can get them on VPN directly, enroll, and start testing.

Link : https://github.com/sickcodes/osx-serial-generator

Generate Complete Sets of Serial Numbers for OS X-KVM, Docker-OS X, OpenCore\ (6 comments)

The code is relatively easy to read if you want to see: https://github.com/sickcodes/osx-serial-generator/blob/master/generate-unique-machine-values.sh