Spyke

Replies

Comment on

Mastodon's Next Major Release Enables Full-Text Search

Reply in thread

It also adds to the deployment complexity even more. Just from memory, to run Mastodon you need:

  • any number of Rails web servers (horizontally scalable)
  • any number of Sidekiq worker processes (horizontally scalable)
  • a PostgreSQL database for persistent storage (vertically scalable modulo sharding)
  • a Redis server for caching and Sidekiq (vertically scalable modulo sharding)
  • a Elasticsearch server for full text search (vertically scalable modulo sharding)

So this is at least 5 different server processes to manage, In reality for almost all deployments, Redis and Elasticsearch are unnecessary; the database can be used for jobs and full text search. Further, it could even be SQLite for all but large instances.

The deployment story for Mastodon is a nightmare and a substitute like Pleroma or even better something in Rust is necessary.

Comment on

I messed up with the `/` diretory

Reply in thread

Yes to rsync. It will update the destination files in place without deleting the source files (unless you provide that flag -- don't.)

You might actually be screwed if you ended up overwriting the EFI variables in /sys/firmware/efi/efivars. See https://unix.stackexchange.com/questions/414799/efi-variable-entries-in-sys-firmware-efi-efivars.

If you still have all your files backed up, it might be easiest to reinstall the base system and then selectively copy back over the directories you want with cp -a. Sorry to be the bearer of bad news, but if you can't even attempt to boot, that's not good.

Comment on

I messed up with the `/` diretory

Reply in thread

I'm not sure if this is the problem, but it might be that cp -r creates the new files according to the current user's umask and uid/gid. Which, if done from a live CD, would be a user that does not exist on the system when you try to boot it. What you want is cp -a.

https://unix.stackexchange.com/questions/44967/difference-between-cp-r-and-cp-a

You might be able to correct this without re-copying everything by using rsync. I don't recall the incantation off-hand (you'll want to google it) but I think you want rsync --partial --archive.

https://serverfault.com/questions/141773/what-is-archive-mode-in-rsync

Edit: Would also help to know if you are getting any error messages at boot time.