@nebulon Thanks! It's been running on Cloudron since 1.4.2 (Mastodon 3.2.1) and it's been auto updating like clockwork since then. It was a fresh install back in the day with no migrations. I'll do some more investigation about the DB issue (I'll use the official upgrade FAQ now) and report back if I find a fix.

@redegelde said in How to install Elasticsearch on Mastodon?:

For the time frame, when will Elasticsearch become avaible or not

As @girish said it's not yet on the roadmap, so I don't think it'll really be possible to guesitmate the time frame.

@redegelde said in How to install Elasticsearch on Mastodon?:

i understand this is needed with the 4.2 version

To be clear, it is not required by 4.2 (as in you can use 4.2 without it). But yes, it can be used with 4.2 and the Cloudron package for 4.2 is already available.

Package is out.

Yes package update is out by now.

Updated package is out.

Never heard about this. Besides, I don't think adding Google Analytics is something that would be welcomed by the Mastodon community.

@nebulon yes with fresh installed mastodon instance it's working fine. Thank you

@mhgcic said in Cloudron + Mastodon + Akamai s3:

We added this solution already and did not work.

S3_ENABLED=true
S3_BUCKET=bucket-name
AWS_ACCESS_KEY_ID=<key_id>
AWS_SECRET_ACCESS_KEY=<secret_key>
S3_REGION=<region>
S3_PROTOCOL=https
S3_HOSTNAME=<hostname>

You seem to be missing the S3_ENDPOINT

They were already applied in https://git.cloudron.io/cloudron/mastodon-app/-/commit/56896d2d63cd22fb5870b11e7394936f5ca7c1c5

@girish next one
https://github.com/mastodon/mastodon/releases/tag/v4.1.4

@dsnradio We do that to prevent source code from being changed either intentionally (user) or malicously (hacker). For the former case, it's to make sure apps can be updated reliably. For the latter, it's for security.

If you want to modify an app , you can build the package yourself - https://git.cloudron.io/cloudron/mastodon-app/ and do whatever changes. Of course, you have to take care of updates as well for the custom installation.

Wow okay. Thank you

@nichu42 good link...

I had a look at https://codeberg.org/Fedimins/mastodon-maintenance-tasks . I couldn't run the script directly because there's a bunch of hardcoded paths in it. Found some commands that maybe we can incorporate. Many of the commands are already in our cleanup script.

(waves) See https://www.thedoodleproject.com/relay for instructions!

@DeBossNow
The path mentioned by @girish is like he said:

@girish said in Can not locate Mastodon app core folders:

in a container and thus each app's filesystem is independent and separate

So your statement:

@DeBossNow said in Can not locate Mastodon app core folders:

I have sftp access to the root of my entire website linux volume, which contains all of the folders of dependencies. I see the Cloudron installation and its dependencies. The entire file structure of my website server is open to me. There is no other volume adjacent to this Linode volume. Nothing can exist outside of this root in my server volume.

Is still factually wrong, since you seem not to know or understand that each container has their own filesystem in their isolated container environment.
So even if you have root access to your server, you will not find /app/code in the servers filesystem.
Since there are isolated and it's inside the container and read-only.

And yes you can still access each container like he even explained to you how you can access the filesystem:

@girish said in Can not locate Mastodon app core folders:

To navigate the filesystem of the app, use the web terminal. Usually, the package keeps the code in /app/code by convention. Note that code is readonly in Cloudron, you cannot change it.

What do you wish to achieve here?
There is a big documentation for Cloudron: https://docs.cloudron.io/ which explains almost everything.
Adding to that the Forum has many resources which already answer almost any of your questions.

And yet it seems to me, you simple choose to ignore all the provided resources for self education and demand support on a level which is unreasonable for a forum request.

Personal note:

The community behind Cloudron and FOSS in general is very forgiving when you show the effort, and when you reach out for help, they almost always respond. (not always in the nicest way, since they maybe seen this question for 50x time, but they still respond to help out.)

So I recommend to you, show some more effort or at least write your request in a more descriptive way.

Since I preached about resources and self education - here is some material:

About the Cloudron Filesystem:
https://docs.cloudron.io/storage/

About the Mastodon app and federation:
https://docs.cloudron.io/apps/mastodon/

The Mastodon Cloudron Forum category:
https://forum.cloudron.io/category/41/mastodon

@DeBossNow I think maybe something is getting suck in the setup. Can you check /home/yellowtent/platformdata/logs/box.log ? You can do a systemctl restart box in another terminal and check what the logs are saying.

@jaschaezra I understand the urge for this, however unless the app has a solid plugin or extension system for this, we can't really support this, as it will make it impossible for us to test for updates and thus will introduce another maintenance hassle on top, which in our experience leads to various side-effects which are hard to debug and cause quite a lot of support burden.