Gonna assume this was a test post. It worked!
Firstly, I wanted to apologize for the silence over the past couple weeks. Work, life took over administering this instance.
Onto the good stuff.
As some of you may have noticed we skipped 0.18.0 because of some unforeseen issues but we're now on 0.18.1. In my extremely minimal testing, the upgrade seems to have gone through largely smoothly! Please do let me know if you see any weirdness. (Some old themes might be borked, please update your own interface accordingly).
I am aware that Jerboa was completely broken, hopefully it works now (I can't test it since I don't have access to Android).
Time for some stats:
$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 392M 1.7M 390M 1% /run
/dev/vda1 94G 21G 69G 23% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 392M 4.0K 392M 1% /run/user/1002
$ free -m
total used free shared buff/cache available
Mem: 3911 475 142 140 3294 3020
Swap: 2399 88 2311
Another important thing I did was upgrade the instance to a mid-tier vultr plan (we did run out of disk space on the old one). Here's the new plan:
AMD High Performance 2 vCPU, 4096 MB RAM, 100 GB NVMe, 5.00 TB Transfer
And last month's vultr stats:
This brings our yearly costs to (there's occasional bumps because of some vultr snapshot nonsense) regardless:
domain: $12/year
vultr: $24 (instance) + $4.8 (backups) = $28.8/month = $345.60 / year
email: still free tier on zoho, woo!
total: $357 / year
Let me know questions/concerns, bugs you've noticed after the upgrade.
Cheers!
Oh wow, this seems like a fantastic addition. One of these days I really gotta switch from my decade old tmux workflow to zellij!
So there's two options (assuming /r/bevy even wants to consider migrating here):
- We setup a dedicated Bevy community
/r/bevycould potentially use the existingRust: Game Developmentcommunity we have here
I don't really have preference either way. I do think that project-specific communities could certainly become a thing if people prefer to keep discussions laser focused.
And yeah, unfortunately I can't really make it free-for-all community creation simply because of potential DDOS/spam attacks and things rampantly becoming out of hand (part of the reason the instance is also application based).
I think TWiR can certainly belong in Rust: News along with any other relevant potentially recurring content (I'm thinking rustfmt, useful pkg update(s), news articles etc perhaps).
I've noticed its kinda challenging finding communities for folks and it's also kinda hard to make an actual announcement of sorts. I do, however, try to "pin" posts which I believe to be particularly important for the members to know. Honestly though, I too am figuring this out along with y'all :)
Their pricing and reputation is certainly good. However, it seems like they don't have simple full server snapshot support. I think that's mandatory at this point in case of potentially irrecoverable failures.
Sigh, I tried it one more time. Same problem. Downtime this time was probably < 5 mins though so hopefully not noticeable. I am wondering whether the database is in some bad shape (no idea why/how). I guess we wait and retry with 0.18.1.
Well, the lemmy container kept running into:
lemmy | 2023-06-24T23:28:52.716586Z INFO lemmy_server::code_migrations: Running apub_columns_2021_02_02
lemmy | 2023-06-24T23:28:52.760510Z INFO lemmy_server::code_migrations: Running instance_actor_2021_09_29
lemmy | 2023-06-24T23:28:52.763723Z INFO lemmy_server::code_migrations: Running regenerate_public_keys_2022_07_05
lemmy | 2023-06-24T23:28:52.801409Z INFO lemmy_server::code_migrations: Running initialize_local_site_2022_10_10
lemmy | 2023-06-24T23:28:52.803303Z INFO lemmy_server::code_migrations: No Local Site found, creating it.
lemmy | thread 'main' panicked at 'couldnt create local user: DatabaseError(UniqueViolation, "duplicate key value violates unique constraint \"local_user_person_id_key\"")', crates/db_schema/src/impls/local_user.rs:157:8
despite the fact that:
lemmy=# select id, site_id from local_site;
id | site_id
----+---------
1 | 1
(1 row)
So you can see that it was unconditionally trying to create a local_site and running into a DB constraint error. I further narrowed it down to this piece of code:
///
/// If a site already exists, the DB migration should generate a local_site row.
/// This will only be run for brand new sites.
async fn initialize_local_site_2022_10_10(
pool: &DbPool,
settings: &Settings,
) -> Result<(), LemmyError> {
info!("Running initialize_local_site_2022_10_10");
// Check to see if local_site exists
if LocalSite::read(pool).await.is_ok() {
return Ok(());
}
info!("No Local Site found, creating it.");
At this point I gave up because I couldn't really tell why LocalSite::read(pool).await.is_ok() was, well...not ok.
Will you update to Lemmy 0.18.0 (announced today)? The new HTTP API is allegedly more lightweight.
Of course I will! I was just waiting for a few more instances to bump theirs before I update this one.
By the way, I updated my dark theme published here for lemmy-ui 0.18.0 :)
Most excellent, I have been using your CSS with Stylebot :) You could also submit a PR to lemmy-ui repo btw with your custom theme so it gets even easier for people to try.
I think it’s likely to spike again when the api goes dark
That's a fair point. I think I might bump up the specs of this instance over the weekend (will make an announcement prior).
I haven’t been back there, is any consensus forming regarding whether people will use /r/rust, [email protected], or [email protected] going forward?
I am still of the opinion that both can (and probably should) co-exist. This particular instance will always be Rust focused, federated and have rust dedicated micro-communities. Whether it continues to grow only time will tell I suppose.
I can somewhat relate. I mostly do something like this (instead of the exact dependency version):
chrono = {version = "0", features = ["serde"]}
clap = {version = "4", features = ["derive"]}
anyhow = "1"
I do, however, typically write application code instead of library, so it's probably less critical for me. Occasionally do run into dependency hell here and there, but nothing too bad so far!
Right, that's certainly possible. Is it enough for us to start thinking about de-federating, maybe? Arguably this has been true since forever on any public forum. I think what's needed is better mod tools on Lemmy in general.
Personally, I think it's best for us to be patient while things settle before we consider any action. FWIW, we don't see much incoming traffic here anyway since the subreddits started coming back online after the 48 hr blackout.
If things start getting out of hand and this instance starts getting bombarded with just bots/troll, we will likely have to consider de-federation (or some other alternative).
Hey all,
Just thought I'd share an update. I have added a few new communities and renamed the existing communities to have slightly more consistent naming throughout this instance. Icons are primarily from Wikimedia Commons (replacements welcome as long as there are no copyright issues).
Added:
- Rust: Web Development
- Rust: Game Development
- Rust: Embedded Systems
Renamed:
- Memes to Rust: Memes
- News to Rust: News
- Support to Rust: Support
- Meta to Rust: Meta
PS: The identifiers for the renamed communities remain the same. Open to any suggestions/thoughts on this change or otherwise.
Cheers!
Hey everyone, thought I'd post some stats since we're one week old now!
From Vultr (instance is hosted through them):
Total applications: 116
Denied applications: 4 (one person asked to change username, 3 others gave one word answer to the application question)
Accepted applications: 112
docker stats (snapshot):
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
7f365c848236 caddy 0.19% 43.22MiB / 969.4MiB 4.46% 7.23GB / 7.65GB 631MB / 146MB 8
d9421a5d930a lemmy-ui 0.00% 49.62MiB / 969.4MiB 5.12% 1.51GB / 3.32GB 869MB / 1.26GB 11
e8850c310380 lemmy 0.08% 52.53MiB / 969.4MiB 5.42% 5.67GB / 5.86GB 942MB / 582MB 8
7ebb13fde277 postgres 0.02% 304.2MiB / 969.4MiB 31.38% 908MB / 2.97GB 3.82GB / 14.4GB 12
9b471baacf84 pictrs 0.05% 10.32MiB / 969.4MiB 1.06% 53.5MB / 1.18GB 653MB / 360MB 14
df -h:
Filesystem Size Used Avail Use% Mounted on
tmpfs 97M 1.7M 96M 2% /run
/dev/vda1 24G 12G 11G 53% /
tmpfs 485M 0 485M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 97M 4.0K 97M 1% /run/user/1002
view more: next ›
Done. Update post coming shortly.