<![CDATA[How to allow push for authenticated user, but pull for anonymous/everybody?]]>Hi there,

How to allow push for authenticated user, but pull for anonymous/everybody?

I would like to have a public available image pull repository of Docker Images.
Pushing new Docker images or updating Docker images should only possible for authenticated users.

Does somebody know how to achieve this?

Thanks!

Mike

PS: This is first part of implementing the idea in this post

]]>https://forum.cloudron.io/topic/10949/how-to-allow-push-for-authenticated-user-but-pull-for-anonymous-everybodyRSS for NodeMon, 15 Jun 2026 13:45:58 GMTSat, 27 Jan 2024 13:15:37 GMT60<![CDATA[Reply to How to allow push for authenticated user, but pull for anonymous/everybody? on Mon, 29 Jan 2024 10:43:37 GMT]]>yeah, as @fbartels said, the app is hosted behind a proxy auth. The whole thing is either protected or not. It's not possible to have public pulls with private pushes.

]]>https://forum.cloudron.io/post/82157https://forum.cloudron.io/post/82157Mon, 29 Jan 2024 10:43:37 GMT<![CDATA[Reply to How to allow push for authenticated user, but pull for anonymous/everybody? on Sat, 27 Jan 2024 19:12:19 GMT]]>@fbartels That sounds like a very good suggestion. Thank you, I will give it a try

]]>https://forum.cloudron.io/post/82004https://forum.cloudron.io/post/82004Sat, 27 Jan 2024 19:12:19 GMT<![CDATA[Reply to How to allow push for authenticated user, but pull for anonymous/everybody? on Mon, 29 Jan 2024 11:10:14 GMT]]>I don't think this is easily doable with the default registry app on Cloudron. But it can still be achieved with other apps available on Cloudron.

I would use the Gitea app as a base. You can tie this app to the Cloudron auth and allow container uploads for a certain user. Within the repo of choice you can then do a public pull. The added benefit is that you can use Gitea actions to build apps in the first place.

]]>https://forum.cloudron.io/post/82003https://forum.cloudron.io/post/82003Mon, 29 Jan 2024 11:10:14 GMT