🎧 Creating a Google Cloud Storage Bucket for Audio Files 🎧
This guide will walk you through setting up a Google Cloud Storage (GCS) bucket perfect for keeping your 🎶 audio files 🎶 safe and sound. We’ll set it up with the right permissions and give you the keys 🔑 (credentials) so you can easily upload and manage your tunes.
Name your bucket: Pick a unique name that follows the naming guidelines. Get creative, but keep it relevant! Example: omi-audio-files.
Where should we store your audio?: Choose a location that makes sense for you. Think about how quickly you need to access your files and your budget. A Multi-region is great for extra reliability across a wider area, while a Region gives you faster access in a specific spot.
Pick a storage class:Standard is usually the best choice for files you access often. If you have audio you don’t need very often, check out the other options (Nearline, Coldline, Archive) to save some 💰.
Control who can access your files:
Public access prevention: Keep this “On” to make sure your audio stays private. 🤫
Access control: Stick with “Uniform” for consistent permissions across all your audio files.
Extra protection for your tunes:
Soft delete policy: This is already on by default – it’s like a safety net if you accidentally delete something!
Object versioning: Want to keep track of changes and easily recover older versions? Turn this on!
Object retention policy: If you need to keep audio for a specific amount of time, use this to set rules.
Encryption type: Google will keep your audio encrypted by default – you don’t need to do anything here unless you have special requirements.
Time to Create:
Double-check everything and click “CREATE”.
Success!
You’ll get a message letting you know your bucket is ready to rock. 🤘
Now that you have set up your GCP storage, you can use it with Omi’s audio streaming feature. For detailed instructions on setting up audio streaming with your newly created storage bucket, please refer to our Audio Streaming Guide.
We welcome contributions from the open source community! Whether it’s improving documentation, adding new features, or reporting bugs, your input is valuable. Check out our Contribution Guide for more information.