Cloudron Forum

@nebulon I see. Ok this solves it for me. Yes build build left me spinning last week but I understood eventually

@timconsidine I'm using cloudron build. Is this -f option undocumented? I don't see any references to it.

The docs describe alternative Dockerfile names:

If your project already has a Dockerfile, name the Cloudron-specific Dockerfile Dockerfile.cloudron or cloudron/Dockerfile.

It would be nice to just set a custom path as my project targets multiple panels and I would like to keep them in one directory to declutter the root folder. Ideal to specify something like:

deploy/cloudron/Dockerfile

@nebulon said in Point arbitrary domains to a cloudron app?:

is there a reason to not make that domain known by Cloudron?

Sort of as fbartels described:

1. you might think of it as a 'customer' domain, so they use the service running on Cloudron and not Cloudron itself, therefore you might want to provide a way to add domains within your deployed app.
2. I've noticed that DNS misconfigurations can stall or block deploys because it just keeps retrying, and I would like to avoid exposure to that; would the 'manual' provider change this? But I realize I'm a bit self-contradictory because of course I also would try to automatically configure certificates for their domains so they don't have to.

@fbartels said in Point arbitrary domains to a cloudron app?:

you need to add the domain to Cloudron in general and when/if a customer changes their dns settings to have the given domain no longer point to you, you will see failures to generate new certificates.

True. I considered having a background task that regularly checks if there's a pointing issue and then removes the domain so it doesn't block deploys, but this is messy…

@fbartels said in Point arbitrary domains to a cloudron app?:

a service where users can point domains via cname to our service

Sounds like what I'm trying to do! I'm not familiar with caddy but will see if there's a simple way for me to deploy that.

@joseph said in Point arbitrary domains to a cloudron app?:

Technically, how will cloudron serve up a secure site without even knowing a domain? It won't have the certificate for this unknown dynamic domain.

True. I think I'm trying to emulate how PaaS platforms let you add a domain with https, but doing it at the app level instead of the platform (cloudron) level. I was thinking yesterday maybe the Cloudron API can add them and provision certificates behind the scenes.

How can I get a Cloudron app to receive requests without adding an alias?

For example, I would like to setup cname.myapp.cloudron.domain and allow users of the app to point their domains there (i.e. a user can make a CNAME record for sub.theirsite.com to cname.myapp.cloudron.domain).

In some way I'm asking an old question but instead of static files I want to deploy a node.js app that responds dynamically.

Seems like a maintainer says it's not an upstream issue:

This seems well outside of YOURLS and its stack. You're getting an nginx error message, but Cloudron builds its YOURLS container using Apache.

Do you have an nginx reverse proxy in front of your Cloudron apps? That would be where to start.

Maybe it's an nginx issue?

@james i didn't get an email notification for this reply, good to know!

i think the use case described previously is more for static sites with surfer (my personal preference as github pages can be super slow to create and upload artifacts).

but nonetheless, could you clarify why it seems to push without any docker build step? i'm used to installing custom apps from registries after building so this "push code" concept seems novel.

(edit: my email was outdated… just updated)

I'm getting 414 errors when shortening very long URLs (in my case about 7000 characters) via API POST requests.

Not sure if this has to do with Cloudron's package, or Cloudron's n8n package making the request, or an upstream issue. Made an issue on their GitHub as well with more details https://github.com/YOURLS/YOURLS/issues/4061

Also, I noticed that YOURLS is not in the forum list of app subtopics on the front page.

Got this working for myself:

1. create an environment and define your SURFER_TOKEN / SURFER_HOST secrets there
2. set the environment in your job
3. expose the secrets to the run command

My example assumes:

• environment name alfa
• you want to upload the bravo directory…
• to your server under /charlie/delta

name: Deploy

on: [push]

jobs:
  build_site:
    runs-on: ubuntu-latest
    environment: alfa
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      # … other steps for install, build, etc…

      - name: Install surfer
        run: npm -g install cloudron-surfer

      - name: Upload
        env:
          SURFER_TOKEN: ${{ secrets.SURFER_TOKEN }}
          SURFER_HOST: ${{ secrets.SURFER_HOST }}
        run: surfer put --token "$SURFER_TOKEN" --server "$SURFER_HOST" bravo/* /charlie/delta

Just got interested in this myself, seems like they use Docker Compose https://github.com/gramps-project/gramps-web/blob/main/docker-compose.yml

@nebulon Agreed. I just use the tools I understand, so it tends to end up with this shape. For me static sites only require GET anyway. I copied headers in the previous version, maybe will add that later. Pull requests welcome if someone wants to improve it.

I just worked on a hack for this https://github.com/rosano/remit

It's a small separate app that maps multiple domains to folders under any public URL: so if it gets a request for your-site-domain.com/path, it will fetch https://your-surfer-cloudron-domain.com/maybe_a_folder_with_some_websites/your-site-domain.com/path and send it as a response. So you name folders with the domain and it figures out the rest.

@nebulon Yes, and I also asked myself last year! https://forum.cloudron.io/topic/11395/multiple-static-sites-on-one-app/3

If I develop a solution, where do you recommend I share it?

Is it possible to have different subdirectories in surfer mapped to their own domains? Like this:

• example1.com maps to /public/alfa
• example2.com maps to /public/bravo

• Title: DumbDrop on Cloudron - No accounts, no tracking, just drag, drop, and share.

• Main Page: https://dumbware.io/DumbDrop
• Git: https://github.com/DumbWareio/dumbdrop
• Licence: GNU GPL
• Docker: Yes
• Demo: https://dumbdrop.dumbware.io (I was able to guess the pin easily)

• Summary: end-to-end encrypted file-sharing app, maybe similar to wormhole (or filepizza but not p2p)

• Notes: they seem to make a nice suite of simple open-source software

• Alternative to / Libhunt link: e.g. https://alternativeto.net/software/dumbdrop/
• Screenshots:

Surprised to find this here! I've been developing apps for this since 2019. Yesterday, I finally made a Cloudron package for the Armadietto server https://github.com/rosano/armadietto-cloudron

Deleting all executions still didn't move the database down from 500mb, but after running VACUUM FULL execution_data; it's now 13mb. I''ll take it.

@joseph it's the execution_data table but I'm not sure how to figure out where the bloat is. the LLM queries are giving me mostly table size but nothing more detailed.