Cloudron Forum

Hi,

I've been wanting to manage my recipes for a while, and I've landed on Tandoor Recipes.

I've packaged here at https://git.eyen.ca/cloudron/tandoor-recipes
I found an initial version here from @klawitterb
At first, I was going to package it on my own as there was somethings that I didn't understand, but ended up copying most of it...

In any case, it packages the latest version (1.4.4) and has LDAP functioning.
There is a set of staticfiles that are generated at runtime and can only be generated at runtime as it depends on the postgres connection details.

@timconsidine
I updated the default server settings to have something more sensible and cleaned up the dockerfile a little bit.

You can find the repo here:
https://git.eyen.ca/cloudron/nfty.sh

Let me know what you think.

The email should work, but I don't know how to trigger it. The logs always says 0 emails sent. So I don't know how to test that.

I was hoping to use drone for my ci as I had experience with it.
I was following the thread over here and discovered woodpecker through there.

For now, I have a working setup here:
https://git.eyen.ca/cloudron/woodpecker-ci

The agent/runner cannot be run on cloudron as a native app at the moment pending this blocking issue discussed here.

Here's an initial attempt modeled on the LSIO image:
https://git.eyen.ca/cloudron/homeassistant

I haven't really tested it much.
I needed the docker wyze bridge but I did not want to expose it to the web so I included it in the docker file for home assistant.

I know at the very least, that either home assistant and the wyze bridge work independently, but I haven't tested supervisor yet.

My nas is currently having issues so I don't know when I will be able to work on it again, but if someone wants to pick up the torch, here you go

@girish said in Docker base image - 4.0:

Updated the base image to 31b195ed0662bdb06a6e8a5ddbedb6f191ce92e8bee04c03fb02dd4e9d0286df. The previous one did not install mongo shell correctly.

The main post has a hash that is too long which leads to an error.
It seems like extra characters were added in the OP.

Using what's quoted here worked.

I've packaged the app, but I'm not sure what to do next.
The repo can be found here:
https://github.com/thejinx0r/actual-server-cloudron

It's been working great for me.

edit:
I continue to maintain it at https://git.eyen.ca/cloudron/actual-server

@girish
It ended up not working.
I didn't investigate it too much.
I just recreated the app and copied the database over.

@girish Alright. I personally prefer email logins.

In any case, I changed the default to accept only the username, but I left it possible for the admin to change the search filter, which is what I am doing now.

@girish
Were you able to resolve it? I haven't seen that specific error in the passed.

@doodlemania2
I don't use cloudron and I only commented as when I was looking for the specific cloudflare error:

The service may be down or it may not be responding to traffic from cloudflared: x509: certificate is not valid for any names, but wanted to match localhost" cfRay=6957204cbdeb1fb9-SJC ingressRule=0 originService=https://localhost

I landed here from Google and I know that in the future, I will probably have this issue again and forget the solution.
So I'm posting this more for future me.

However, this would solve that specific issue that @girish was having,

I got my services up and going that used a self signed ssl cert and was able to proxy it with cloudflare.

It would be cool to try cloudron as it sounds like a really great product, but I personally don't have the budget for it at the moment.

@girish
The link to the change log is broken.
You put in v11 instead of v10
https://github.com/jellyfin/jellyfin/releases/tag/v10.8.6

I messed up. I'm updating my custom my apps through my CI and I misconfigured it. I pushed an app that did not use ldap on to jellyfin and when I reverted back to proper jellyfin, it forget that it had ldap. I just edited the evars for the container and now it works.

I'll just keep an eye on it for the next update.

@necrevistonnezr
How do you know that the live patching is enabled for that kernel?
I just don't know how to check.

-- edit --

Found it:

canonical-livepatch status

returns

last check: 23 seconds ago
kernel: 5.15.0-67.74-generic
server check-in: succeeded
patch state: ✓ no livepatches needed for this kernel yet
tier: updates (Free usage; This machine beta tests new patches.)

last check: 1 minute ago
kernel: 5.19.0-35.36~22.04.1-generic
server check-in: succeeded
patch state: ✗ kernel version not supported
tier: updates (Free usage; This machine beta tests new patches.)

So based on the pattern in the docs,
the 22.04 hwe kernel will only be supported for live patching once the 24.04 LTS is released.

@martinkbs
That's exactly what I was looking for!
I wasn't aware of Baserow or NocoDB. It sounds it might fit my needs.

Thanks for the ideas!

@subven
Thanks for the feedback!
For the user, I was following the nodejs tutorial. I'm not sure whihch one to use at the moment.

Anyways, I'll wait for feedback from @girish or @nebulon

Having an option would be great.
Can this topic be moved to feature request?

@girish said in AVX Support in your VPS/Server:

cat /proc/cpuinfo | grep -i avx

I have avx on my system.
AVX was launched ~2011 (https://en.wikipedia.org/wiki/Advanced_Vector_Extensions)

If a new system doesn't support avx, it's likely a celeron system or a lower speced system.

@girish
Were you able to login afterwards with your LDAP credentials?

I did have to create an admin account first as well, but then I was able to login with my LDAP and transferred admin rights to my Cloudron account. And just to confirm, did you use your email to login? I set it up to login with email only as I haven't looked in to the LDAP syntax yet for enabling both email and username (as you can see here)

For the licensing, I agree with your conclusion, but for legal purposes, if you do distribute Tandoor, that you would be in fact providing support (to a degree) but that Cloudron's value does not substantially depend on Tandoor. I think you are in the clear for distributing it.

@girish
I updated my repo to support both username and email logins.

edit:
I just realized that it creates 2 accounts and doesn't link them together when I login with both username and email.

@girish
I'm just posting here as this came up while googling.
For posterity, I had to do something like this in my config.yml file:

        - hostname: demo.site.com
          service: https://localhost:8000
          originRequest:
            noTLSVerify: true

It was not clear from the documentation that you needed the originRequest portion.