sqliteonlinecom/soe-postgres repository overview

⁠What is soe?

Soe - external module for accessing local and remote databases from SqliteOnline.com⁠

SQL Editor, any database from any device.

This docker PostgrSQL⁠ including an external module "SOE" to make it much easier to run a ready set. (without creating a complex file: via docker stack deploy or docker-compose).

⁠How to use PostgrSQL image

⁠Warning!

The connection is on localhost, so the password is not used!

To make password access work, fix the file pg_hba.conf, replace trust with md5

# "local" is for Unix domain socket connections only
local   all             all                                     md5
# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
local   replication     all                                     md5
host    replication     all             127.0.0.1/32            md5
host    replication     all             ::1/128                 md5

⁠How to use this image

docker run --name soe-postgres --rm -d -e POSTGRES_PASSWORD=my_secret_pw -e SOE_DB_ROOT=1 -p 8081:17321 sqliteonlinecom/soe-postgres

⁠Connecting to your database via SqliteOnline.com

You can check if the server settings are correct. http://localhost:8081/soe/test

Go to the SqliteOnline.com⁠ website and click the Owner DB button

• Url http://localhost:8081/soe/
• DB name postgres
• Login postgres
• Password my_secret_pw

⁠Using environment variables in soe configuration

• soe_path path (default: soe)
• soe_body_size limit on request length (default: 2097152)
• soe_timeout session time limit in minutes (default: 15)
• soe_row_limit limit the number of lines, unlimited - 0 (experimental feature) (default: 100000)
• soe_login_allow allow access to the database, only users from the list, via "SOE" (example: user1,user2,user3)
• soe_login_deny block users from the list to access the database via "SOE" (example: user1,user2,user3)
• soe_db_root allow the user root to access the database through "SOE". allow - 1, deny - 0 (default: 0)

⁠Where to Store Data

Create a data directory on a suitable volume on your host system, e.g. /my/own/datadir.

docker run --name soe-postgres --rm -d -e PGDATA=/var/lib/postgresql/data/pgdata -v /my/own/datadir:/var/lib/postgresql/data -e POSTGRES_PASSWORD=my_secret_pw -e SOE_DB_ROOT=1 -p 8081:17321 sqliteonlinecom/soe-postgres

The -e PGDATA=/var/lib/postgresql/data/pgdata -v /my/own/datadir:/var/lib/postgresql/data part of the command mounts the /my/own/datadir directory from the underlying host system as /var/lib/postgresql/data inside the container, where PostgrSQL by default will write its data files.

⁠Using nginx configuration (from remote server)

You can check if the server settings are correct. https://youdomain/soe/test

# replace nginx_path on you path name
location /soe/ {
   gzip on;
   gzip_comp_level 9;
   gzip_types application/json;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_pass http://127.0.0.1:8081⁠;
proxy_redirect off;
proxy_buffering off;
proxy_buffer_size 128k;
proxy_buffers 100 128k;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_next_upstream error timeout http_500 http_502 http_503 http_504;
proxy_connect_timeout 5s;
proxy_read_timeout 30s;
proxy_send_timeout 30s;
}

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.