Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cardano Operations Book: discussion, how to link there
See original GitHub issueSomeone just referenced this site from the CIP repository today: https://book.world.dev.cardano.org
Also titled the Cardano World Repository, it’s still pretty empty but appears to be coming from an official source and has some information that’s hard to find documented anywhere else (e.g. the new networks evolved from the Testnet that I’ve only seen documented informally so far).
The currently mostly greyed-out page outline has some overlap with the material here in the Dev Portal (cardano-wallet, Ogmios). More generally I was wondering if anyone knows about its development plan & timeline, and can post ideas about it here, in the hope when ready that this will be properly introduced on & linked from the Dev Portal.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I also think the “juicy stuff” is on https://book.world.dev.cardano.org/environments.html we can just link that.
I think the original intention of that site was to include a lot more information, but IMO - the current state (except index) is good, it shouldn’t onboard more as it will likely have yet another overlap with instructions on : dev portal (community maintained), docs.cardano.org (IO maintained), github repo of components (readme.md+docs folder) and other community sites (eg: coincashew) for step-by-step instructions. The more the websites referenced, greater are chances of confusion/chaos/outdated (or different styles of information).
Instead, we could use the config/topology file/genesis/etc references as-is for downloads, but need to also be mindful of standards: For instance, P2P - while works - is still not production-ready (the n2n versions are still changing), might not be best idea to include default templates with P2P turned on. But given that it’s only enabled on non-mainnet networks, except preprod (supposed to replicate mainnet) - other networks having that config might be OK.
Additionally, preprod/preview networks are both supposed to be reset soon, and we should be having a new community initiated testnet as well.
With the above changes upcoming, I would prefer if we could defer changes for now - until there is clearer picture in coming weeks