Login

Recent searches

No recent searches

Search options

Only available when logged in.
social.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
social.lol is a lighthearted social hangout for the omg.lol community.

Administered by:

Server stats:

840
active users

social.lol: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#selfhosting

52 posts50 participants0 posts today
Public
ItzTrain

Ok So it took me a while and I still feel like I'm not fully sure of #seaweedfs . I got 3 master servers ( which I don't think I need). I have 1 filer and one s3 gateway and one volume server ( right now). I'm uploading to it right now and using rclone ( which is pretty dope) to mount them to my services. Right now it's just Linux ISO's.

#homelab#selfhosted#selfhosting
Public
aleidk

I'm thinking about stop #selfhosting services as it's to much trouble (and sometimes time consuming) just for myself, as nobody I know are interested in them.

So far I have found replacement for some, but I'm having trouble finding a #git forge. I would use #codeberg but I have high latency to Europe based data centers /:

I would appreciate some recommendations, the closer to Latin America the better. I'm also willing to support/help the instance if I can.

#askfedi
Public *
Iznogoud

Not me blocking *.telemetry.mozilla.org

Also, check out your pihole log with

sudo awk '/query\[A\]/ || /query\[AAAA\]/ {print $6}' /var/log/pihole/pihole.log | sort | uniq -c | sort -nr

Surprises aplenty. Or not.

#pihole #dnssec #selfhosting

Update: added AAAA records (ipv6) to above command to have a complete view

Public
InfoQ

Self-hosted LLMs are going to power the next generation of applications in critical industries like financial services, healthcare, and defense. But they come with their own unique challenges!

In this #InfoQ video, Meryem Arik shares:
✅ Best practices for self-hosting LLMs
✅ Practical tips for deployment & optimization
✅ Real-world case studies from the field

👀 Watch now: bit.ly/3XJqkST

📄 #transcript included

#LLMs#SelfHosting
Replied in thread
Public *
Debacle

@urbanprivacy

#UnplugTrump, daher Signal in der Amazon Cloud von Jeff B., einem DJT-#Broligarchen? Vom Regen in die Traufe!

Threema ist dbzgl. besser, zumal es Users nicht zwingt, ihre Telefonnummer rauszurücken.

Aber #digitaleSouveränität bietet der Silo nicht, da man sich den Server nicht aussuchen kann, z.B. in der #EU oder #selfHosting.

Zum Glück gibt es seit 1999 einen Internet-Chat-#Standard, der freie Föderation erlaubt wie Email oder das #Fediverse.

@xmpp

#Jabber#XMPP
Public *
Mauricio Teixeira 🇺🇸🇧🇷

What do you do folks with old/small SD cards?

I found out I've been accumulating a bunch of 2/4/8 GB cards, which are not really much useful these days. Trying to figure out if they're still useful, or if I should just trash them.

