Cloudron Forum

• Title: flohmarkt on Cloudron - A decentral federated small advertisement platform

• Main Page: https://codeberg.org/flohmarkt/flohmarkt
• Git: https://codeberg.org/flohmarkt/flohmarkt
• Licence: AGPL
• Docker: Yes
• Demo: https://codeberg.org/flohmarkt/flohmarkt/wiki/flohmarkt-instances

• Summary: The name flohmarkt is a german word and translates to flea market or garage sale in english. This is a symbol for each flohmarkt being meant to be a small place for a somehow connected group of people. All the flohmarkts willing to federate make up one big place for small advertisements about exchange of goods and services.
  flohmarkt as its project name is written in lower-case letters.
• Notes: I would like to run my own flomarkt as I do not want my listings to be in the grace of some admins who can just take them down (like kleinenziegen.de o bea does if you miss something in the description)

• Screenshots:

Oh, forgot to mention @nebulon

I just happen to recognize it now. Thanks @girish!

After creating a new key and configuring it in app.ini and restarting gitea I still get an error:

root@0f44f577-d0e0-42e6-a371-d3914aba0014:/home/git# sudo -u git bash
git@0f44f577-d0e0-42e6-a371-d3914aba0014:~$ export GNUPGHOME=/app/data/appdata/home/.gnupg
git@0f44f577-d0e0-42e6-a371-d3914aba0014:~$ gpg --list-keys
/app/data/appdata/home/.gnupg/pubring.kbx
-----------------------------------------
pub   rsa4096 2025-01-21 [SC] [expires: 2027-01-21]
      EF80C8DE297670B7E8C0360108DA2115185FFD9C
uid           [ultimate] jascha.wtf Gitea <git@git.jascha.wtf>

section of app.ini:

[repository.signing]
SIGNING_KEY = EF80C8DE297670B7E8C0360108DA2115185FFD9C
SIGNING_NAME = jascha.wtf Gitea
SIGNING_EMAIL = git@git.jascha.wtf
INITIAL_COMMIT = always
CRUD_ACTIONS = pubkey, twofa, parentsigned
WIKI = never
MERGES = pubkey, twofa, basesigned, commitssigned

GITEA__REPOSITORY__ENABLE_PUSH_CREATE_USER=true

From the log:

Jan 21 10:45:28 Error: exit status 128 - error: gpg failed to sign the data
Jan 21 10:45:28 fatal: failed to write commit object
Jan 21 10:45:28 - error: gpg failed to sign the data
Jan 21 10:45:28 fatal: failed to write commit object
Jan 21 10:45:28 2025/01/21 09:45:28 ...ers/web/repo/repo.go:217:handleCreateError() [E] CreatePost: initRepository: initRepoCommit: git commit: exit status 128 - error: gpg failed to sign the data
Jan 21 10:45:28 fatal: failed to write commit object
Jan 21 10:45:28 - error: gpg failed to sign the data
Jan 21 10:45:28 fatal: failed to write commit object
Jan 21 10:45:28 2025/01/21 09:45:28 ...eb/routing/logger.go:102:func1() [I] router: completed POST /repo/create for 82.140.42.234:0, 500 Internal Server Error in 55.3ms @ repo/repo.go:222(repo.CreatePost)

Update: Gitea does not get the signing key. The response of https://git.jascha.wtf/api/v1/signing-key.gpg is empty

My best guess is that there are some path poblems - https://docs.gitea.com/administration/signing

Oh, no, my key is gone. That is odd as I never touched the key after it worked.

@nebulon I now get a new error:

root@0f44f577-d0e0-42e6-a371-d3914aba0014:/home/git# sudo -u git bash
git@0f44f577-d0e0-42e6-a371-d3914aba0014:~$ export GNUPGHOME=/app/data/appdata/home/.gnupg
git@0f44f577-d0e0-42e6-a371-d3914aba0014:~$ gpg --list-keys
gpg: WARNING: unsafe permissions on homedir '/app/data/appdata/home/.gnupg'
git@0f44f577-d0e0-42e6-a371-d3914aba0014:~$

This is odd - after working for a looong time I suddenly get this error when creating a repository and initializing it:

CreatePost, initRepository: initRepoCommit: git commit: exit status 128 - error: gpg failed to sign the data
fatal: failed to write commit object
 - error: gpg failed to sign the data
fatal: failed to write commit object

I first thought that maybe the key is gone. By checking this I found that:

