Cloudron Forum

ToolJet is an open-source low-code framework to build and deploy internal tools quickly without much effort from the engineering teams. You can connect to your data sources, such as databases (like PostgreSQL, MongoDB, Elasticsearch, etc), API endpoints (ToolJet supports importing OpenAPI spec & OAuth2 authorization), and external services (like Stripe, Slack, Google Sheets, Airtable) and use our pre-built UI widgets to build internal tools.

Link: https://github.com/ToolJet/ToolJet
Docker: https://docs.tooljet.com/docs/setup/docker/

Appwrite - A Firebase Alternative

https://appwrite.io/

Mixpost is a Laravel marketing platform for social networks.

https://github.com/lao9s/mixpost

An open-source knowledge-based community software. You can use it quickly to build Q&A community for your products, customers, teams, and more.

Github: https://github.com/apache/incubator-answer
Website: https://answer.apache.org
Docker Installation: https://answer.apache.org/docs/installation/

Update: Updating post to reflect Answer moving to the Apache Incubator Program.

Hello!
It would be great if we had the ability to add notes to manual backups for Apps. For example, we develop a lot of sites on Cloudron and it would be great to add a few notes after a manual backup so we know which backup contains what.

Thank you!

I was taking a look at Whoogle, which already has Docker container support.

Get Google search results, but without any ads, javascript, AMP links, cookies, or IP address tracking. Easily deployable in one click as a Docker app, and customizable with a single config file. Quick and simple to implement as a primary search engine replacement on both desktop and mobile.

Link: https://github.com/benbusby/whoogle-search

Laudspeaker is an Open Source Product Onboarding and Cross Channel Customer Messaging Platform that you can self host. Open Source alternative to Braze / Iterable / One Signal / Customer Io / Pendo / Appcues. Use Laudspeaker to design product onboarding flows and send product and event triggered emails, sms, push and more.

You can self-host or use our hosted offering of a customer io / braze / iterable alternative, so you can send product/ event-triggered cross-channel messages while keeping control of your customer data.

Website: https://laudspeaker.com
Github: https://github.com/laudspeaker/laudspeaker
Further Information: https://www.ycombinator.com/launches/HY2-laudspeaker-an-opensource-customer-io-braze-iterable-alternative

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Github, Docker

@joebudi said in Budibase: an open source, no code platform:

I was wondering if the Cloudron community would be interested in a Budibase add-on?

For viewers who don't know, Budibase is an open-source low code platform for building internal tools. You can connect your SQL database and generate responsive CRUD apps in a couple of clicks. You can find out more info on the Budibase Github repo.

The reason for this post is to understand the level of interest for this add-on so I (cofounder) can add weight to my proposal at our next roadmap meeting.

budibase.com

+1 on this!

@mhgcic said in Zoho ZeptoMail:

Thanks, but seems to be working fine now. I think it was their verification process. I started using zeptomail when it first came out but was very unstable.

Now works well, we have been using it up till now elasticmail. However, we found that too much abuse from robots signing people up to our mailing list caused issues with being reported as spam, now we have moved our newsletters to zoho campaigns and transactional emails to Zeptomail.

Yes, I completely agree -- they rebranded from Transmail to Zeptomail and it had seemed like it wasn't done properly, so months of issues.

I do occasionally have issues with domain verification and at random (normally fixed within a few minutes to hours) it seems to "drop" the verification. But over the past 6-8 months, that also seems to have been fixed.

For reference, if anyone else comes by this topic -- we have it configured in Cloudron as follows:

Cloudron Configuration

• External SMTP Server
• SMTP Host: smtp.zeptomail.com
• SMTP Port: 587
• Username: emailapikey
• Password: *{zeptomail-smtp-api-key} *

Retrieve / Create SMTP API Key

1. Zeptomail Console
2. Mail Agents > {mail-agent-name}
3. Setup Info > SMTP > "Send Mail API Token #"

You can already use the Cloudron API to setup app status within Uptime Kuma as well as modifying the App Error or Offline pages, if you wanted to add a link to your status page.

There might be a better way of doing this, but I'm doing it this way at the moment inside Uptime Kuma:

• Generate an API Key from your profile page (https://my.cloudron.domain/#/profile)
• Go to the settings of the app to get the AppId in the URL (https://my.cloudron.domain/#/app/{AppId}/display)
• Add a new status monitor in Uptime Kuma (http(s) keyword) and set the keyword to healthy

I personally wouldn’t mind an internal page for admins to get a quick list of apps, backups, or generic server issues with errors so easily fix things if there are issues.

+1 This looks incredible!

@fbartels Thank you so much -- that worked out perfectly!

@girish @nebulon Would it be possible to add a section to the Cloudron Docs or another MKDocs instance so we can add "community" documentation and how-to guides? I have a couple I'd like to push that way.

I've got a rough example setup to show how it might be done: https://git.cloudron.io/justinlosh/cloudron-docs/-/tree/master/knowledgebase/docs/community-guides?ref_type=heads

The only downfalls I can think of at the moment are:

• Outdated Content
• Cluttering up the docs site
• Review Process (Mistakes, Incorrect Information, Guide Testing)

Looks like they have one that is Docker-Ready: https://github.com/revoltchat/self-hosted

@robi So I did this slightly different than @fbartels did, which also seems to be working.

• Add New Monitor
• Monitor Type: HTTP(s) - Keyword
• URL: https://my.cloudron.tld/api/v1/apps/{APP_ID}/?access_token={API_KEY}
• Keyword: healthy
• HTTP Options
• Method: GET
• Body:

{
    "runState": "running",
    "health": "healthy"
}

I retrieved the AppID from going go https://my.cloudron.tld/api/v1/apps/?access_token={API_KEY}

So far this seems to be working over the past few days.

@timconsidine Yeah, I think it's been going for a bit, maybe 2021? I've tested the alpha version and to my surprise it's pretty stable, but of course they keep pushing new features. IIRC Passkeys was the last addition.

I'm planning on using it for another project and wanted to experiment with it and get something usable -- so I can work through some thoughts and ideas.

It's my first time trying to package something and I hit a problem, trying to work through it -- something permissions related with start.sh. But I'm trying to use the older Wiki.js package and port over Wiki.js 3 to see if I can get something working to play around with. If you're curious, you can take a look here.

@girish said in Cloudron Docs - Community Guides:
I submitted a PR, I'll probably work through cleaning things up and have a few other items I might be able to push in the near future. Let me know if I did that correctly -- or if I need to change anything with the PR.

+1 This would be a great addition to Cloudron!

@girish said in What's coming in 7.4:

Backup integrity

I'm really looking forward to this feature! I've been having issues with Wasabi -- timeouts and per their support "multipart uploads with inconsistent part numbers". I will be moving away from them to a different solution, but knowing that this feature is coming will be some additional peace of mind.

So this is the "quick and dirty" how to guide I've put together pretty quick. It should give you the basics to get everything running. I'm still working through a few minor issues -- such as installing addons (currently troubleshooting the composer "home" directory).

If anyone has any feedback let me know. I'll work on a polished article here in the next few days and run through another installation and get this updated.

1. To get started, install the LAMP app
2. After the LAMP app has installed, increase the memory on the app to 512mb / 1gb so that composer will run efficiently
3. Follow the guide posted on the Statamic Docs to install Statamic using Composer.
4. You will need to adjust the permissions on files and folders within the {project-directory} during the Statamic installation

chown -R www-data:www-data /app/data/{project-directory}
find . -type d -exec chmod 755 {} \; 
find . -type f -exec chmod 644 {} \;

5. You will need to update the .env file with the MySQL, Redis, and Mail user names, passwords, and server information.
6. After you have followed the above instructions, you will need to configure Apache to serve your updated "public" directory. Futher instructions can be found here.
7. For good measure, I restarted the app which seems to have solve a few minor issues.
8. After the restart, launch the terminal and cd to your Statamic directory and complete the following commands. If you need further information refer here.

cd /app/data/{project-directory} composer php please make:user

8. Update your healthcheck information by using the following information. I added the following to /app/data/{project-folder}/public/.htaccess

    # CloudronHealth Check
    RewriteCond %{HTTP_USER_AGENT} CloudronHealth
    RewriteRule ^ - [R=200]

9. Afterwards, you can login to https://{domain}/cp

For further information and resources, I would refer to the following articles:

• Cloudron Docs: Composer
• Cloudron Docs: Laravel