@stefano need some #mastodonhelp am running my #mastodon on my own little #FreeBSD server.
Uncategorized
4
Posts
3
Posters
0
Views
-
@stefano need some #mastodonhelp am running my #mastodon on my own little #FreeBSD server. Since the port is no longer maintained, any advice on how to upgrade and maintain? Even with ports every upgrade I've done so far has been a real problem requiring me to start my server over or manually migrate the SQL database. I'm currently on 4.3.6.
-
@stefano need some #mastodonhelp am running my #mastodon on my own little #FreeBSD server. Since the port is no longer maintained, any advice on how to upgrade and maintain? Even with ports every upgrade I've done so far has been a real problem requiring me to start my server over or manually migrate the SQL database. I'm currently on 4.3.6.
@tj hello! I think you could try to install it using my tutorial: https://it-notes.dragas.net/2022/11/23/installing-mastodon-on-a-freebsd-jail/
Then, point it to your current media directory, redis and database servers. It should be working.
-
@stefano need some #mastodonhelp am running my #mastodon on my own little #FreeBSD server. Since the port is no longer maintained, any advice on how to upgrade and maintain? Even with ports every upgrade I've done so far has been a real problem requiring me to start my server over or manually migrate the SQL database. I'm currently on 4.3.6.
In fairness, looking (from the outside) at the upgrade experiences of a number of #Mastodon nodes where I have accounts, the latest of which was an aborted 4.4 to 4.5 upgrade on one node (not this one) that lost a day's worth of data, I think that we can put this down to the general nature of the Mastodon upgrade process rather than the platform that it runs on.
Mind you, I have yet to hear of a large complex WWW-involved system with SQL-back ends where upgrades are *not* fraught with pitfalls. (-:
-
In fairness, looking (from the outside) at the upgrade experiences of a number of #Mastodon nodes where I have accounts, the latest of which was an aborted 4.4 to 4.5 upgrade on one node (not this one) that lost a day's worth of data, I think that we can put this down to the general nature of the Mastodon upgrade process rather than the platform that it runs on.
Mind you, I have yet to hear of a large complex WWW-involved system with SQL-back ends where upgrades are *not* fraught with pitfalls. (-:
@JdeBP @tj @wild1145 Personally, I've updated frequently and never encountered major problems - at least none that couldn't be resolved with a little analysis. The Mastodon update process is generally reliable. In my view, losing a whole day's worth of data implies either poor planning of the operation or a significant dose of bad luck.
Before any major update, I take a full snapshot of everything, ready to restore it if something goes sideways. The trouble often stems from the fact that installing and subsequently updating "complex" projects like Mastodon is done in a semi-automated way, perhaps using Docker. This creates an abstraction layer over your actual setup and, consequently, leaves you with little control over what's happening under the hood.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Chronic Illness Humor (@chronicillness.bsky.social)
https://bsky.app/profile/chronicillness.bsky.social/post/3m57elwhfck23
-
@matz TAKE THAT
-
A NEW YORK LA SPERANZA HA VINTO SULLA RABBIA
@news
Finito il clamore e ammortizzata la sorpresa, dovremmo lasciar spazio alla riflessione ed esaminare quel che è successo nella Grande Mela per trarne qualche insegnamento.
L'articolo A NEW YORK LA SPERANZA HA VINTO SULLA RABBIA proviene da GIANO NEWS.
-
Giustamente si criticano le #BigTech statunitensi. Ma anche in Europa.. #Spotify, la macchina degli umori - Jacobin Italia https://jacobinitalia.it/spotify-la-macchina-degli-umori/
-
> The recent introduction of generative AI means that we no longer have any control over how big tech companies are using our information
Yeah, automated web spidering and page scraping has totally never been done before, and search engines have definitely never been cataloging and indexing and running analytics etc... until The AI came along and blah blah blah.
This is not the problem. Anyone who thinks that they ever had control over the content they placed online needs to wake up. Us old folks here may remember submitting our sites to search index queues, wanting our data to be spread across the internet for others (inc the search engines) to see and use and inspire.
But sure, blame The Algorithms (nevermind, this buzzword is from the last decade, now everyone blames AI like it's a monolithic problem (similar to the "fuck cars" lunatic fringe who ignore the facts).
People's illiberal policies and the flawed expectations on the content "owner's" side ... Those are the problem. Stop treating things like a monolithic issue and maybe look at the flawed expectations before blaming whatever buzzword is popular.
-
@JdeBP @tj @wild1145 Personally, I've updated frequently and never encountered major problems - at least none that couldn't be resolved with a little analysis. The Mastodon update process is generally reliable. In my view, losing a whole day's worth of data implies either poor planning of the operation or a significant dose of bad luck.
Before any major update, I take a full snapshot of everything, ready to restore it if something goes sideways. The trouble often stems from the fact that installing and subsequently updating "complex" projects like Mastodon is done in a semi-automated way, perhaps using Docker. This creates an abstraction layer over your actual setup and, consequently, leaves you with little control over what's happening under the hood.
-
In fairness, looking (from the outside) at the upgrade experiences of a number of #Mastodon nodes where I have accounts, the latest of which was an aborted 4.4 to 4.5 upgrade on one node (not this one) that lost a day's worth of data, I think that we can put this down to the general nature of the Mastodon upgrade process rather than the platform that it runs on.
Mind you, I have yet to hear of a large complex WWW-involved system with SQL-back ends where upgrades are *not* fraught with pitfalls. (-:
-
@BONOPHOTO3 mai due uguali
