You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the hosted instance of Briefkasten (https://briefkastenhq.com), runs on Vercel which has a 10s limit on its API routes. Meaning, for the API endpoint which saves new bookmarks, it was not possible to also take the screenshot there and keep it consistently under 10s.
So for the hosted instance, I put the screenshot taking into a decoupled message queue that would be worked through by some serverless function workers.
This seems like way too much work for a self-hosted instance, hwoever, plus the self-hosters do not have that arbitrary 10s limit.
Suggested solution
Vercel adds an environment variableVERCEL which is 1 when an application is running on their platform. Therefore, we can easily tell whether we need to run the screenshotting process through the queue, or have the resources to just fire up playwright / puppeteer right in the backend process and take the screenshot immediately upon adding the bookmark.
This is a feature request from myself, just adding this issue to keep track, inform the community, and potentially gather any additional feedback yall may have 🙏
I do not have an ETA on this, but plan to add it soon ™️
Alternative
No response
Additional context
No response
Validations
Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
The text was updated successfully, but these errors were encountered:
Clear and concise description of the problem
Currently the hosted instance of Briefkasten (https://briefkastenhq.com), runs on Vercel which has a 10s limit on its API routes. Meaning, for the API endpoint which saves new bookmarks, it was not possible to also take the screenshot there and keep it consistently under 10s.
So for the hosted instance, I put the screenshot taking into a decoupled message queue that would be worked through by some serverless function workers.
This seems like way too much work for a self-hosted instance, hwoever, plus the self-hosters do not have that arbitrary 10s limit.
Suggested solution
Vercel adds an environment variable
VERCEL
which is1
when an application is running on their platform. Therefore, we can easily tell whether we need to run the screenshotting process through the queue, or have the resources to just fire up playwright / puppeteer right in the backend process and take the screenshot immediately upon adding the bookmark.This is a feature request from myself, just adding this issue to keep track, inform the community, and potentially gather any additional feedback yall may have 🙏
I do not have an ETA on this, but plan to add it soon ™️
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: