• 4 Posts
  • 5 Comments
Joined 1Y ago
cake
Cake day: Jun 17, 2023

help-circle
rss
How can I reduce the amount of storage used by my Lemmy instance?
I've had a Lemmy instance running on a VPS with 100 GB of storage for a few months and it has filled up. I've been searching for ways to reduce the amount of storage used but so far I am coming up empty. Can anyone point me in the right direction?
fedilink

Thanks for talking through it with me, everyone. I got it working with a Docker compose install of Lemmy and a non-Docker Mastodon install. Reverse proxy was configured manually in nginx. Mastodon.fdr8.us and Lemmy.fdr8.us are now live! I have some fine tuning to do still and a lot of setup, but I’m happy that they are working. Cheers!


I have reverse proxy configured for Mastodo using Nginx. It’s the Lemmy Easy Deploy script trying to bind all traffic on port 443 where I run into problems.


Interesting point. I hadn’t given that any consideration but if my Mastodon/Lemmy plans don’t work out I might give it a shot.


Anyone hosting Lemmy and Mastodon on the same server?
I have Mastodon running on a VPS running Debian 11. Now I would like to add a Lemmy instance on the same server. I tried using the from scratch method from Lemmy documentation, but ran into errors that likely stemmed from minor version incompatibilities of the dependencies. I tried using the Lemmy easy deploy script but it wants to bind all traffic on port 443 for Lemmy which would break my Mastodon install. Has anyone managed to get Lemmy and Mastodon running on the same box, and if so, can you share any details of your setup?
fedilink


Trouble compiling Lemmy server
I'm attempting to get a Lemmy server running on Debian 11 using this documentation: https://join-lemmy.org/docs/administration/from_scratch.html The following command fails as a result of some minor version incompatibilities: cargo install lemmy_server --target-dir /usr/bin/ --locked --features embed-pictrs Removing --locked seems to work, but it fails compiling later in the process with the following output: Compiling diesel-async v0.1.1 error[E0405]: cannot find trait `RowGatWorkaround` in module `diesel::row` --> /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/diesel-async-0.1.1/src/pg/row.rs:16:23 | 16 | impl<'a> diesel::row::RowGatWorkaround<'a, diesel::pg::Pg> for PgRow { | ^^^^^^^^^^^^^^^^ not found in `diesel::row` error[E0405]: cannot find trait `RowGatWorkaround` in module `diesel::row` --> /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/diesel-async-0.1.1/src/pg/row.rs:30:39 | 30 | ...diesel::row::RowGatWorkaround<'b, diesel::pg::Pg>>::Field> | ^^^^^^^^^^^^^^^^ not found in `diesel::row` For more information about this error, try `rustc --explain E0405`. error: could not compile `diesel-async` (lib) due to 2 previous errors error: failed to compile `lemmy_server v0.17.4`, intermediate artifacts can be found at `/usr/bin/` Does anyone know how I can remedy this?
fedilink

Thanks for the suggestion! Unfortunately the closest thing is trinity.tech and it’s been in use since 2007. If it were available they’d probably charge me a premium rate for it too. Single dictionary words are generally more expensive. I’m kind of being a choosing beggar I guess but I really want a catchy domain name cheap.


Ready to take the plunge and spin up a Lemmy server but I’m already stuck trying to come up with a domain name.
As the title says, I'm ready to fire up a Lemmy server of my own. I have a suitable VPS running Debian 11. I think I can probably make short work of it once I get past this one difficult point. What should I call my Lemmy server? With catchy names out there like "Lemmy.World" and "sh.itjust.works", I really want to come up with something good. Unfortunately after thinking it over for three days now and checking tons of names for availability, I don't feel any closer to deciding on a name. It doesn't help that almost all the dictionary words are sold at premium rates these days, even with a fairly obscure tld. Any name suggestions or techniques for choosing a good name would be appreciated. It probably sounds silly but this part just isn't my strong suit and I'm frustrated that it's holding up the project.
fedilink