# How to sync 2 server istances?

**URL:** <https://vaultwarden.discourse.group/t/how-to-sync-2-server-istances/2862>\
**Category:** Uncategorized\
**Created:** [August 17, 2023, 2:29pm UTC](https://vaultwarden.discourse.group/t/how-to-sync-2-server-istances/2862 "2023-08-17T14:29:19Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ozpac](https://avatars.discourse-cdn.com/v4/letter/o/73ab20/32.png) [@ozpac](https://vaultwarden.discourse.group/u/ozpac)\
**Post date:** [August 22, 2023, 11:06am UTC](https://vaultwarden.discourse.group/t/how-to-sync-2-server-istances/2862/2 "2023-08-22T11:06:56Z")

</div>

Good idea.  
This might be of help:

> [@Is the bitwarden rs service stateless if its using postgres backend?](https://vaultwarden.discourse.group/t/is-the-bitwarden-rs-service-stateless-if-its-using-postgres-backend/450/7):
>
> I am using bitwarden\_RS in a serverless environment (Cloud RUN - uses Knative) with postgres backend (managed). It’s working fine, you just need to disable the attachment functionality. Here my env settings to auto-configure my containers: USER\_ATTACHMENT\_LIMIT 0 ORG\_ATTACHMENT\_LIMIT 0 DATABASE\_URL postgresql://user:password@IP:port/dbName SMTP\_HOST xxxxxxxxx SMTP\_PORT xxxxxxxxx SMTP\_SSL true SMTP\_USERNAME xxxxxxxxx SMTP\_PASSWORD xxxxxxxxx SMTP\_FROM xxxxxxxxx DOMAIN [https://xxxxxxxxx…](https://xxxxxxxxx.xx)

---

_[View the full topic](https://vaultwarden.discourse.group/t/how-to-sync-2-server-istances/2862)._