Hey everyone! I'm exploring an interesting idea where I use GitHub releases as a remote storage solution and also an API server for my app. I have this repository where I store various metadata related to my app updates. Each update includes screenshots, screen recordings, and an info.json file that organizes update sections—like categories for patch notes, titles for those sections, and the assets that go along with them. This info.json acts like an API response, which my app can pull directly from a GitHub REST API URL. The app can use this JSON to create the UI and also embed videos from the GitHub release pages. Essentially, it's like treating GitHub releases as a flat file storage. Does anyone see potential issues with this approach?
3 Answers
GitHub Pages are super user-friendly! I've been using them myself and found them quite enjoyable. It's worth considering if it helps you more directly manage your media and file storage.
Using GitHub Pages could really back you up, especially since you can embed URLs for your assets directly from the releases. I think it could totally streamline things for your app. Just keep in mind potential rate limits, but if it works for rendering like a browser request, you should be good!
This is a neat approach, and honestly, I can't pinpoint any major red flags right now. My only concern would be relying on a platform for something it wasn’t primarily built for. In my experience, using tools in unintended ways can lead to issues if the vendor decides to change something down the line. You might be okay, but it’s something to keep on the radar.
Related Questions
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads