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
In the future we plan to provide benchmarks using fakedatafs and a table to sort by the tag categories.
i have looked in the latter, and it seems to me the simplest solution would be to have one page per backup software and use some sort of page metadata to enumerate which tags apply to which page. this would probably imply the use of a static site generator.
having one page per software would also allow those page to feature benchmarks and other data about the tools.
i haven't reviewed the SSG alternatives in detail, but here's the one i thought would be worth mentioning:
Jekyll: Ruby, builtin to Github pages, which avoids committing HTML to git, but tags are not well supported which forces committing HTML to git in the end
Ikiwiki: Perl, doesn't support github pages out of the box, crude support for tags, which are pages you link to, limited filtering support
Also note that Gitlab pages support any arbitrary SSG, not just Jekyll, which may make deployment easier because it doesn't require committing rendered content into git - it's just part of the regular CI system.
The text was updated successfully, but these errors were encountered:
the TODO currently states:
i have looked in the latter, and it seems to me the simplest solution would be to have one page per backup software and use some sort of page metadata to enumerate which tags apply to which page. this would probably imply the use of a static site generator.
having one page per software would also allow those page to feature benchmarks and other data about the tools.
i haven't reviewed the SSG alternatives in detail, but here's the one i thought would be worth mentioning:
Also note that Gitlab pages support any arbitrary SSG, not just Jekyll, which may make deployment easier because it doesn't require committing rendered content into git - it's just part of the regular CI system.
The text was updated successfully, but these errors were encountered: