#Pretty cool indeed!

1 messages · Page 1 of 1 (latest)

inner spruce
# 
~ ➤ /Library/PostgreSQL/16/scripts/runpsql.sh; exit                            
Server [localhost]: 
Database [postgres]: 
Port [5432]:  
Username [postgres]:    
Password for user postgres: 
psql (16.3)
Type "help" for help.

postgres=# \dn+
postgres=# \dn
      List of schemas
  Name  |       Owner       
--------+-------------------
 public | pg_database_owner
(1 row)

postgres=#
topaz root
#

nice 🙂

inner spruce
#

https://docs.dagger.io/manuals/user/053831/host-services/

dagger -m github.com/kpenfound/dagger-modules/postgres@v0.1.0 call client --db=postgres --user=postgres --password=postgres --server=tcp://localhost:5432

learning from implementation of 👆 open in another shell after creating postgres db previously

core container \
from --address postgres:latest \
with-service-binding --alias mydb --service tcp://localhost:5432 \
with-default-terminal-cmd --args psql,postgresql://postgres:postgres@mydb \
terminal
Host Services Access | Dagger

Dagger Functions do not have access to the network of the host you invoke the Dagger Function from (i.e. the host you execute a CLI command like dagger call from). Instead, host network services need to be explicitly passed when executing dagger call.