L
@girish said in Cal.com (was Calendso) - Calendly Alternative:
@3699n yes, I think it's worthwhile re-investigating the current situation with selfhosting cal.com . Added to our internal list.
FYI, I am as of yesterday attempting to package cal.com for Cloudron, so far, the project dependencies installation and building is working. I am currently looking over the startup part of cal.com, and might be able to provide a working package or, at the least, a good starting point.
Hello everyone,
I've successfully packaged open-webui | formerly known as ollama-webui for Cloudron.
The application allows you to chat with a remote Ollama server.
To see my package code: https://github.com/Lanhild/open-webui-cloudron
The package is fully working as of today, Feb 14th. The only issue I'm facing and would require assistance with is this. If anyone has a clue about this one, feel free to make a PR.
P.S.: If the Cloudron team wishes to manage the packaging for this app, I'll gladly hand in my code, just notify me!
The code of my attempt at packaging cal.com for Cloudron is here
The package works as in:
@girish The repo code that I linked can be freely used as a good advanced starting point by the team in order to package cal.com. If there are any questions, please feel free to ask by mentioning me in this thread
@girish done and ready @ https://github.com/Lanhild/web-check-cloudron
I've added the proxyAuth addon so that when deployed on Cloudron, only your users can use it.
Pipelines bring modular, customizable workflows to any UI client supporting OpenAI API specs – and much more! Easily extend functionalities, integrate unique logic, and create dynamic workflows with just a few lines of code.
Hi,
I made a package for Open WebUI's Pipelines. It works well.
The following are missing from the upstream:
Stumbled upon https://localsend.org a while ago. It has impressive performance, a great UI/UX.
Compatible w/ Linux, Windows, Mac, Android, iOS
I've started a package, not sure I'll be able to go further than that though. Anyway, so far I've managed to get the UI up and running, but there is an error with the database connection.
https://github.com/Lanhild/healthchecks-cloudron
Don't hesitate to ask if there's any questions/needs
@LoudLemur All the information I needed were present in the Cloudron documentation.
Some applications that I use (such as Ollama-webui) are not very resource hungry, therefore I wanted to have them on my Cloudron server rather than a dedicated server. Basically, reducing the amount of servers to maintain/update by having more services on my Cloudron.
Traces, evals, prompt management and metrics to debug and improve your LLM application.
Tools for the full development workflow
All Langfuse features are tightly integrated with Langfuse Tracing.
Open source LLM engineering platform: Observability, metrics, evals, prompt management, playground, datasets. Integrates with LlamaIndex, Langchain, OpenAI SDK, LiteLLM, and more. 
YC W23
Hi,
I started a package for Langfuse. Everything works well, the only missing element is the startup of the application. I have the following error:
Jun 21 17:22:43 prisma:error <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - Invalid `prisma.$queryRaw()` invocation: <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x". <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - This happened because Prisma Client was generated for "linux-musl-openssl-3.0.x", but the actual deployment required "debian-openssl-3.0.x". <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - generator client { <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - provider = "prisma-client-js" <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - binaryTargets = ["native", "debian-openssl-3.0.x"] <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - } <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - The following locations have been searched: <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /app/code/langfuse/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/.prisma/client
Jun 21 17:22:43 prisma:error <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - Invalid `prisma.$queryRaw()` invocation: <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x". <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - This happened because Prisma Client was generated for "linux-musl-openssl-3.0.x", but the actual deployment required "debian-openssl-3.0.x". <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - generator client { <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - provider = "prisma-client-js" <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - binaryTargets = ["native", "debian-openssl-3.0.x"] <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - } <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - The following locations have been searched: <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /app/code/langfuse/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/.prisma/client <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /app/code/langfuse/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/@prisma/client <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /app/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/@prisma/client <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /tmp/prisma-engines <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /app/code/langfuse/packages/shared/prisma
Jun 21 17:22:43 /app/code/langfuse/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/@prisma/client <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /app/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/@prisma/client <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /tmp/prisma-engines <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /app/code/langfuse/packages/shared/prisma
Jun 21 17:22:43 Telemetry, unexpected error: PrismaClientInitializationError: <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - Invalid `prisma.$queryRaw()` invocation: <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x". <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - This happened because Prisma Client was generated for "linux-musl-openssl-3.0.x", but the actual deployment required "debian-openssl-3.0.x". <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - generator client { <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - provider = "prisma-client-js" <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - binaryTargets = ["native", "debian-openssl-3.0.x"] <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - } <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - The following locations have been searched: <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /app/code/langfuse/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/.prisma/client <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /app/code/langfuse/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/@prisma/client <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /app/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/@prisma/client <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /tmp/prisma-engines <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - /app/code/langfuse/packages/shared/prisma <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - at In.handleRequestError (/app/code/langfuse/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/@prisma/client/runtime/library.js:122:7154) <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - at In.handleAndLogRequestError (/app/code/langfuse/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/@prisma/client/runtime/library.js:122:6188) <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - at In.request (/app/code/langfuse/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/@prisma/client/runtime/library.js:122:5896) <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - at process.processTicksAndRejections (node:internal/process/task_queues:95:5) <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - at async l (/app/code/langfuse/node_modules/.pnpm/@prisma+client@5.13.0_prisma@5.13.0/node_modules/@prisma/client/runtime/library.js:127:11167) <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - at async A (/app/code/langfuse/web/.next/server/pages/api/public/health.js:1:5002) <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - at async a (/app/code/langfuse/web/.next/server/pages/api/public/health.js:1:4690)
Jun 21 17:22:43 at async A (/app/code/langfuse/web/.next/server/pages/api/public/health.js:1:1119) <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - at async /app/code/langfuse/node_modules/.pnpm/@sentry+nextjs@8.8.0_@opentelemetry+api@1.9.0_@opentelemetry+core@1.25.0_@opentelemetry+instr_g4e53b5uljxdtjcdarqr3up6tm/node_modules/@sentry/nextjs/cjs/common/wrapApiHandlerWithSentry.js:90:43 <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - at async K (/app/code/langfuse/node_modules/.pnpm/next@14.2.3_@babel+core@7.24.7_@opentelemetry+api@1.9.0_@playwright+test@1.43.1_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) { <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - clientVersion: '5.13.0', <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - errorCode: undefined <30>1 2024-06-21T21:22:43Z my.numi.tools 14b3836e-aeca-46c2-bd02-d454bfec8b80 1022 14b3836e-aeca-46c2-bd02-d454bfec8b80 - }
I'm guessing it's because the environment the app's been built on is different than the runtime's.
I may have an idea for the easiest way to achieve this. (I don't know if it's been proposed before)
Instead of creating/modifying a dedicated Cloudron app, a simple change could be made to the app store: The ability to add custom sources files.
Just like apt or any other package manager has, we could have source files that contain;
Each source files you added could also have applications that use private Docker images, so prompting the user if they want to add a custom registry credentials for this source file would be necessary.
This would then allow to list additional applications in the Cloudron app store that come from these source files, and tag/label them as Custom
You could install them just like officially packaged apps, update, backup, etc.
IMO, sources files would be the most user-friendly way to install custom apps as there'd be no need for the use of Cloudron CLI, as everything would be done through the UI
Let me know what you think about it.
Wanted to share something I do for my packages; Using a package.json to manage various scripts
I use a package.json file with different scripts to achieve common Cloudron packaging tasks:
It also offers a better portability for other potential developers (providing the Cloudron CLI as a dependency, etc.)
Here is an example of one:
{
"name": "io.cloudron.yourapp",
"description": "Cloudron Yourapp application",
"scripts": {
"build": "bash scripts/build.sh",
"format": "npx prettier . --write",
"lint:shell": "npx shellcheck -x scripts/*.sh",
"lint:apply": "npx shellcheck -f diff scripts/*.sh | git apply",
"update:prod": "bash scripts/update.sh -l prod",
"update:test": "bash scripts/update.sh -l test",
"prepare": "husky"
},
"devDependencies": {
"husky": "^9.0.11",
"prettier": "^3.3.1",
"cloudron": "^5.5.0",
"shellcheck": "^2.2.0"
}
}
Apart from a package.json, I also ship all of my packages repos with files such as .editorconfig and .prettierrc to help uniformize my different packages.
@Kubernetes I might take a quick look at it. Not sure I'll go very far, but I can contribute some notes/remarks at the least
Free high-performance wiki tool
This tool for sharing manual,
business proposal and simultaneous editing minutes in real time.
it supports comfortable information sharing and work efficiency within the team.
https://growi.org/en/
https://github.com/weseek/growi
Would be a great addition to Cloudron.
I've already looked a bit into the code. IMO, the difficult part is the many components involved with this software, i.e.:
Elasticsearch
Mongodb (no problem for this, just use the addon)
S3 for file upload (optional)
HackMD for collaborative editing (optional, can be an external hackmd server)
I could maybe look into starting a package for this app someday.
I've opened https://github.com/open-webui/open-webui/pull/839, as a mean to comply with Cloudron packaging standards.
Coming back with great news!
Open WebUI introduced today automatic releases with versions strings from the version field in the package.json file.
I also found the issue with document uploading, there was a missing environment variable.
I thoroughly tested the package, documented what I could/was necessary.
The package https://github.com/Lanhild/open-webui-cloudron is now fully working 