@robi I went ahead and created the App request thread: https://forum.cloudron.io/topic/9764/forgejo

So the memory leak indeed seemed to be coming from the frequent health check. I customized the health check path and returned a simple response object, and it seems to do the trick. [image: 1690991598001-131f8985-2dcb-4006-ad8a-887963dea05f-image.png] I still think I have something incorrectly handled somewhere and if the website would have a lot of traffic, the issue would probably resurface. But it's not very likely, so I'll stick to YAGNI. (I'll keep an eye on the stats in any case.) Thanks for the help.

You can check if listen({ host: '0.0.0.0', port: 3000 }) makes it better.

@nebulon Great, thanks for the information. I think having support for headless apps would be a nice feature in the future.

@Kubernetes yes. You can also add the optionalSso flag to indicate that the app can installed without it as well (so an option is provided at install time)

The dockerfile is here . It's nothing special, just lots of packages on base ubuntu. To add to what's been said: our approach is the batteries included approach and it's optimized for developer/sysadmin productivity (as opposed to saving disk space). When we open a web terminal, we want all the common tools across all apps (ping, nc, telnet, tar, node, php, python what have you). The Web terminal and File manager have a bunch of tooling prerequisites - tar, zip, rar, jq, database clients (mysql/postgres/redis/mongo), etc for it work well. Any image will work including multi-stage builds. You have to pay attention to our deployment paradim though - https://docs.cloudron.io/packaging/cheat-sheet/#filesystem . Containers are run on a readonly fs, there is no way around this.

You can look into bookstack-app , pixelfed-app , nextcloud-app for some apps that use redis

I left a note in that issue.

For a while there was a WIP tag but people forgot to use it

@girish Oh, I see. Right, unless you install your own torrent tracker, and use the install base swarm to seed images from your own infrastructure at minimal bandwidth usage. No need for docker hub then!

Problem solved after compiling the source

@ekevu123 Thanks for the report! There was indeed a bug that the dashboard code throws an error when an app does not use any addons. https://git.cloudron.io/cloudron/box/-/commit/e02f3d70649c75c64e4126f1deea45b3456277a0 is the fix.

@girish, I have access again. Thank you!

@rxlict yes, if the build fails, everything will go pear-shaped. Trying to go ahead will fail. The important step is to solve the build issue, which will be in how the Dockerfile is constructed. Can you share which app you're trying to package? Stick with it : it can be a frustrating process solving the build issues, but once you have success, it's all worth while.

@nebulon I wasn't told exactly but believe it had something to do with removing the www user

@alwynispat we have some resources on that topic at https://docs.cloudron.io/packaging/tutorial/ as well as a forum section https://forum.cloudron.io/category/96/app-packaging-development