# Access to CloudSQL Postgres database using unix socket

**URL:** <https://community.forestadmin.com/t/access-to-cloudsql-postgres-database-using-unix-socket/450>\
**Category:** Help me!\
**Created:** [June 10, 2020, 9:16pm UTC](https://community.forestadmin.com/t/access-to-cloudsql-postgres-database-using-unix-socket/450 "2020-06-10T21:16:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![anon39848301](https://avatars.discourse-cdn.com/v4/letter/a/b9e5f3/32.png) [@anon39848301](https://community.forestadmin.com/u/anon39848301)\
**Post date:** [June 11, 2020, 7:19am UTC](https://community.forestadmin.com/t/access-to-cloudsql-postgres-database-using-unix-socket/450/2 "2020-06-11T07:19:50Z")

</div>

Hi @narciero, and Welcome to the Forest Admin community!

(I’m assuming here that you were able to fully onboard on your own localhost, and that’s the deployment process that fails, am I right?)

I’m not that familiar to the complete GCSQL/GCR environment, I’m pretty sure you can proxy the database to expose a classic database connection string, but you might not want to do this I guess ?

For now, we do not support unix socket connection string, at least from the onboarding screens. You might still be able to initialize `Sequelize` in the `models/index.js` folder using this socket though, using the `dialectOptions` parameters, like :

```javascript
var sequelizeConfig = {
    dialect: 'postgres',
    dialectOptions: {
        socketPath: '/path/to/the/socket',
    }
    port: 5432,
};

```

Let me now if that helps 🙂

---

_[View the full topic](https://community.forestadmin.com/t/access-to-cloudsql-postgres-database-using-unix-socket/450)._