Advise on Convert Gitea App to Portainer using "Convert to Custom App"

I have various Truenas apps running successfuly, including Gitea. I also have Portainer installed and running.

I am considering making Gitea run under Portainer. Gitea has its own dataset and related folders within.

Would it be advisable to Convert Gitea to a Custom App and then use the resulting yaml to create a Stack in Portainer? Would I regret this totally???

Any advice / guidance will be greatly appreciated.

Brian

To me, the answer is yes (though I’ve been using Dockge, and have started using Dockhand, rather than Portainer), because I don’t have any faith in the long-term viability of the apps ecosystem. But what would you be hoping to accomplish this way? You’d gain more control over the software, at the expense of more of your effort in maintaining it.

Hi Dan

Thanks for the reply.

I am not fully clear on what I could achieve but I believe I would gain better control of updating etc., i.e. it would be less opaque, and also I would have better mobility of the containers etc., if my truenas system needs to be replaced. But I also recognise my tendency to meddle with tech which gets me into trouble occasionally :melting_face:

I suppose the main thing is that I would be more in line with the actual docker environments provided by the software developers and would not be so strategically dependant on Apps ecosystem and Truenas strategies in the future. If necessary I could move to Linux as my hosting environment.

The example of Gitea is particularly important because it is my main Git instance for all of my music/sound production (I used to be a software developer so was able to figure out how to make it work for Audio projects). I also would eventually do my own nginx, vaultwarden and immich apps too.

So pretty similar to my reasons, then.

Give serious thought to Caddy instead: