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
We should replace the current custom portal loop implementation with gnodev.
Gnodev should be user-friendly for those who want to showcase a preview of their work, including:
Us, the core team -> gno.land
Berty -> gno.berty.io
And others
Essentially, running gnodev with no arguments starts a default local-only server with development-friendly options, such as auto-reload and an in-memory store.
In contrast, gnodev staging or gnodev --various --flags --to --customize --it allows for running a portal loop in staging mode. This setup will feature a persistent store instead of an in-memory one, disable file system watching for auto-reload, and ensure that replayable transactions are stored in a format suitable for a Git repository, ideally in jsonl format.
cc @gfanton. But I believe this is a great opportunity to open this tool to more hands and minds. Is anyone interested in starting to improve gnodev?
The text was updated successfully, but these errors were encountered:
moul
changed the title
META gnodev to power portal loop(s)
Gnodev to power portal loop(s)
Sep 27, 2024
We should replace the current custom portal loop implementation with gnodev.
Gnodev should be user-friendly for those who want to showcase a preview of their work, including:
Essentially, running
gnodev
with no arguments starts a default local-only server with development-friendly options, such as auto-reload and an in-memory store.In contrast,
gnodev staging
orgnodev --various --flags --to --customize --it
allows for running a portal loop in staging mode. This setup will feature a persistent store instead of an in-memory one, disable file system watching for auto-reload, and ensure that replayable transactions are stored in a format suitable for a Git repository, ideally injsonl
format.cc @gfanton. But I believe this is a great opportunity to open this tool to more hands and minds. Is anyone interested in starting to improve gnodev?
The text was updated successfully, but these errors were encountered: