Cloudron Forum

If anyone is interested, here is a working setup in coolify:

• create project and add a postgres and redis database
• create a "docker compose empty" service
• Enable Connect To Predefined Network
• add the docker compose and env
• to generate the secrets, use the script on any pc (insert anything when asked for db infos):

curl -LO https://tooljet-deployments.s3.us-west-1.amazonaws.com/docker/.env.external.example
curl -LO https://tooljet-deployments.s3.us-west-1.amazonaws.com/docker/external.sh && chmod +x external.sh
mv .env.external.example .env && ./external.sh

• you can use the standard postgres db for tooljet, for tooljet db you can use any name, the database will be created on launch
• enter the url you want to use at the service settings (https://example.com:3000)

docker compose:

services:
  tooljet:
    tty: true
    stdin_open: true
    container_name: Tooljet-app
    image: 'tooljet/tooljet:ee-lts-latest'
    restart: always
    env_file: .env
    deploy:
      resources:
        limits:
          cpus: '2'
          memory: 4G
    environment:
      SERVE_CLIENT: 'true'
      PORT: '3000'
    command: 'npm run start:prod'
    healthcheck:
      test:
        - CMD-SHELL
        - 'wget -qO- http://127.0.0.1:3000/'
      interval: 30s
      timeout: 50s
      retries: 10
  postgrest:
    image: 'postgrest/postgrest:v12.2.0'
    restart: always
    env_file: .env
    deploy:
      resources:
        limits:
          cpus: '2'
          memory: 2G
    environment:
      - PGRST_SERVER_PORT=80
      - PGRST_DB_PRE_CONFIG=postgrest.pre_config

ENV:

TOOLJET_HOST=https://example.com
LOCKBOX_MASTER_KEY=(use env generator)
SECRET_KEY_BASE=(use env generator)
ORM_LOGGING=all
DATABASE_URL=(COPY DB URL FROM COOLIFY)?sslmode=disable
ENABLE_TOOLJET_DB=true
TOOLJET_DB_URL=(COPY DB URL FROM COOLIFY)?sslmode=disable
PGRST_DB_URI=(COPY DB URL FROM COOLIFY)?sslmode=disable
PGRST_HOST=postgrest
PGRST_JWT_SECRET=(use env generator)
REDIS_URL=(COPY REDIS URL FROM COOLIFY)
CHECK_FOR_UPDATES=true
DISABLE_SIGNUPS=true
USER_SESSION_EXPIRY=2880
COMMENT_FEATURE_ENABLE=true
ENABLE_MULTIPLAYER_EDITING=true
ENABLE_MARKETPLACE_FEATURE=true
DISABLE_TELEMETRY=true
DEPLOYMENT_PLATFORM=docker
LANGUAGE=en

Chibisafe is a file uploader service written in typescript that just works. It's easy to use, easy to deploy, free and open source. It accepts files, photos, documents, anything you imagine and gives you back a shareable link for you to send to others.

You can run it in public mode, user accounts mode or invite-only mode. Big files are automatically chunked to minimize network failure and users can create an API key to use the service programatically and hook it to other things.

The service also comes with a dashboard where you can edit almost every configuration of the instance directly from the UI without having to touch environment or configuration files manually. Control the name, the rate limit, max file size, accepted extensions, meta descriptions, etc directly from our intuitive panel.

Features of v6 aka Holo
Beautiful docs
️ S3 Storage Support
Beautiful masonry to browse media files
Chunked uploads for big files
Share direct links to uploaded files
Albums/Folders with direct links to share
Snippets/Gists creation with direct links to share
️ File management and file tagging
User management and quotas
Built-in URL shortener
️ Public or Private mode (with invite support)
️ ShareX support out-of-the-box to upload screenshots/screenrecordings from your desktop
iOS shortcut to upload files through the share menu
Browser extension to upload content from websites easily
🧩 Easily extensible
Open source
No ads and no tracking (except for IP logging of requests)

Licence: MIT / Docker: Yes, optional
Link: https://github.com/chibisafe/chibisafe / https://chibisafe.app/

@ekevu123 I would recommend to use dokploy.com if you do not need the additional features of coolify.

@jdaviescoates It's included now I think

Is it planned to integrate this within the next releases, or not possible in general?

@girish It works now

@girish I did a fresh installation and added some ldap credentials there. But after a reboot, they are overwritten with empty values and some predefined filters:

This is without any import of a backup or other changes.

@nebulon yes
I just want to define the LDAP server, filter, user, basedn, password and fields in the env file or somewhere else or have the option to disable that the ldap settings get overwritten after every restart.

@girish I want to use this filter:
&(objectCategory=person)(objectClass=user)(department=*)(title=*)
I use the Azure ADDS Server directly to use this filter.

It would be really great to have these settings in the env file.

@nebulon Hi, for 2 years now I have to manually overwrite the LDAP Settings 2-3 times a week. Would it be possible to not use the cloudron LDAP in any way? Maybe with a startup script? I need some custom LDAP filters.

Here is a step-by-step Guide for Shopware 6:

1. Create LAMP App and change the memory limit to 2 GB (Resources Tab)
2. Open Cloudron File Manager and add memory_limit = 512M to php.ini and switch to PHP 8.2 in PHP_VERSION
3. Download Shopware Installer (https://github.com/shopware/web-recovery/releases/latest/download/shopware-installer.phar.php)
4. Upload this file to the /public directory and open it https://yourdomain.com/shopware-installer.phar.php and complete the download process
5. After Download, the page automatically reloads and shows Welcome to Shopware 6 - do not continue here
6. Go to Cloudron File Manager and open /apache/app.conf and change the DocumentRoot to /app/data/public/public
   then add RemoveHandler type-map .var to /public/.htaccess above or below the shopware config and restart the app
7. Now you can open https://yourdomain.com/installer and enter the mysql credentials from credentials.txt (cloudron file manager root directory)
8. After the setup, you have the option to configure mail, choose configure own smtp server and enter the sendmail credentials from credentials.txt
   Additional info for mail if you use Cloudrons mail system instead of an external service: Make sure that the Shop owner's email address in Settings -> Basic Configuration is the Cloudron address, if you want to use another mail address there, you have to enable Masquerading in Cloudron Outbound Email settings. Use Port 2525 and no encryption.

• If you want to change the primary domain afterwards, you can edit the APP_URL in /public/.env.local
• If you want to add multiple domains for different Storefronts it just works after adding the Alias Location in Cloudron

Icon for launcher: https://i.imgur.com/xCR7bwQ.png

I don't think this is a best-practise configuration for Shopware, but it works, no errors so far after this short installation and test.

I don't think it would make sense to create a cloudron package for shopware.
You do not want to have auto-updates with shopware because of plugin/theme compatibility. There are still many breaking changes. Also the update process in shopware backend is really easy and works well.
Maybe it would make sense to introduce 1-click LAMP Templates to Cloudron, for less technical users.

Shopware should work on Cloudron LAMP App

Hi, we use n8n and Metabase on Cloudron and this would be a nice addition:

Give your data team magical powers
Integrate and synchronize data from 3rd party sources

Build real-time and batch pipelines to transform data using Python, SQL, and R

Run, monitor, and orchestrate thousands of pipelines

Github: https://github.com/mage-ai/mage-ai
Docs: https://docs.mage.ai/introduction/overview

Thank you very much! Because of the solution in the n8n Forum I tried writing to the /app/data/.n8n/ folder, which is not writable, but I could just use /app/data/ as the path.

I also run Cloudron on Netcup but I always use their Root-Servers with more "dedicated" resources. I didn't notice any lag so far, I used digitalocean before.

@nebulon I want to write a file to the local file system with the "Write Binary File" Node. But I have to specify a path to do so.

https://share.getcloudapp.com/bLul4qWZ
https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/

Same question for n8n Cloud: https://community.n8n.io/t/path-for-storing-writing-binary-file-on-n8n-cloud-write-binary-file-node/7383

Hi, what is the correct path to write or read a binary file in n8n with Cloudron?
If I enter no path, I get a permission error: ERROR: EROFS: read-only file system, open 'sample.csv'
If I enter the standard path I get a not found error: /home/node/.n8n/sample.csv or /app/data/.n8n/sample.csv: ERROR: ENOENT: no such file or directory, open '/app/data/.n8n/sample.csv'

Thanks a lot

I was able to install this App via the Cloudron LAMP App:

1. Open Path "/app/data/public/" and delete all files (including .htaccess)
2. run git clone https://github.com/atrocore/skeleton-pim-no-demo.git . && php composer.phar self-update && php composer.phar update (make sure you are in "/app/data/public/")
3. run find . -type d -exec chmod 755 {} + && find . -type f -exec chmod 644 {} +;
4. run find client data custom upload -type d -exec chmod 775 {} + && find client data custom upload -type f -exec chmod 664 {} +
5. add to cron in cloudron app settings: * * * * * php /app/data/public/index.php cron
6. open App URL and run setup
7. Get mysql credentials from /app/data/credentials.txt
8. Add required parameters to /app/data/php.ini:
   max_execution_time=180
max_input_time=180
memory_limit=256M
9. Restart App
10. Finish Setup

Updates can be done in the Admin UI:
Administration → System → Modules → Update
(you have to restart the App in Cloudron after every Update)

You can use this Image for the Launcher: