If preferred, gist.cafe can be run locally where teams can share and run their secret gists faster on their own servers by running our docker image
Then create a gistcafe container with external links to your local instance:
--security-opt flag only required for running swift
That can now be launched with:
To update, remove your container and pull the latest version, then recreate it:
Tip: to enable all team members to update the same gists, have them use a shared gist GitHub Access Token in their GITHUB_TOKEN Environment Variable.
The least invasive way of trying out all popular languages is to run the servicestack/gistcafe Docker image in VS Code's Docker Extension:
After right-clicking on the running container and clicking on Attach Visual Studio Code you'll open a VS Code window into the running instance at the users /app home directory. To start with a clean folder free of clutter, you can run code src to open a new VS Code window into the empty src folder.
To quickly get started playing with each language use the built-in x tool to download any GitHub repo.
To make it easy, gistcafe has a hello-* repo for each language that supports running a single source file "Hello World" which you can browse with:
Then download the language you want, e.g you can download & run a Deno "Hello World" App with:
For installing all other non-single file (i.e. hello-*) repos you'll instead want to use x new so it applies all project transformations with your Project Name:
Once you're ready to share your new App with the world you can publish it to a GitHub Gist by generating a GitHub Access Token with gist scope and adding it to your GITHUB_TOKEN Environment Variable:
Then to publish your App to a new Gist, run:
if -desc is unspecified the description is inferred from your folder name.
To update your Gist run publish again:
This will create a basic C# Console App you can run locally with:
To help quickly visualize your program output, the referenced ServiceStack.Common
lib includes .PrintDump() and .PrintDumpTable()
dump utils
to dump objects to the console.
Whilst Inspect.vars() saves objects you can inspect in the UI after the Gist is run.
To help quickly visualize your program output, the referenced gistcafe
package includes Inspect.printDump() and Inspect.printDumpTable()
utils to dump objects to the console.
Whilst Inspect.vars() saves objects you can inspect in the UI after the Gist is run.
To help quickly visualize your program output, the referenced gistcafe-go
package includes inspect.PrintDump() and inspect.PrintDumpTable()
utils to dump objects to the console.
Whilst inspect.Vars() saves objects you can inspect in the UI after the Gist is run.
To help quickly visualize your program output, the referenced gistcafe
package includes inspect.printdump() and inspect.printdumptable()
utils to dump objects to the console.
Whilst inspect.vars() saves objects you can inspect in the UI after the Gist is run.
To help quickly visualize program output, the net.servicestack.gistcafe
package includes Inspect.printDump() and Inspect.printDumpTable()
utils to dump objects to the console.
Whilst Inspect.vars() saves objects you can inspect in the UI after the Gist is run.
To help quickly visualize program output, the net.servicestack.gistcafe
package includes Inspect/printDump and Inspect/printDumpTable
utils to dump objects to the console.
Whilst Inspect/vars saves objects you can inspect in the UI after the Gist is run.
To help quickly visualize program output, the gistcafe
gem includes Inspect.print_dump and Inspect.print_dump_table
utils to dump objects to the console.
Whilst Inspect.vars saves objects you can inspect in the UI after the Gist is run.
To help quickly visualize program output, the gistcafe
package includes Inspect::printDump and Inspect::printDumpTable
utils to dump objects to the console.
Whilst Inspect::vars saves objects you can inspect in the UI after the Gist is run.
To quickly visualize program output, the gistcafe::inspect
module includes print_dump, print_dump_table & print_dump_table_columns
utils to dump objects to the console.
Whilst inspect::vars saves objects you can inspect in the UI after the Gist is run.
To quickly visualize program output, the gistcafe hex package
includes Inspector.print_dump and Inspector.print_dump_table
utils to dump objects to the console.
Whilst Inspector.vars saves objects you can inspect in the UI after the Gist is run.
#Script is a simple, fast, highly versatile and embeddable scripting language for .NET Apps that utilizes a familiar JavaScript inspired Syntax to enable dynamic scripting of .NET Apps via controlled access to pluggable methods and arguments within a sandbox environment - making it ideal for use-cases like content-heavy websites, live documents, Email Templates and can easily introspect the state of running .NET Apps where they provide valuable insight at a glance - all the way to creating Windows Desktop Apps.
Embedded in the x tool & requiring no compilation or build tools it's watch mode makes it ideal for live explorative literate programming:
For a quick glance of Live programming in motion check it out on YouTube:
#Script Lisp is a scripting language built into the x tool that can script .NET Apps and be seamlessly embedded into #Script code. It has a large built-in library sporting 1000+ extensible Script Methods as well as implementing most of the Simplified Common Lisp Reference and for improved readability and familiarity also adopts a number of Clojure syntax for defining a data list and map literals, anonymous functions, syntax in Java Interop for .NET Interop, keyword syntax for indexing collections and accessing index accessors and Clojure's popular shorter aliases for fn, def, defn - improving source-code compatibility with Clojure.
Like all lisps, it's ideal for usage in a REPL on both the command-line as well as being able to open a REPL session into a remote ServiceStack instance where it's able to inspect and invoke functionality of a Live running .NET App instance:
It's watch mode makes it well suited for live explanatory programming with instant feedback after each save:
It's built in methods lets you run shell scripts, query databases, explore both local and remote S3 file systems, query HTTP APIs, etc:
The x dotnet tool lets you easily create console apps & upload them to gists.
To create gists you'll need to generate a GitHub Access Token with gist scope and add it to your GITHUB_TOKEN Environment Variable (win, mac, linux). (alternative: use -token arg in each publish command)
Then to publish your App to a new Gist, run:
if -desc is unspecified the description is inferred from your folder name.
To update your Gist run publish again:
{title} by @{user} on gist.cafe.