root@0f44f577-d0e0-42e6-a371-d3914aba0014:/home/git# sudo -u git gpg --list-keys
gpg: Fatal: can't create directory '/home/git/.gnupg': Read-only file system
root@0f44f577-d0e0-42e6-a371-d3914aba0014:/home/git# 

I have not changed anything and I do not know when this happened as I was not using my git for the last ~9 months.

Any idea what is going on @nebulon?

Hi there,

when I saw this post

@girish said in Vaultwarden - Package Updates:

[1.17.0]

• Full changelog

I went to read the changeling to find the following in the general section:

Bitwarden has changed the push API endpoints which affects the EU region endpoint users. So if you use the push functionality and use the EU region you need to make some changes.
You have to update push.bitwarden.eu to api.bitwarden.eu.
This is also an issue with any previous version of Vaultwarden.

That made me curious and I went on to look who this push thingy thing is doing.
I found this Wiki entry about Enabling Mobile Client push notification.

This would be awesome! To get this we would need some new environment variables in the docker file and be able to change the values - made it could be a tab in the app view in cloudron.

Thanks for considering!

Hi!

I would love to be able to enter a git repository or an URL to a file which are pulled regularly to manage my robots.txt

It is a little bit pain to update every running app when there is a new crawler which need to be blocked. I maintain a repository for myself but need to copypaste manually into cloudron.

Bonus would be if you could merge two external files to one robots.txt

Thanks for considering this

@girish this worked for me, thanks.

If someone can tell me how I can manipulate the array that plugins from /app/data/customconfig.php are loaded first because I have nearly no clue about php.

Hi!

I want to use the "Nextcloud Attachment" plugin (see here) because it would be great to have it.

Unfortunately it needs to be loaded before any other attachment plugin. From the readme:

When enabling the plugin make sure to place it before any other attachment plugins like filesystem_attachments E.g.

$config['plugins'] = array('nextcloud_attachments', /*...*/ 'filesystem_attachments', /*...*/ 'vcard_attachments' /*...*/);

At the moment the plugins coming with the package are loaded like this:

$config['plugins'] = array('acl', 'archive', 'attachment_reminder', 'emoticons', 'managesieve', 'markasjunk', 'newmail_notifier', 'vcard_attachments', 'zipdownload');

I would suggest:

• Create an empty array for the plugins
• require_once "/app/data/customconfig.php";
• array_push($config['plugins'], 'acl', 'archive', 'attachment_reminder', 'emoticons', 'managesieve', 'markasjunk', 'newmail_notifier', 'vcard_attachments', 'zipdownload')

Could that be possible?

deSEC is a new and free DNS provider https://desec.io

The have an API https://desec.readthedocs.io/en/latest/

I really like them and it would be great to use them with Cloudron

Everyone else: Give them a try!

@girish At the moment you need the Pixelfed Live App to stream. Get the apk here: https://dl.apps.pixelcdn.net/pixelfed-live/android/pixelfed-live-v1.0.1-release.apk

As far as I know it should be merged into the iOS and Android App but I do not know the status at the moment. I asked upstream to provide some more info.

@jdaviescoates yes, I am aware of Pinafore, I just do not like it this is what I love about the fediverse: there are so many clients for most AP-based the hints that folks can choose from.

Sorry for my absence - I will go through this thread tomorrow and see what needs to be done because so already was able to stream (on another instance)

I would love to get Elk self hosted.

Elk is an alternative frontend for Mastodon/Pleroma and though it is in Alpha it is more than stable.

https://github.com/elk-zone/elk

@girish said in Cloudron SPF record does not permit IP:

@jaschaezra @matix131997 I could reproduce this one. Looks like Haraka outbound is adding that header. Note that this is not a problem for mail delivery as such, but it's not nice that the mail client IP is revealed for no reason. Looking into a fix.

And it gives a SPF-Soft-Fail which can at worst lead to being rejected.

@girish sorry but I have to ask: any update on this?

@nebulon said in sitemap.xml:

@jaschaezra generally we try to stay as close as possible to mainline upstream, to avoid unexpected behavior and more importantly stay on the maintained packages. Too often forks or extra modules become abandoned, making it hard to update the package later on.

I do understand that but there is nearly no chance to add other tools as a server admin except forking the package and adding the missing stuff.

It would be great if there would be a way to add new stuff to an existing package without having the maintenance hassle. Like "add to existing app" or something like this.