Skip to content
flisk-shPublic

About

Personalised Flisk demo stacks generated by demo.flisk.sh, one branch per demo demo.flisk.sh

Resources

Stars

2 stars

Watchers

0 watching

Forks

Latest commit

 

History

1,120 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 

Repository files navigation

Flisk demos

Personalised Flisk demo stacks, one branch per demo (demo/<id>).

Each branch is generated by demo.flisk.sh when someone asks Grok for a demo on X: the stack is composed from the thread, scaffolded with the flisk CLI and checked with flisk config verify.

Get one for anyone: open https://demo.flisk.sh/<x-handle>/<what-they-build-in-dashes>, for example demo.flisk.sh/0xHxxe/solidity-dapp-contract-done. On X: @grok make a Flisk demo for @someone. Link format: demo.flisk.sh/<their-handle>/<what-they-build-in-dashes>

Each demo page shows the exact clone command for its branch. Run one:

git clone -b demo/<id> https://github.com/flisk-sh/demos.git <stack>-demo
cd <stack>-demo
npm install -g @flisk-sh/flisk
flisk doctor
flisk up

Generated files (.flisk/.flisk-out/, Tiltfiles) are not committed: flisk up writes them on your machine.

Flisk runs the stack locally on Docker + Tilt with live reload. It is not a deploy tool. Source: github.com/flisk-sh/flisk

About

Personalised Flisk demo stacks generated by demo.flisk.sh, one branch per demo demo.flisk.sh

Resources

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages