Better documentation

[WilhelmStein]

As it stands, the current documentation makes it rather hard to understand how to operate the cli. For example, it is not apparent how one is supposed to upload missing source files in order to trace blockchain transactions found through the site's explorer.

Some examples would be very helpful and would better illustrate the usefulness of this tool.

[BogdanHabic]

Hey @WilhelmStein, I couldn't agree more: the current documentation is far away from stellar.

We're working on a documentation website that will cover the CLI, the dashboard, and the API. Once that is live, it will be much more straightforward how to add missing source files, export transactions, etc.

[stoplion]

+1 to this

[robert-e-davidson3]

Would also be nice to know what it wants when I get this message:

Couldn't detect provider directory structure. This can be caused by:
• The directory is not set correctly. If this is the case, either check if you are in the right directory or pass an alternative directory by using the --project-dir flag.
• Tenderly is having trouble reading the directory correctly. If you think this is the case, rerun this command with the --force flag.

Is there a spec somewhere for how to lay out a directory in a way that tenderly will understand?

[BogdanHabic]

Hey @robert-e-davidson3,

Tenderly supports Hardhat, OpenZeppelin SDK, Truffle, and Hardhat Deploy directory structures out of the box.

Are you using any of these frameworks?

[samlaf]

@BogdanHabic I am in a hardhat directory and getting the very same error as @robert-e-davidson3 was getting.

[jrocco2]

@BogdanHabic I'm also pulling a fresh hardhat template (advanced with typescript) and running tenderly init and hitting this error

[jrocco2]

I also just tried it with the basic template and i got the same problem

[ghost]

I am still getting the same problem

[Riphal]

Can you go through these guide steps and say if that works for you?

[stevieraykatz]

This appears to be a symptom of a missing ./deployments dir in a project repo when initializing from scratch. By creating an empty deployments dir this error went away.

[ferencdg]

deployments

thank you! It is ridiculous that tenderly doesn't fix this.