(Note: I do have a bunch of USB flash drives as well, so using adapters to make use of them as such doesn't help).

#homeLab#SelfHosted#RaspberryPi
Public
Abnormal Human Being

So, I am stuck trying to apply the current #Mastodon update. Note that there may be many good reasons why, chief among them, that I am self-taught and very much in the "trying stuff out half-blindly while learning"-stage. Thankfully, nothing broke irreversably just yet.

If anyone here feels like helping a noob out, or just loves a conundrum, details can be found here:

lemmy.abnormalbeings.space/pos

lemmy.abnormalbeings.space[SOLVED][Mastodon] Getting stuck on trying to apply the latest update - AbnormalLemmingsSOLUTION HERE (by @just_another_person@lemmy.world): https://lemmy.abnormalbeings.space/post/804932?scrollToComments=true [https://lemmy.abnormalbeings.space/post/804932?scrollToComments=true] >You have a dependency discrepancy with your local node modules and your global. You should be running this in a node virtual environment so all of the local projects dependencies don’t conflict with global. >https://stackoverflow.com/questions/3653495/is-there-a-virtual-environment-for-node-js [https://stackoverflow.com/questions/3653495/is-there-a-virtual-environment-for-node-js] >https://www.develves.net/blogs/asd/2016-04-28-using-virtual-environments-nodejs/ [https://www.develves.net/blogs/asd/2016-04-28-using-virtual-environments-nodejs/] cross-posted from: https://lemmy.abnormalbeings.space/post/804932 [https://lemmy.abnormalbeings.space/post/804932] I have searched around for answers to this, but so far, the solutions I found and tried have not been working for me. Thankfully, the update isn’t that critical, so time is not of the essence as of now. But I fear, the problem will only persist. So, bit of a headscratcher: I am following the guide to upgrade (no Docker) from here. [https://github.com/mastodon/mastodon/releases/tag/v4.3.7] Simple enough, right? Sadly, I keep getting: ~/live$ RAILS_ENV=production bundle exec rails assets:precompile I, [2025-04-03T20:30:30.072648 #981372] INFO -- : [dotenv] Loaded .env.production Mastodon and Webpacker requires Yarn ">=4 <5" and you are using 1.22.22 Exiting! So, the proposed solution? Using corepack as intended. That, at first, upon entering “corpack prepare” and “corepack enable” in succession, seemed to run silently and without errors/warnings. But it changed nothing at all for the error message. Prompting me to search around, haphazardly try to apply fixes, trying to remove and reinstall yarn, “the usual”. My last attempt was to globally remove yarn and corepack with npm and then re-install both. Since then, a new, exciting error is happening: ~/live$ corepack enable Internal Error: EACCES: permission denied, symlink '../lib/node_modules/corepack/dist/pnpm.js' -'/usr/bin/pnpm' at async Object.symlink (node:internal/fs/promises:1005:10) at async EnableCommand.generatePosixLink (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23156:5) at async Promise.all (index 0) at async EnableCommand.execute (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23143:5) at async EnableCommand.validateAndExecute (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:20258:22) at async _Cli.run (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21195:18) at async Object.runMain (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23642:19) Oh, and when trying to install yarn and corepack, now, I get: ~/live$ npm install yarn npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch npm error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log ~/live$ npm install corepack npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch npm error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log ::: spoiler the logs in question: $ cat /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log 0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@11.2.0 2 info using node@v22.14.0 3 silly config load:file:/usr/lib/node_modules/npm/npmrc 4 silly config load:file:/home/mastodon/live/.npmrc 5 silly config load:file:/home/mastodon/.npmrc 6 silly config load:file:/usr/etc/npmrc 7 verbose title npm install yarn 8 verbose argv "install" "yarn" 9 verbose logfile logs-max:10 dir:/home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z- 10 verbose logfile /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log 11 silly logfile start cleaning logs, removing 1 files 12 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368 13 silly logfile done cleaning log files 14 silly idealTree buildDeps 15 verbose stack Error: Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 15 verbose stack at unsupportedURLType (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:369:15) 15 verbose stack at fromURL (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:428:13) 15 verbose stack at Function.resolve (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:110:12) 15 verbose stack at #nodeFromEdge (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1039:22) 15 verbose stack at #buildDepStep (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:904:35) 15 verbose stack at async Arborist.buildIdealTree (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:181:7) 15 verbose stack at async Promise.all (index 1) 15 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5) 15 verbose stack at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:149:5) 15 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:208:9) 16 error code EUNSUPPORTEDPROTOCOL 17 error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 18 silly unfinished npm timer reify 1743710053061 19 silly unfinished npm timer reify:loadTrees 1743710053064 20 silly unfinished npm timer idealTree:buildDeps 1743710057205 21 silly unfinished npm timer idealTree:#root 1743710057206 22 verbose cwd /home/mastodon/live 23 verbose os Linux 6.1.0-31-amd64 24 verbose node v22.14.0 25 verbose npm v11.2.0 26 verbose exit 1 27 verbose code 1 28 error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log ~/live$ cat /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log 0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@11.2.0 2 info using node@v22.14.0 3 silly config load:file:/usr/lib/node_modules/npm/npmrc 4 silly config load:file:/home/mastodon/live/.npmrc 5 silly config load:file:/home/mastodon/.npmrc 6 silly config load:file:/usr/etc/npmrc 7 verbose title npm install corepack 8 verbose argv "install" "corepack" 9 verbose logfile logs-max:10 dir:/home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z- 10 verbose logfile /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log 11 silly logfile start cleaning logs, removing 1 files 12 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368 13 silly logfile done cleaning log files 14 silly idealTree buildDeps 15 verbose stack Error: Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 15 verbose stack at unsupportedURLType (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:369:15) 15 verbose stack at fromURL (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:428:13) 15 verbose stack at Function.resolve (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:110:12) 15 verbose stack at #nodeFromEdge (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1039:22) 15 verbose stack at #buildDepStep (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:904:35) 15 verbose stack at async Arborist.buildIdealTree (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:181:7) 15 verbose stack at async Promise.all (index 1) 15 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5) 15 verbose stack at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:149:5) 15 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:208:9) 16 error code EUNSUPPORTEDPROTOCOL 17 error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 18 silly unfinished npm timer reify 1743710065916 19 silly unfinished npm timer reify:loadTrees 1743710065919 20 silly unfinished npm timer idealTree:buildDeps 1743710070343 21 silly unfinished npm timer idealTree:#root 1743710070344 22 verbose cwd /home/mastodon/live 23 verbose os Linux 6.1.0-31-amd64 24 verbose node v22.14.0 25 verbose npm v11.2.0 26 verbose exit 1 27 verbose code 1 28 error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log ::: Thankfully, mastodon is still working, no database issues, nothing indicating I fucked up beyond repair yet. I am a bit at a loss, unfortunately, but eager to use my fuckup as a learning experience - am glad to hear any and all more experienced folk chiming in!___
#sysadmin#techsupport#update
Public
Daniel Colquitt

I was initially rather hesitant at the prospect of #selfhosting my email, but I’m massively impressed by @stalwartlabs, which has made the whole process straightforward.

I’ve just enabled encryption at rest, which uses my PGP/SMIME public key to encrypt all my messages upon receipt. With my private key installed on my clients, the whole thing is seamless.

If you’re looking for a modern and powerful JMAP/IMAP/SMTP server that’s easy to deploy, I can’t recommend @stalwartlabs enough.

Public
Elena Rossini on GoToSocial ⁂

🏕️ my adventures in #selfhosting - day 107 (sleepwalking edition) 😴​

Hello Fedi friends!

I'm lucky I didn't have to do any coding today... my little one woke me up at 4:50am, so even if it's only 3:30pm I've been wide awake for 11 hours now. Running commands in terminal would have been... risky I think 😅​

It feels really strange to be past a HUGE self-hosting hurdle. Now my self-hosted Ghost blog is fine... up and running wonderfully, with perfectly working TXT and DMARC records (knock on wood).

What will my next big challenge be? I'm thinking self-hosting PeerTube... but I will enjoy this peace and sense of accomplishment for a little while longer before taking that on.

Thanks for all your help and encouragement throughout my self-hosting adventures ❤️​

#MySoCalledSudoLife
Public
shom ✊🏽🐧📷🤿🏔️🪚

Last year I started a webring like it was 1999 with the System Crafters community. And for its first anniversary I wrote a blog post about How I accidentally got better at self-hosting and FOSS contributing.

Sometimes you don’t have to wait for someone else, you can be a catalyst. Happy Birthday Craftering!

Thanks to @daviwil for fostering a great community and to @kern for building Ringfairy and being so encouraging.

shom.dev · How I accidentally got better at self-hosting and FOSS contributingA year ago (April 3rd, 2024) I started a webring with the System Crafters Community, building the web I wanted to see instead of lamenting its absence. Craftering has motivated others to write and share more, which in itself is very rewarding, but what I didn’t anticipate is how it improved my self-hosting and FOSS contributions.
#SystemCrafters#Webring#SmallWeb
ExploreLive feeds
About