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
User interface (already implemented, but left here as reference)
Only one init file (was: .pow file) is provided to kapow server. If more are needed, they chan trivially included via the shell trick <(cat *.pow), or, from within the .pow file with a source.
The output of the --help should look something like:
Usage: kapow [OPTIONS] COMMAND [ARGS]...
Start aiohttp app.
Options:
--help Show this message and exit.
Commands:
route Manage current server HTTP routes
server Start a Kapow! server
read Get data from the current context (GET)
write Append data from the current context (POST)
set Set data from the current context (PUT)
delete Remove data from the current context (DELETE)
@nilp0inter, (no hurries at all!), can you review the contents of this issue sometime to ensure that they match your original email? Domo!
The text was updated successfully, but these errors were encountered:
KAPOW_URL
is split intoKAPOW_DATA_URL
andKAPOW_CONTROL_URL
.--url
param present in some commands is also split in two:--data-url
and--control-url
kapow set
tokapow write
, in order to better hint that no overwriting is done.kapow get
tokapow read
.kapow set
, which will overwrite the content of the given resource .kapow delete
, which will remove the content of the given resource.index
in favour ofID
. This precludes any chance of race conditions ocurring.kapow route
subcommands withiptables
's syntax:add
replaced by--append | -A
remove
replaced by--delete | -D
list
replaced by--list | -L
frobnicate
replaced by--dont-cross-the-streams | -X
.pow
file) is provided tokapow server
. If more are needed, they chan trivially included via the shell trick<(cat *.pow)
, or, from within the.pow
file with a source.The output of the
--help
should look something like:@nilp0inter, (no hurries at all!), can you review the contents of this issue sometime to ensure that they match your original email? Domo!
The text was updated successfully, but these errors were encountered: