Cloudron Forum

Sync, search and backup shell history with Atuin

https://atuin.sh/

Been using it for a while now. I wanted to be able to sync my shell history outside of my LAN, so I've made a package for Cloudron @ https://github.com/Lanhild/atuin-cloudron

@james Welcome! Happy to see a new name appear on the forums.

We've made a Cloudron package for https://shields.io/.

The pros of self-hosting this service is that you can add your tokens for all your self-hosted application, or e.g. GitHub Personal Access Token to fetch badges for private repositories.

Feel free to use the code for the app store.

https://github.com/Numigi/shields-cloudron

@Lonkle How'd you do this?

I'm running into issues as I have multiple Cloudron servers with custom apps and only the ability to configure a single docker registry

@robi said in ZeroNet:

please take a look at how to solve the websocket issue and tor finding its linked libraries that are in the same directory.

Thanks for the heads up. I don't have enough knowledge about this aspect to help though.

Next time, consider not mentioning staff or app devs groups, as it sends an email to each members by default. I'm sure the people that wish to contribute would regardless of a notification

@dsp76 I'm using it, so far no issues.

@nebulon Yeah, it does work. What I meant was that it doesn't work for some clients, even though they are indeed connected to a network. I used to believe it was an issue on the client side, but the fact that it works on another typebot Cloudron instance for the clients is what makes me believe it comes from the server.

@nebulon That's where it becomes confusing - you don't need to.

When trying to reach a published bot via a new tab, a client gets the error Failed to load resource when loading the page. Trying it out on multiple other networks and devices, I cannot replicate this error.

This led me to believe it is a network error on the client side. Though, when trying the same steps over at Typebot's SaaS, the client doesn't get any errors, and the connection is successful.

I'm thinking there's a quirk hidden somewhere in Cloudron's app configuration leading to this behavior.
Any clues, I'm pretty lost.

@girish Yes please, this'd be appreciated.

@joseph Ah, I see. I was trying to add the oidc extension to use my own external IdP. Now I understand why.

When uploading an extension's .jar to /app/data/extensions, restarting the application deletes the extension file. Thus, configuring an extension is impossible.

@robi was actually a parameter in the startup file. It's all updated in my repo that I've linked previously in this topic.

@Lanhild I'm still having issue with the healthcheck, though.

Solved it by removing an unused param

@Lanhild

This last point has to be done before the initial startup, as the daemon of the binary cannot run without a valid .runner registration file.

I have solved this issue by checking if the registration file exists. If it doesn't, I simply start the runner's cache-server. The instruction to register the runner is explained in the post install message.

https://git.cloudron.io/packages/uptime-kuma-app/-/merge_requests/8

Used in the context of Gitea Actions, their version of GitHub Actions.
From the fact that Cloudron is used by many to reduce costs (by renting less VPSs), it'd be pretty useful to be able to host such an application on Cloudron.

I've made a package of the binary @ https://github.com/Lanhild/act-runner-cloudron. Though, some aspects that bring issues:

• Can't have a proper healthcheck (I have no idea what the binary uses as a port)
• 2 runtime options; Docker or binary. They suggest to use the docker option. Though, it needs access to the docker socket.
• Runner registration to Gitea instance; the runner has to "register" to a Gitea instance using a token provided by the latter. Then the runner pings the instance and checks to validate the response.

This last point has to be done before the initial startup, as the daemon of the binary cannot run without a valid .runner registration file.

https://gitea.com/gitea/act_runner

@girish thank you for the clarification. As a maintainer of apps, I had seen the changes but didn't fully understand all of them.

@girish Dependencies to install are specified in each pipelines or filters frontmatters. (the scripts that the actual software ingests)

I've already made the package @ https://github.com/Lanhild/pipelines-cloudron and dependencies installation works.

@nebulon mostly, I want to override Cloudron's OIDC for this app.