Web Editor for SQLITE

I received a potentially nice tip from Mr Shark today – a web editor for SQLITE (as against PHPLITEADMIN which is not Web based and uses PHP). Beware I found some kind of timeout, the author agreed this was likely some kind of timeout, then closed the issue on Github without doing anything. Not sure what that means.

tmpFCD6

sudo pip install --upgrade pip
sudo pip install sqlite-web
sqlite_web -H 0.0.0.0 -x –P dbs/iot.db

Where 0.0.0.0 is the IP address of the machine with SQLITE on it (otherwise the editor defaults to localhost so you can access the DB from the board itself.

Change that to the IP address of your SQLITE installation.

The software uses port 8080 by default, To use instead for example port 89…on internal address  192.168.1.19

sudo sqlite_web -H 192.168.1.19 -x -p 89 -P dbs/iot.db

If using port under 1024 you need to run with sudo/

If you want to pass the password as an environment variable:

SQLITE_WEB_PASSWORD=mypass

sudo SQLITE_WEB_PASSWORD=mypass /usr/local/bin/sqlite_web -H 0.0.0.0 -x -P -p 89 /home/pi/dbs/iot.db

 

If you’re planning to use this a lot, it can be installed as a service, right now it holds up that user session and you break out with control-C.

Looks good. https://github.com/coleifer/sqlite-web

Facebooktwittergoogle_pluspinterestlinkedin

4 thoughts on “Web Editor for SQLITE

  1. Peter, please add a link to original github project: https://github.com/coleifer/sqlite-web

    look there to see the variable you can set to avoid giving password twice every time you want to use it... i asked the author today and he added the option in about a couple of hours: https://github.com/coleifer/sqlite-web/issues/49

    in case in your system default sqlite-web http port (8080) is in use, change it using the -p switch... for example:
    sqlite_web -H 0.0.0.0 -p 81 -x -P dbs/iot.db

    then just point your browser to your SBC ip and port: http://ip:port

    in case we can convert this to a service, running at boot... as i don't need to edit sqlite db so often, i just created an alias to run it, and kill it once done... no need to abuse poor ram...

  2. It is a very nice utility - thanks for the heads up. As I have multiple databases which require multiple instances on different ports of this utility (if you want them running as the same time), I found the most practical method was to add 2 buttons per database on the node red dashboard tab I use for system diagnostics. These link to exec nodes - one to initiate sqlite_web on the required database and one to kill it using "sudo pkill sqlite_web".

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.