Best posts made by benborges

Live Demo ·

https://github.com/ShaneIsrael/fireshare

it's working !!

I have nocodb reading this sqlite file and I can add layers of data on top while tg-archive is feeding new posts to the base itself,

tldr :

I have tg-archive running at /home/tg-archive/

there I have a site folder that sync from telegram and output static sites.

But I wanted to be able to have research, filtering, sorting with a simple front-end, that's where nocodb comes in.

All I did was a clean symlink for yellowtent user/group from /home/tg-archive/sites/telehunt/ to /srv/telehunt/

ln -s /home/tg-archive/sites/telehunt/ /srv/telehunt

sudo chown -h yellowtent:yellowtent telehunt/ inside /srv/

then I added this as filesystem mount in the volumes view pointing to /srv/telehunt/ with name telehuntsrv

next I attached this volume to the nocodb container, when it's running, I added the path to the sqlite file /media/telehuntsrv/data.sqlite

And voila

(warning, war content) My test use case : http://osintukraine.com:9090/#/feed (use incognito to accept the self-signed cert)

I have a question for @girish maybe, I'm going to package Fireshare code for cloudron
but I'm wondering if by using the .env provided I will be able to point the //path/to/my_game_clips: folder (source)
to another cloudron LAMP container (running the scrapping of videos) such as /home/yellowtent/appsdata/cc81fa5c-a060-4fb8-bcaa-c13b009b0c43/data/public/media

docker run --name fireshare -v $(pwd)/fireshare:/data:rw -v $(pwd)/fireshare_processed:/processed:rw -v /home/yellowtent/appsdata/cc81fa5c-a060-4fb8-bcaa-c13b009b0c43/data/public/media:/videos:rw -p 8080:80 -e ADMIN_PASSWORD=your-admin-password -d shaneisrael/fireshare:latest

This is the test link above, I'm currently running and it works fine outside of a cloudron package so i'm wondering, can I have variable pointing to another data volumes on a different app/container?

@nebulon Testing it!

This is really neat because the numbers of node/third-party connectors from the community are really interesting to use !

It seems there is now a fork of Gitea here : https://codeberg.org/forgejo/forgejo

Oh my god I love cloudron ! Solved !

@murgero I wish Cloudron would have some kind of native integration with self-hosted ntfy.sh

that would be dope, to organize events alerts

Would love a ntfy.sh integration for this, much easier to "consume" and stay alert on than email in my opinion

@potemkin_ai It seems ntfy is now available in the app store :)))

it would be really neat to be able to use ntfy priority management of notifications to on the cloudron side define which notifications are more important than others, so to be able to have silent notifications or very visible popup notification for more important alert, but I guess for this to work, Cloudron should have a notification API that could integrate at the cloudron level with ntfy ?

@girish Oh that's really great !
I use different jitsi for different domains, for very small team but it's really neat if I could host two in the same server !

@dev-cb Ohhh this is exciting, wondering what happens if N8N gets an upgrade that breaks a community node..what would be the upgrade path? wait for community node upgrade, then upgrade existing installed custom packages and restart N8N ?

Well I don't know but /SRV with proper permissions (yellowtent) works !
I can finally see the content of the mount from the file manager.

Maybe my problem is that I have to remount these volumes now that I changed ownership ?

anyway, will try some more but this is a good step forward :

@nebulon you're right, probably a network glitch

solution :
so I edited the cloudron-setup file, modified the line number 70 variable redo="false" to "true" and ran the install again, it all went flawless.

@Supaiku When I needed filesystems mount a few months ago (on top of sshfs mounts) I remember I struggled quite a bit to mount filesystems folders, but one thing worked :

• Create /srv/YourFolder
• Symlink that folder to the folder you want on the filesystem
• mount that path inside Cloudron

That's how I read SQLite files from other apps from say NocoDB or other cloudron apps.

@girish Thanks for taking the time to ponder on this !

Yes you got me right and I understand why it's not possible in the case of nocodb.

just FYI, the path nocodb use in the cloudron context to store uploaded files is
/app/data/nc/uploads/noco/{NameOfTheDatabase}

Your suggestion to link directly to the LAMP or to a static "mirror" of this is the path I finally went with, it's was the logical step since provided I can link to it, where the media is does not matter much.

i'm not yet releasing this publicly but it's coming !

Thanks for the help!

@BrutalBirdie Can you just describe how your Zabbix system is running, I'm guessing outside of the cloudron vps right ?

