Updated aiotunnel scripts call

Dockerfile

@@ -4,4 +4,4 @@ COPY requirements.txt /aiotunnel
 RUN pip install -r /aiotunnel/requirements.txt --no-cache-dir
 ADD . /aiotunnel
 WORKDIR /aiotunnel
-CMD python aiotunnel.py server -r
+CMD aiotunnel server -r

README.md

@@ -22,7 +22,7 @@ So just run the `tunneld` on the server at `10.5.0.10` (you probably'll want to
 NOHUP or by creating a systemd service) in reverse mode:
 
 ```sh
-[email protected]:~$ python aiotunnel.py server -r
+[email protected]:~$ aiotunnel server -r
 ======== Running on http://0.0.0.0:8080 ========
 (Press CTRL+C to quit)
 ```
@@ -31,7 +31,7 @@ On the target machine at `10.5.0.240` run the client bound to the service we wan
 this case but could be anything):
 
 ```sh
-[email protected]:~$ python aiotunnel.py client --server-addr 10.5.0.10 --server-port 8080 -A localhost -p 22 -r
+[email protected]:~$ aiotunnel client --server-addr 10.5.0.10 --server-port 8080 -A localhost -p 22 -r
 [2018-10-14 22:20:45,806] Opening a connection with 127.0.0.1:22 and 0.0.0.0:8888 over HTTP
 [2018-10-14 22:20:45,831] 0.0.0.0:8888 over HTTP to http://10.5.0.10:8080/aiotunnel
 [2018-10-14 22:20:45,832] Obtained a client id: aeb7cfc6-3de3-4bc1-b769-b81641d496eb
@@ -61,25 +61,25 @@ communicate with him by using HTTP requests:
 So on our known server located at `10.5.0.10` we start a `tunneld` process
 
 ```sh
-[email protected]:~$ python aiotunnel.py server
+[email protected]:~$ aiotunnel server
 ======== Running on http://0.0.0.0:8080 ========
 (Press CTRL+C to quit)
 ```
 
 On the network-constrainted machine we start a `tunnel` instance
 
 ```sh
-[email protected]:~$ python aiotunnel.py -A 10.0.5.240 -P 22
+[email protected]:~$ aiotunnel -A 10.0.5.240 -P 22
 [2018-10-15 00:58:41,744] Opening local port 8888 and 10.0.5.240:22 over HTTP
 ```
 And we're good to go.
 
 It's possible to use the `Dockerfile` to build an image and run it in a container, default start
-with a command `python aiotunnel.py server -r`, easily overridable.
+with a command `aiotunnel server -r`, easily overridable.
 
 ```sh
 [email protected]:~$ docker build -t aiotunnel /path/to/aiotunnel
-[email protected]:~$ docker run --rm --network host aiotunnel python aiotunnel.py client --server-addr 10.5.0.10 --server-port 8080 -A localhost -p 22 -r
+[email protected]:~$ docker run --rm --network host aiotunnel aiotunnel client --server-addr 10.5.0.10 --server-port 8080 -A localhost -p 22 -r
 ```
 
 ### Security
@@ -88,15 +88,15 @@ [email protected]:~$ docker run --rm --network host aiotunnel python aiotunnel.py c
 to encrypt the communication and use HTTPS (defaulting on port 8443 instead of 8080)
 
 ```sh
-[email protected]:~$ python aiotunnel.py server -r --ca /path/to/ca.crt --cert /path/to/cert.crt --key
+[email protected]:~$ aiotunnel server -r --ca /path/to/ca.crt --cert /path/to/cert.crt --key
 /path/to/keyfile.key
 ======== Running on https://0.0.0.0:8443 ========
 ```
 
 And client side
 
 ```sh
-[email protected]:~$ python aiotunnel.py client -A 127.0.0.1 -P 22 --ca /path/to/ca.crt --cert
+[email protected]:~$ aiotunnel client -A 127.0.0.1 -P 22 --ca /path/to/ca.crt --cert
 /path/to/cert.crt --key /path/to/keyfile.key
 [2018-10-18 22:20:45,806] Opening a connection with 127.0.0.1:22 and 0.0.0.0:8888 over HTTPS
 [2018-10-18 22:20:45,831] 0.0.0.0:8888 over HTTPS to https://10.5.0.10:8443/aiotunnel

aiotunnel.py → scripts/aiotunnel

@@ -1,3 +1,5 @@
+#!/usr/bin/env python
+
 from aiotunnel.cli import main
 
 

setup.py

@@ -14,5 +14,5 @@
     author_email='[email protected]',
     packages=['aiotunnel'],
     install_requires=required,
-    scripts=['aiotunnel.py']
+    scripts=['scripts/aiotunnel']
 )