Cloudron Forum

Gave it a try and packaged it. Was actually quite easy as its a ready to run go app. Seems like LDAP and mail needs to be set up from within the application. Otherwise it seems to be running fine.

If somebodys interested code is here:
https://git.apehost.de/cloudron-apps/documize/

Just stumbled upon this and thought this might be interesting for others as well: Mealie has an integration with Open AI which enables importing recipes from images. Worked really well in my tests.

To enable this you'll need an API key and at least Tier 1 which you'll get after depositing 5$, see also https://docs.mealie.io/documentation/getting-started/installation/open-ai/.

For cloudron simply open the env file in the file manager and add OPENAI_API_KEY=<your_key>.

Just packed this up, syncing seems to work fine, but mail isn't yet working.

If anyones interessted
https://git.apehost.de/cloudron-apps/joplin-server/
https://hub.docker.com/r/benklaw/cloudron-joplin-server

@jdaviescoates Happy to share the code, just fired it up a couple of months ago to see if it would work. So should be regarded as a prototype only.
https://git.apehost.de/cloudron-apps/outline
Keep in mind that it also requires a S3 compatible storage like minio. So full solution would actually require 3 apps to be running.

So I was curious about my proposal and just tried this. Seems to work quote well. Much easier than setting up a fully fledged identity provider like keycloak imho.
Basically dex is a go app which is controlled by a yaml config. Currently just running it inside the outline app itself with a little nginx proxy in front of it. When logging in it redirects to the login mask from dex which then authenticates the user from cloudrons LDAP.

@cloudron_hacky I packed up tandoor recipies myself. Although there are still some open issues feel free to have a look at my repo: https://git.apehost.de/cloudron-apps/cloudron-tandoor-recipies/

@timconsidine I've packed it up as a custom cloudron app. Wouldn't call it production ready though. Same for outline itself.
So I've got now 3 apps driving this, outline, keycloak and minio for storage. Not exactly simple.

I’m using multi stage dockerfiles for my projects, works like a charm. Only for final stage I use the cloudron base image.

@girish how about adding oidc as another addon and just ferderate to LDAP? Something like https://github.com/dexidp/dex could be used for this.
Only thinking out loud, never used this myself. Stumpled over it while working on other projects.

Count me in

@girish works perfectly fine now, thanks for the quick fix

I haven’t spend a lot of time in tandoor, but I really find the ui unappealing.

Also an interesting side fact: you can connect self hosted LLMs as long as they support the open ai api. It’s also mentioned in the docs.

@brianb you can compile your app as self contained. It will eliminate the need of having the .net framework installed in the cloudron base images.

@girish I did try all combinations, smtp & smtps port, mailsecure 0/1. Didn't help.

But I spottet this bug on github. Sounds at least similar.
https://github.com/laurent22/joplin/issues/5222

I’m building a nuxt.js app myself (same as next but for vue). I find it relatively easy to build a custom docker image for cloudron. Using gitlab + gitlab runner on cloudron to build the app and push a docker image to the internal docker registry and deploy it from there to cloudron. Even got 2 versions of the app running for some test staging.

Latest release includes generic oidc authentication. Hooked it up with keycloak and seems to be running fine.

So here's a little sum up how I do it:

1. Create dockerfile

ARG nodeversion=21-bullseye

# build stage using standard node container
FROM docker.io/node:$nodeversion AS builder

WORKDIR /app

# copy & install dependencies
COPY package.json yarn.lock .yarnrc.yml ./
COPY .yarn/ .yarn
RUN yarn install
# copy source code & build
COPY . .
ENV NODE_ENV=production
RUN yarn build --standalone 

# use cloudron base image for running the app
FROM docker.io/cloudron/base:4.0.0@sha256:31b195ed0662bdb06a6e8a5ddbedb6f191ce92e8bee04c03fb02dd4e9d0286df

WORKDIR /app
ENV NODE_ENV=production

# copy built files
COPY --from=builder ./app/.output ./.output/
# start script for execution of the app, make sure its executable
COPY --from=builder ./app/start.sh ./
RUN chmod +x /app/start.sh

# set the port and host and expose the port
ENV HOST 0.0.0.0
ENV PORT 8000
EXPOSE 8000

# start the app using start script
CMD [ "/app/start.sh"]

2. Create start.sh

#!/bin/bash

set -eu

# set any environment variables here, e.g. database connection details

# run the server
node .output/server/index.mjs

3. Create CloudronManifest.json
   Nothing special here, follow documentation from Cloudron, set app details, add addons, set exposed port, etc.
4. Create CI/CD pipeline
   This depends a bit on your runner setup, I'm using a custom gitlab runner package on Cloudron I build for myself + the cloudron build service app. This has some quirks but works for me. Its a docker in docker runner but without access to the docker.sock its not possible to run docker commands itself (or at least didn't figure out how). Normally you'd need access to the docker.sock which is not possible with app packages and a security risk.
   Nevertheless here's a sample of my .gitlab-ci.yml

stages:
  - stage

deploy_stage:
  stage: stage
  image: node:19
  environment:
    name: STAGE
  variables:
    BUILD_SERVICE: 'https://builderbot.serverdomain.de'
    FQ_IMAGE_NAME: 'docker.serverdomain.de/imagepath'
    TAG: pre
  only:
    - main
  script:
    - npm install -g cloudron
    - cloudron build --tag $TAG --set-build-service $BUILD_SERVICE --set-repository $FQ_IMAGE_NAME --build-service-token $CI_BUILD_SERVICE_TOKEN
    - cloudron update --server my.serverdomain.de --token $CI_CLOUDRON_TOKEN --app appsubdomain.serverdomain.de --image docker.serverdomain.de/imagepath:$TAG
    #- cloudron install --server my.serverdomain.de --token $CI_CLOUDRON_TOKEN --location appsubdomain.serverdomain.de --image docker.serverdomain.de/imagepath:$TAG

For first run you need to use install cli cmd and afterwards update. Hence I always keep it commented out in the pipeline in case I need to reinstall the app from scratch. A combined command for this would be brilliant *hint *hint @girish

Apart from that there's a little more to it in terms of one time setup which I ommited:

• Setup private docker registry in Cloudron (alternative use a public registry)
• Register the gitlab runner in gitlab
• Setup secrets in gitlab, e.g. Cloudron access tokens
• might be more I've forgotten, as always once setup things get blurry in memory

@jdaviescoates I've got this running using dex serving as a connection between oidc and cloudron ldap. Works pretty well.
If you're interested you can find the code in my repo https://git.apehost.de/cloudron-apps/outline

Hi,

is there any way to properly set an image in the server side e-mail signature?
Tried inline image & svg but seems like most e-mail providers don't support this.

Thanks!

@girish I’ve used their env sample as a reference for configuring it with Dex in my package: https://github.com/outline/outline/blob/main/.env.sample