That’s ok if it worked the first time. Not sure how this will go. If it happens use the name option with publish-new and make sure it’s a different name.
That will force a new history and avoid the GE exists problem.
Good luck!
That’s ok if it worked the first time. Not sure how this will go. If it happens use the name option with publish-new and make sure it’s a different name.
That will force a new history and avoid the GE exists problem.
Good luck!
its only a template i found on line but holly hell this is amazing
dweb open a7ddb192773ab609ea223008a31f572ef4493c6bbc71b996c2d0ef9d86ed335faf2f284527c051c3214b5d2b89388180
Did the moderators ever get a chance to move these to a new thread, that you know of?
I’d really like to continue the discussion with you, but under an on-topic banner.
They haven’t responded. Why don’t you start a new topic anyway and copy your question to it.
Why don’t you start a new topic anyway and copy your question to it
Done. Here.
I’ve published an update to dweb which includes the following:
dweb publish
will error right away if you accidentally try to publish-new when you mean publish-update (and vice versa). Thanks to @aatonnomicc for highlighting the need for this.dweb
uses PrivateArchive by default when publishing a website but can display websites published using either PublicArchive or PrivateArchive. This is because using PrivateArchive is cheaper and more efficient, but still leaves the data accessible if it is stored for public access.To install or update:
cargo install dweb-cli # Add --locked if that doesn't compile
To view the RESTful APIs:
dweb serve
Then, in another terminal:
dweb openapi-docs
I’m looking for feedback and requests from web devs on this topic: Web client devs - best way to do low level Autonomi REST APIs
Next I’ll be implementing Pointer, Scratchpad and then Vault REST APIs, so if you are interested in using those please let me know any requests on that topic.