Post by @shom

Hello little One's 😎 😎

Just got in and trying things out..

Replying to @stefano

@stefano @madamada welcome! Little One is a great name for the test instance.

Replying to @shom

@shom
I agree, however, I hope this server will stay permanent, not just as a "test environment" :)

@stefano @madamada

Replying to @fasnix

@fasnix @shom @madamada this server will be permanent.
I'm planning to add a "public" server. I'm not sure if it will be this (using sqlite, we could hit some limits) or another one, using PostgreSQL, ready to scale.

But yes, this is our littleOne and will stay.

Replying to @stefano

@stefano
If you add a public server, would you aim for it to accept an "unlimited" amount of users, or would you rather restrict it to, say, 100 / 500 / 1000 users?
(Where are the limits for sqlite?)

@shom @madamada

Replying to @fasnix

@fasnix @shom @madamada I don't know 😃 Some local automated tests show that 100 users with sqlite are fine, as long as there's not too much concurrency in writing stuff into the DB. For the public server....I don't know as well. The limit will probably be the limit of the hardware I'll be using. There's something to be fixed: blog generation will only work on single process installations, not on clustered setups. I'll probably easily adapt it to build blogs only on one specific machine (the one doing the housekeeping). Still, the blogs will finish into the local file system, so this needs to be sorted, too. But this will come later.

Replying to @stefano

@stefano @fasnix @shom @madamada another solution could be put the blog files into the s3 storage, too (if configured) and serve them just proxying the files.

Replying to @stefano

@stefano good conversation here. I'll share my perspective, it would be nice if the posts and blogs are treated the same from a storage perspective so the admin can just back up one location. I really like the tiered approach for serving external media, storing / serving internal vs external media would be a good separation to have.
@fasnix @madamada

Replying to @shom

@shom @fasnix @madamada the backup procedure is already backing up the blogs, so we’re covered. And yes, that’s a good approach. I’ll try to put it into the todo list. Thanks!

Replying to @shom

@shom @fasnix @madamada Built-in backups of the database, the configuration and, optionally, local owned media, with a manifest and a restore command.

You can fully export all your contents (including posts) and re-import them into another littleFedi instance. It'll be another account with another handle, but you won't lose any of your contents. Your data stays yours.

#OwnYourData