Cloudron Forum

@nebulon perfect, thanks a lot for this!

@nebulon the ajv module itself is present, since standalone ajv works when enabled explicitly via the .env - just as you pointed it out.
we use it to check incoming data from other internal services for potentially malformed data structures before further processing. Checking for (custom) string formats would be handy

here a snippet, based off of the example from ajv for the code node:

const Ajv = require("ajv");
const addFormats = require("ajv-formats")

const ajv = new Ajv();
addFormats(ajv);

const schema = {
  type: "object",
  properties: {
    foo: { type: "integer" },
    bar: { type: "string", format: "email" },
  },
  required: ["foo"],
  additionalProperties: false,
};

const data = { foo: 1, bar: "no.email.com" };

const valid = ajv.validate(schema, data);
if (!valid) {
  console.log(ajv.errors);
  return ajv.errors;
}
return data;

this should result in this error, showing everything is working:

{
    instancePath: '/bar',
    schemaPath: '#/properties/bar/format',
    keyword: 'format',
    params: { format: 'email' },
    message: 'must match format "email"'
  }

@nebulon i am running the validation logic in a "Code" node within the n8n app.

Hi everyone,
i need to do some json schema validation with ajv and would need the "ajv-formats" extension (https://ajv.js.org/packages/ajv-formats.html) for checking for email and date data types. since version 7 those are separated from the main ajv module. I think this library would also be very useful for "n8n as API" use cases, would you consider adding it? Or do i have to do and maintain this myself - if possible at all?

Best,
Dominik

@girish thanks for your response! I was running 7.3.1. So i updated and recreated the setup now with 7.3.2, now the App Proxy proceeds into running, but still does not serve the app.
Here some things i tried and observed:

• when using a self signed cert for usage with the IP, it serves a blank page
• when using a public domain with an LE cert, it responds an nginx 502
• The app is reachable from the public internet in both cases with TLS when adressing it directly
• The Cloudron Health check reaches Caddy on the target host every 10 sec. with status 301

Hi everyone,
i am trying to set up the new App Proxy with TLS, but struggle to do so. The app I want to proxy through Cloudron runs on a DO droplet behind a Caddy reverse proxy, no domain is attached and a self signed certificate is installed. The app is reachable from the web. When setting up the App Proxy in Cloudron with https://<IP>:443, it does not start, stays on starting for a while and then switches to not responding...
Am i missing something here?
Any help is appreciated!

@robi thanks for the info! Where can i get in contact with the devs to work out an arrangement for packaging this?

Is there anything one can to do to help this come to be? I would love to integrate my Budibase instances with Cloudron, the potential is really there!

@doodlemania2 they indeed released it some time ago. I have a deployment running for some time now and did not encounter any issues so far. When packaging for cloudron i suggest adding the postgres database plugin, since the internal db limits to 4k rows in the free tier.

Budibase is now in version 2 since a couple of days, keeping the open source tier. Given the amount of additional functionality the platform has gained since the original discussion here took place, especially now with version 2, I feel it would be a great addition to the cloudron App Store, what are your thoughts on this @joebudi @nebulon ?