#s3fs — Public Fediverse posts

#s3fs 1.96 released with improved performance and FUSE 3 compatibility: https://github.com/s3fs-fuse/s3fs-fuse/releases/tag/v1.96

Jellyfin Web на своём сервере. Фронтенд для медиастриминга

Многие из нас первым медиасервером устанавливали Plex . Но это коммерческое решение. Некоторые считают, что в последних версиях он изменился к худшему : например, заставляет регистрировать аккаунт, логиниться через центральный веб-портал, передвигает пользовательский контент в подменю, рекламирует собственные продукты и сервисы, выкатывает ненужные функции. Поэтому для медиасервера лучше выбрать опенсорсную программу, как Jellyfin .

https://habr.com/ru/companies/ruvds/articles/909074/

#ruvds_статьи #Jellyfin_Web #Jellyfin #Plex #Infuse #s3fs #Kodi #JellyCon #Astiga #MusicSync #CloudBeats #YouTube #Tubesync #ytdlp #ytdlsub

Jellyfin Web на своём сервере. Фронтенд для медиастриминга

Многие из нас первым медиасервером устанавливали Plex . Но это коммерческое решение. Некоторые считают, что в последних версиях он изменился к худшему : например, заставляет регистрировать аккаунт, логиниться через центральный веб-портал, передвигает пользовательский контент в подменю, рекламирует собственные продукты и сервисы, выкатывает ненужные функции. Поэтому для медиасервера лучше выбрать опенсорсную программу, как Jellyfin .

https://habr.com/ru/companies/ruvds/articles/909074/

#ruvds_статьи #Jellyfin_Web #Jellyfin #Plex #Infuse #s3fs #Kodi #JellyCon #Astiga #MusicSync #CloudBeats #YouTube #Tubesync #ytdlp #ytdlsub

Loooooooooks like my #s3fs cache plan for #mastodon is working... gotta let it run for another few hours and see what happens.... but I think we're onto somethin!

As a shortcut while I'm trying to get #Wasabi to lift the public access restriction, I'm implementing #s3fs on the local server and I'll have to let things make the long round trip... we'll see how it effect user performance when it people hit the #Mastodon instance. (my dev instance of course)

Hmm. With some tuning, I'm able to saturate one of the lanes of my #100GbE link using #s3fs. So full #25GbE. Now, to figure out how to get it to use all 4 lanes. Does anyone have suggestions?

#homelab #s3 #storage

Thinking further about the Nextcloud rollout:

Much of the stuff I was considering storing on s3fs is already there. And if I switch to an alternate object-storage-based filesystem, such as JuiceFS, the migration process should be nothing more than a simple copy, followed by remounting the storage on the same mount-point. Nextcloud doesn't actually need to know how the backend works -- just that it looks like a filesystem.

So there's no risk to just sitting pat with what I have.

Also, even if I move it to another type of filesystem, I'll still have the filesystem level access to the data, so migrating to another system or integrating with other software should be simple.

In fact, migrating out of Gitea should be a simple matter of doing a checkout onto the external storage. If the performance really does suck, I can then copy it to another external storage within Nextcloud (I think).

The rest of the material I want to store in Nextcloud is small enough that there is no real reason to put it into object storage. And there is one reason not to: surely it is more secure to keep private "office" documents on the same server (if I need to upload them at all, that is).

And finally, it appears that there isn't enough reason to keep using ResourceSpace , since Nextcloud replicates the key features I would have been using it for. Instead, I should probably be looking at the available Nextcloud apps to see if I can fill in any gaps in functionality (mainly the ability to read and extract metadata and preview information from a range of file types).

So it looks like I may not even have to reinstall Nextcloud. Just invest some time in organizing and tagging.

#VirtualStudio #Infrastructure #Nextcloud #s3fs #JuiceFS #Gitea

Does anyone have working tips on how to get Mastodon running with S3 Object Storage? I can get it working fine for adding images/data to posts, but when they're re-read, I seem to be missing something ...

#mastodon #devops #s3 #s3fs #s3objectstorage #config

@thomas

I am using S3 storage with PeerTube. The current version offers two methods of integrating S3 storage: “Native object storage” and “Old object storage method”.
https://docs.joinpeertube.org/admin-remote-storage

When experimenting with native object storage, I observed that my browser makes direct connections to the S3 storage provider. For privacy reasons, this is not what I want. I strongly prefer self-contained websites.

So I switched to the old S3 storage method that relies on #s3fs, and activated its cache. It works well.

The S3 integration offered by Mastodon and described in your post reminds me of the native object storage method of PeerTube. Does this mean users will have to make direct connections to the S3 storage provider?

#S3 #objectStorage #Mastodon #PeerTube

s3fs vs native S3 API access for Mastodon? 🤔💾

#mastodon #s3fs #s3 #objectstorage #objectstore #performance

#PeerTube et #S3FS, ça ne fonctionne plus du tout. Je ne comprends pas pourquoi, mais c'est devenu impossible de faire les montages comme décrit ici : https://docs.joinpeertube.org/admin-remote-storage

#S3FS
https://s3.wasabisys.com/s3.peertube.fedi.quebec/cafonctionne.txt
:flan_cool:
Restera juste à tout copier de S3QL à S3FS... :flan_tired:

Je voudrais faire cette #migration #S3QL -> #S3FS, mais je me rends compte du temps que ça prendra. Clairement plusieurs (dizaines?) heures.

J'aimerais pouvoir m'assurer que les trois dossiers dans storage ne changeront pas pendant la copie, mais je ne trouve nulle part dans #PeerTube un moyen de rendre l'instance en "semi-maintenance" disons, c’est-à-dire que toutes les fonctions restent activent, excepté l'envoie de nouvelles vidéos temporairement suspendue pour tous les utilisateurs.

Je crois que je vais devoir migrer de #S3QL à #S3FS...

J'ai eu l'idée d'utiliser S3QL avant que la doc de PeerTube propose de le faire avec S3FS.
https://docs.joinpeertube.org/admin-remote-storage
S3QL chiffre ,compresse et découpe en fichiers séquentiels de 10Mo qui sont donc inutilisables sans repasser par S3QL pour lire.
Mais c'est surtout que ces étapes ajoutent beaucoup de pression sur le CPU, peut-être même plus que le transcodage des vidéos, si on en juge par ce test de direct.

@dada Puisque j'y songe et que t'es le seul à avoir tagué #s3fs (du moins dans la BdD de mon instance), maintenant que PeerTube le propose (https://docs.joinpeertube.org/#/admin-remote-storage), as-tu essayé? Moi j'utilise S3QL depuis environ un an avec mon PeerTube et il y a certains ratés. Particulièrement quand Wasabi fait des siennes...

Je viens de parler de mon idée de faire le switch : https://mastodon.fedi.quebec/@manu/104413573295029166

cc: @mrjack

Avec la dernière mise à jour de :peertube: #PeerTube, je songe passer de #S3QL vers #S3FS pour mon bucket chez :wasabi: Wasabi et ainsi outrepasser le chiffrage des vidéos et donc la nécessité d'utiliser le VPS comme proxy d'accès au bucket. Ça devrait épargner énormément de bande passante et le CPU du VPS.
https://docs.joinpeertube.org/#/admin-remote-storage
#SysAdmin