You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your instructions ask to clone the 1BLog... site. But users should be able to install from git too, because that's how software is usually installed. There are also problems in instructions like there is no file default.json-default that instructions mention.
I am trying to write a script to clone from git, but it fails for unclear reason. zeronet siteSign skips data/users/content.json for some reason.
I think you need to make instructions to create a new blog easier, and they should start from "git clone". It is best to have a script cloning the github repository. You probably also want to remove "domain": "Blog.ZeroNetwork.bit" from contents.json because only you own it, and most people probably will not register a domain.
The text was updated successfully, but these errors were encountered:
Yes, zeronet.py siteSign {address} --inner_path data/users/content.json was missing.
So it would be great if ZeroBlog page had accurate instructions including that one command. I think siteSign should also replace "address" in content.json, and instructions should look like this:
Your instructions ask to clone the 1BLog... site. But users should be able to install from git too, because that's how software is usually installed. There are also problems in instructions like there is no file default.json-default that instructions mention.
I am trying to write a script to clone from git, but it fails for unclear reason. zeronet siteSign skips data/users/content.json for some reason.
I think you need to make instructions to create a new blog easier, and they should start from "git clone". It is best to have a script cloning the github repository. You probably also want to remove "domain": "Blog.ZeroNetwork.bit" from contents.json because only you own it, and most people probably will not register a domain.
The text was updated successfully, but these errors were encountered: