mirror of
https://github.com/sigmasternchen/ShellSpider
synced 2025-03-16 08:29:02 +00:00
readme + we now have a name
This commit is contained in:
parent
73a5498b83
commit
2a0571f4f4
2 changed files with 26 additions and 2 deletions
24
README.md
24
README.md
|
@ -1,2 +1,26 @@
|
|||
# ShellSpider
|
||||
A web-server in shell script
|
||||
|
||||
Why?
|
||||
====
|
||||
Because I can.
|
||||
|
||||
Requirements
|
||||
============
|
||||
- an up-to-date version of bash
|
||||
- socat (for networking)
|
||||
- python (for url-encoding)
|
||||
- some other basic tools, like sed, grep, awk, getopt
|
||||
|
||||
Usage
|
||||
=====
|
||||
|
||||
```
|
||||
./server.sh --port=[PORT]
|
||||
```
|
||||
|
||||
For other options start the script without the port-option.
|
||||
|
||||
Why again?
|
||||
==========
|
||||
I did this just for fun. I wanted to reach the limits of shell scripts. Turned out: Building a fully functional webserver is possible.
|
||||
|
|
|
@ -8,7 +8,7 @@ progname="server"
|
|||
|
||||
help() {
|
||||
cat << EOF
|
||||
usage: $progname --port=PORT
|
||||
usage: $progname [OPTIONS] --port=PORT
|
||||
|
||||
Options:
|
||||
-p, --port=PORT set port
|
||||
|
@ -56,7 +56,7 @@ declare -A settings
|
|||
settings[home]=$home
|
||||
settings[verbose]=$verboselevel
|
||||
settings[executeable]="sh php py cgi"
|
||||
settings[server]="server"
|
||||
settings[server]="ShellSpider V1"
|
||||
settings[index]="true"
|
||||
declare -p settings > $settingsfile
|
||||
|
||||
|
|
Loading…
Reference in a new issue