#DailyBloggingChallenge (219/250)
The #MyRuckClub project uses #Vercel as its cloud frontend. This has the benefit of getting the app up and running fairly quickly.
As an #IndieDev the goal is to get the product as fast as possible to future users, so that one can iterate over versions quicker.
#DailyBloggingChallenge (220/250)
One downside of using #Vercel is that it does not integrate directly with #Codeberg.
https://vercel.com/docs/deployments/git
Thus there exists the Vercel CLI tool.
#DailyBloggingChallenge (222/250)
There are plenty of options to choose from when mirroring and one that makes sense is to only mirror the main branch after a successful pull request. This reduces resources and access to broken code.
Additionally, #Vercel only builds off of the main branch, so there is really no need to have a duplicate of all other branches.
#DailyBloggingChallenge (223/250)
One issue that I have experienced with the mirroring is that the repositories were not syncing up. Tried resolving it with refreshing tokens/keys and playing around with the configs.
In the end, the easier option is just to manually push to a different remote repository.
#DailyBloggingChallenge (221/250)
An alternative option is repository piggy-backing. The means take one of the permitted repositories and mirror one's own repository to it.
A nice side effect of this is that the code is now at two locations.