HelloZeroNet / HelloZeroNet/ZeroNet

zeronet zite upload glitches

オープン
#805 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
JavaScript
スター
18.8k
フォーク
2.3k
PR マージ指標
30日以内にマージされた PR はありません

説明

these are not previously mentioned.
for someone with a "dynamic" site like jekyll which simulates wp, one has to re-up the site changes over time to keep up with posts and such. normally not an issue here. what is the issue however, that zeronet resigns the json file every time. Any changes here get ignored. So like if you setup "media" or "optional" content, on each upload then you simply cannot reset that information-the file gets resigned every time.

furthermore this complicates things. If you have a "name" for your site and want to use it, that too gets overridden. You have to re-save it via the zero ui every time. This simply is too much work for changing sites. If your sites doesnt change, you dont have traffic. It will drop off the net.

If your zite is huge you have two options: torrent files everywhere or everyone hosts a huge website, which for jekyll in most cases is a waste. Jekyll sites themselves are not yuge(<10mb), the "optional content" MAY be.

I need a solution.

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

調査の方向性

No source file, test, or concrete entry point is named. Start by tracing the zite upload and JSON-resigning flow described in the report, then reproduce a re-upload of a changing Jekyll site. Done means re-uploads preserve the site's optional or media settings and its name without requiring manual Zero UI changes.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
jekyll
領域
distributed-systems
issue の種類
バグ
難易度
5/5
見積もり時間
1週間以上
活発さ
停滞
明瞭さ
説明が足りない
初心者へのやさしさ
20/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。