@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.

tootctl accounts cull --concurrency xx - removes remote accounts that no longer exist tootctl accounts prune - remove accounts that have never interacted locally tootctl domains purge <domain> - https://docs.joinmastodon.org/admin/tootctl/#domains-purge run_tootctl statuses remove --days=xx - https://docs.joinmastodon.org/admin/tootctl/#statuses-remove tootctl media remove --days <days> --concurrency <concurrency> - https://docs.joinmastodon.org/admin/tootctl/#media-remove

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

non-answer: we recently got cloudron.social and intend to move there. I haven't heard to scaling issues. But in any case, you are able to move things in and out of Cloudron Don't think there is anything that is as mature as Mastodon. Some alternatives: https://github.com/superseriousbusiness/gotosocial , https://akkoma.dev/AkkomaGang/akkoma , https://github.com/jointakahe/takahe , https://pleroma.social/

@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.

What is it that you are trying to achieve What did you do to get to your current state Provide a step by step level so people can understand what you do - maybe use a service like https://asciinema.org/

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.

BTW (back to the topic of this thread):
Mastodon 4.1.1 has just been released. 😬

@nebulon i've identified the issue and it was my S3 configuration.

The endpoint and hostname should never have the bucket name.

S3_ENDPOINT=https://s3.us-west-001.example.com
S3_HOSTNAME=s3.us-west-001.example.com

@girish great that works! remember to rebuild the feeds and redeploy elasticsearch if that's in use.

@matwinck you have to make someone an admin - https://docs.cloudron.io/apps/mastodon/#admin

@alwynispat sure of course:

Puma

export WEB_CONCURRENCY=4 # number of worker processes
export MAX_THREADS=5 # the number of threads per process

Streaming API

export STREAMING_CLUSTER_NUM=2 # number of worker processes

Sidekiq

export SIDEKIQ_THREADS=4
export DB_POOL=25 # must be at least the same as the number of threads

@RazielKanos said in deleting old crap:

Heyas, I just ran a cleanup and was amazed that of my nearly 10GB it just deleted 60 MB(!) of cached files and 800 KB of preview cards. How can I get rid of all the crap lets say... order than 2 months? can't be all 5GB in the database, right?

tootctl media remove and tootctl statuses remove are run in the background with Mastodon v4 (settings can be found on the administration page).

What I am running every night (via cron job) is:
/app/code/bin/tootctl media remove-orphans
/app/code/bin/tootctl preview-cards remove --days=7
/app/code/bin/tootctl cache clear
/app/code/bin/tootctl accounts prune
and now with v4.1:
/app/code/bin/tootctl media remove --prune-profiles --days 7

My instance has around 40-50 users and is connected to 8 public relays.
It is about 50 GB in size now (it was 80-90 GB with v4.0).
Hope that helps.

I have it up and working with the new Cloudron LibreTranslate app. Running on the same Linode as my Mastodon.

https://forum.cloudron.io/topic/8527/libretranslate-with-cloudron-mastodon-server/1

@girish I've disabled backups for now as I try and work out why there is an issue with it. My Linode backs up daily at the moment so worst case I recover the whole system.

@dxciBel said in New external users sometimes don't receive confirmation mails:

Not that I know of. User management was left to the app during install.

Phew. I think you should be OK then! Ignore me.

https://www.reddit.com/r/Mastodon/comments/yzp1qz/mastodon_server_hardware_requirements/

This is a discussion on Reddit about what it takes to host a Mastodon instance (Mastodon uses the ActivityPub protocol). The requirements are quite high. One large instance with 29,000 users is hosted on this hardware:

2 AMD 5950 16c/32thread 128GB ram with nvme ssds running sidekiq jobs
1 AMD 5950 16c/32thread 128GB ram with nvme ssds running elasticsearch and redis
1 AMD 5950 16c/32thread 128GB ram with nvme ssds running Postgres DB
2 AMD 5950 16c/32thread 128GB ram with nvme ssds running PUMA (mastodon web app) and nginx (only one is currently powered on - other is being reworked
1 AMD Epyc 32c/64th 400GB ram with 10TB of nvme ssd acting as a s3 storage provider and another nginx/PUMA web front end

This is a total of 96 CPU cores! Another person with 500 users says,

"For those interested in a data point, I am running an instance with nearly 500 users. Currently running on an AWS Lightsail instance with 4GB Ram, 2 vCPU, for $20/month, and an S3 instance for media storage (1TB - nearly full) for $3/month. I am constantly monitoring resources - as the system is running well but nearly topped out.

I will likely be moving to 8GB RAM, 4 vCPU instance, and 2TB S3 in the coming weeks."

These requirements are quite high. I also recently learned that bandwidth is a continuous 1-2 Gbits/s. No wonder Mastodon is having trouble keeping up with the influx of Twitter users!

@alwynispat you've got DB_POOL specified twice 🙂
I'm doing:
be945764-0726-41d0-8886-d387d17c123a-image.png

@b2breporter Oh - not totally sure, but I think we figured it out. We were originally trying to post images that were much larger in file size.

@alwynispat do you mean nginx? How is NPM involved here?

edit: oh, maybe you mean your nginx proxy manager?