Skip to content

Add possibility to configure sessions over dsn #348

@alexander-schranz

Description

@alexander-schranz

I would think it would be great to configure sessions over DSN.

Currently a config for doctrine_dbal looks like the following in sulu:

    sessions:
        default:
            backend:
                type: doctrinedbal
            workspace: "%env(PHPCR_WORKSPACE)%"
        live:
            backend:
                type: doctrinedbal
            workspace: "%env(PHPCR_WORKSPACE)%_live"

And config for jackrabbit look like this in sulu:

parameters:
    env(JACKRABBIT_URL): 'http://localhost:8080/server/'
    env(PHPCR_USER): 'admin'
    env(PHPCR_PASSWORD): 'admin'

# ...
    sessions:
        default:
            backend:
                type: jackrabbit
                url: "%env(JACKRABBIT_URL)%"
            workspace: "%env(PHPCR_WORKSPACE)%"
            username: "%env(PHPCR_USER)%"
            password: "%env(PHPCR_PASSWORD)%"
        live:
            backend:
                type: jackrabbit
                url: "%env(JACKRABBIT_URL)%"
            workspace: "%env(PHPCR_WORKSPACE)%_live"
            username: "%env(PHPCR_USER)%"
            password: "%env(PHPCR_PASSWORD)%"

So the dsn can be very different I think, currently I would go with something like:

PHPCR_DSN=doctrindbal://default
PHPCR_DSN=jackrabbit://admin:admin@localhost:8080/server/?workspace=default

Which can be configured this way:

    sessions:
        default:
            dsn: "%env(PHPCR_DSN)%"

I'm not sure about the jackrabbit format and if jackrabbit can be behind https?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions