Skip to content
This repository

If Twitter is a 'command-line social network', then Scriptus is shell scripting.

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 docs
Octocat-spinner-32 misc
Octocat-spinner-32 scripts
Octocat-spinner-32 src
Octocat-spinner-32 .gitignore
Octocat-spinner-32 LICENSE
Octocat-spinner-32 README.md
Octocat-spinner-32 datastore_transport_interaction.ucls
Octocat-spinner-32 pom.xml
Octocat-spinner-32 scriptus.notes
Octocat-spinner-32 scriptus.todo
Octocat-spinner-32 spellcheck.sh
README.md

Scriptus is a way of programming interactions between people. What's new is that these interactions can be complicated and span days, weeks, months or years: elections, chess tournaments and games are all easy to create.

A simple example:

var task = ask("What to do?");

sleep("1d");//1 day

var response;

do {

  response = ask("did you do "+task+" yet?", {timeout:"1d"});

} while( response != "Stop it!" | "yes");

It's easy to get started. Scriptus programs interact with people via Twitter and has a simple UNIX-like process model.

On Twitter, people are asked questions using @mentions. Responses are sent back to Scriptus by replying to the tweets sent out. Anything after "//" will be ignored. For example:

@ianso electing HOW many presidents-for-life?!
[the reply] @robotoscriptu 4 //but I can depose them whenever I want!

A Scriptus server can be stopped at any time. Programs will continue where they left off when it is started again.

You will need JDK 6 or more recent. Download Scriptus here and then launch it using this command

java -jar scriptus.war

Scriptus will immediately start at http://127.0.0.1:8080/. You can change the port using the -p option.

The Scriptus minisite includes a blog + RSS feed for notable updates. The user guide documents how to run Scriptus, and the API documentation shows how to use it. More is available at the documentation index.

The license is GPL v2 or above.

Something went wrong with that request. Please try again.