@girish That would simply be amazing !

So on Friday I launched an upgrade process to move from Ubuntu 20 to Ubuntu 22.
I followed the doc here https://docs.cloudron.io/guides/upgrade-ubuntu-22/

And everything appears to be going as planned, but the recreating containers script part is running since Friday and is still not over, progress is still ongoing, I see little dot on my terminal displaying fine every few seconds but I have no idea what this script is doing, there is nothing that indicate containers are being regenerated, the box is literally doing nothing but printing dots on my terminal.

I'm worried of interrupting the process, I don't know where I am in the process.

I obviously have full backups and snapshot ready, so I can go back anytime but if I can get this done and finished, I'd rather stay on Ubuntu 22.

Any hint, is it normal that this container cgroup v2 recreation is taking.....Days & Nights ?

I had perhaps some 40 containers running, some bigger than others, but nothing out of the ordinary.

Does it matter for this recreation ?

box.log output this every few minutes, so I'm thinking the recreation is ongoing and when it's done it should start the platform following the script directive...

Friday night, saturday, night, sunday, night, Monday morning and it's still printing dots...

2022-09-12T06:53:23.963Z box:locker Lock unreleased platform_start                                                     

@ajtatum correct, but that's not a cloudron limit, that's how cloudflare & DNS work
the MX can never be proxied hence, somewhat nullifying the whole idea ??

in my usecase, the only solution I have found is for anyone that attempt to resolve my IP directly is sent to my.cloudron.domain (hence cloudflare proxied) but there is nothing you can do for the MX.

@girish I'm not sure what to say, the community nodes UI is there, live on the cloudron package, but without being able to test an install and subsequent N8N upgrade I'm not sure how I can provide more information

I went and stopped the process, started it all over again but this time I managed to catch that there is a problem with the script right at the beginning, I can't have the log file because I reverted back to my snapshot of Ubuntu 20

But the error is about docker network not being able to get an IP fro the box network and when it try it fails but then continue with the "recreation" of containers as if the previous step had worked properly ?

@kevin-k Strange...can you try to revert back to a working backup, reinstall community modules again, reboot once again and go to that page see if everything stick ?

I had issues first time I installed, had to reinstall once, but then it went smooth...

When I realized I had been waiting for nothing for 4 days I reverted back to snapshot, so now I'm on Ubuntu 20 and I can't find anything.

but it's very clear that the process was going on for ever, without even the docker running (even tho the service was active and loaded)

@girish I'm using cloudron + CF for osintukraine.com, these consideration are super important in adversarial environments, (the question here is not about CF ethics etc..I'm fully aware of them, but still had to use CF for a bunch of very valid reasons)

So yes, the proxy at setup of the app itself would definitely help CF users, I can confirm that every installed app in a CF handled domains, requite to login to CF and manually set proxy enabled.

Since cloudron has full access to CF via the API it would be perfect to allow to set the proxy from the get go, including for the my subdomain.

The problem I'm seeing is that my subdomain is also the MX dns entry
so even if all apps get proxied properly from the start, the MX entry in itself almost render the use of CF + Cloudron useless in a very critical environment.

OSINTukraine will be moved back to registrar DNS because ultimately, my domain is already burned, the only thing that kinda save me is that I setup a system that redirect any direct targeting of the box IP back to CF, but again, my IP is burned.

1 year after, I can say that the environment does not seem to be that dangerous for the project I'm running, hence considering to move back.

@girish Oh great, that seems good then, happy to test it when it's available !

@girish So this is what's happening on the CF side when a cli command is ran :

For now the temporary fix is to create an IP access rule that make an exception for my ASN, waiting for CF to advise on the best way to implement this at a more granular level.

This can be set to solved !

Cloudflare reply :

curiously, other Nextcloud app on the same cloudron are upgrading in automated mode just fine, so that should be a hint that it's maybe a particular nextcloud app provoking this in this particular nextcloud.

i'll debug some more and try to update again with debug true at the get go and see if I can catch something

Also removed

wp-content/plugins/disable-wordpress-core-update

and a rss plugin throwing some errors, updated to latest package and i'm up and running !
Thanks all

@girish This is exactly what I was looking, even better because I don't have to replace any of my path now, this is actually perfect, thank you very much for taking the time to test it !

demo here https://russia.osintukraine.com/#2022-06-11

@nebulon This was a strange episode, still unclear what happened, but everything "came back" to normal for some reason.