Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Republishing IPNS #1810

Open
Ludwintor opened this issue Feb 10, 2024 · 1 comment
Open

Republishing IPNS #1810

Ludwintor opened this issue Feb 10, 2024 · 1 comment
Labels
need/triage Needs initial labeling and prioritization

Comments

@Ludwintor
Copy link

Ludwintor commented Feb 10, 2024

Hi. I use guide at http://docs.ipfs.tech.ipns.localhost:8080/how-to/publish-ipns/#publishing-ipns-names-with-kubo and faced a problem that when I first time publish IPNS to points at CID of ipfs files stat / it works well but when I add new file to root folder I publish IPNS with same key and new CID from ipfs files stat / it says that everything published but nothing changes. Going to IPNS still shows old folder and ipfs name resole <IPNS> shows that it still old CID.
After that I restarted a daemon and now IPNS points to CID what I wanted without republishing after restarting. Why IPNS updates it pointer only after restarting daemon?

@Ludwintor Ludwintor added the need/triage Needs initial labeling and prioritization label Feb 10, 2024
Copy link

welcome bot commented Feb 10, 2024

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additiona round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.tech if you just need general support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant