• r

    rp

    1 year ago
    perhaps @User can help you with this.
  • ?

    user

    1 year ago
    Oh one sec.
  • ?

    user

    1 year ago
    Okay I got it.
  • ?

    user

    1 year ago
    If anyone else wants to use docker-compose to run their own postgres container + supertokens container all in one network, here is my docker-compose file for reference:
  • ?

    user

    1 year ago
    yaml
    //docker-compose.yml
    version: '3'
    
    services:
      database:
        image: postgres
        restart: always
        ports:
          - '5432:5432'
        environment:
          POSTGRES_USER: postgres
          POSTGRES_PASSWORD: pass123
          POSTGRES_DB: my_db
    
      supertokens:
        image: supertokens/supertokens-postgresql
        restart: always
        ports: 
          - '3567:3567' 
        environment:
          POSTGRESQL_USER: postgres
          POSTGRESQL_PASSWORD: pass123
          POSTGRESQL_HOST: database
          POSTGRESQL_PORT: 5432
          POSTGRESQL_DATABASE_NAME: my_db
  • ?

    user

    1 year ago
    Keep in mind you are publishing your ports here. Remove those if you want the containers to be contained within your network in production
  • r

    rp

    1 year ago
    thanks! the issue was the value of
    POSTGRESQL_DATABASE_NAME
    ?
  • ?

    user

    1 year ago
    Yes I forgot that it was referencing the name of the
    database
  • ?

    user

    1 year ago
    I mixed up
    database
    and
    tables
    for a second
  • r

    rp

    1 year ago
    ah okay!