nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Self-Hosted Overleaf Community Server: Would every big server need a Production Status request?

davrot

We are pondering if we should bring Dropbox sync to the Overleaf Community Edition. For the use-case with under 50 dropbox users per server, we don't see any problem. But what is with the bigger server with > 50 dropbox users?

Does every server admin need to submit the Production Status request for their own server? And if so, how likely is it that the requests are granted for the individual servers? Honestly, I have a problem to put number to that amount. But say for the sake of the argument several hundred production status requests.

Thanks!

best wishes
David

Find more posts tagged with

API

Third Party Integrations

Comments

iNeil

Hello @davrot,

Production Status is handled at the Dropbox API app level, rather than at the individual server or user level.

For example, if you create an individual Dropbox API app for an Overleaf Community Edition instance, that app would need to apply for Production Status if it needs to link more than 50 users or 5 teams. Each API app would need to go through this process individually if it reaches the user or team threshold.

For further information, please review the DBX Platform Developer Guide – Production Approval.

davrot

Hello @iNeil,
Thanks for the information. I had the feeling that every server (they all need an individual set of API key / secret), would be seen as its own individual app. I also didn't found any way to refer to an already approved app in the API key process. And I have the feeling it wouldn't be a good idea to hardcode one common API key / secret openly into an open source code project, right?

iNeil

Hi @davrot, You're correct that it wouldn't be a good idea to hardcode your app key and secret in a public open-source repository. We recommend keeping your app key and secret private whenever possible. If they are currently included in a publicly available repository, please remove them for security reasons. If you require to rotate the app key and secret, please submit a ticket to our team using the following link:

https://www.dropbox.com/developers/contact