Has the file buffer disappeared? How do you get the file buffer when sending a file to BuildShip?
Here's a video that might help:
6 Replies
AI Support Bot Information
<@999510535987023873> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
It seems like the video you mentioned may not be available for direct viewing or description in the document provided. However, you can start using BuildShip by setting up an account and creating a project in a region of your choice. Once set up, you can start creating workflows by connecting nodes or using templates. Test your workflow, check the logs, and deploy with a click【4:0†buildship-docs.json】.
For more specific guidance, I recommend watching a short walkthrough video available in the BuildShip documentation or visiting the BuildShip website for detailed guides【4:0†buildship-docs.json】. If you have any other questions about BuildShip, feel free to ask!
BuildShip AI Support
@Harini @Bhavya
@nithinrdy
hey there stuart (sorry about the delay), the buffer property is indeed not present in the v2 file upload trigger because files are handled a bit differently in it.
In short: in the v1 trigger, files were saved in memory, but never saved to disk. In the v2 trigger, each uploaded file is written to disk. The problem is that the underlying library we use provides the
buffer option only when files are stored in memory, not when they're saved to disk.
As for a way around, we're adding a set of utilities that makes file handling (including operations like converting between file types, like from a base64 string to a nodejs buffer) on BuildShip easier.
The project is still a WIP, but we're in the final stages of wrapping it up and once its done, this would be the go-to way to obtain a file's buffer (among other such operations).@Stu I ended up finding somewhat of a workaround. Instead of using the file upload with buffer, I just use 'Upload File' and use the file path/file name.
Took me a minute to figure that out but I can confirm it works, return the url and I'm able to use it in the rest of my flow.
@BuildShip team, it would be great if the video/tutorial/template were updated to reflect this...I spent way too long trying to figure this out.
