Discussing Best Practices for Storing Files Externally on DigitalOcean Spaces

This meeting involved a discussion between State Changers Michael and Ray about the use of the DigitalOcean service for object storage, particularly focusing on the best practices for storing files within spaces. To provide file organization and also to anonymize sensitive data, they considered using a company's UUID as the prefix for the path of any files they upload. Ray also suggested base64 encoding the file name to handle any strange characters.

Michael clarified his choice of DigitalOcean over other options like Google Cloud Storage or AWS. He opted for DigitalOcean not only due to his lack of experience in the other platforms but also because of progress reasons - he was already using DigitalOcean to host the WeWeb code thus, it felt like a natural progression to utilize another of their features, the spaces object storage. There was also a mention of the significant performance improvement experienced when code was self-hosted on DigitalOcean, reducing page load times by approximately 90%. Reinforcing the notion that infrastructure decisions could possibly have a greater impact on performance than pure code optimizations. It is important to note there was no mention of the keywords: "Xano", "FlutterFlow", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", and "AI21".

(Source: Office Hours 10/30/2023 )

State Change Members Can View The Video Here

View This Video Now

Join State Change Risk-Free