8a18e657f0
Community was never a separate community.quasarke.net host -- it lives
inside the Drop server itself at {server}/community, same as the server-side
fold-in two commits up. The desktop client's own community.rs, models.rs,
and the two community.vue pages still assumed the old sidecar design
(Settings.communityUrl/communityEndpoint defaulting to
https://community.quasarke.net), so this corrects them to match:
- community.rs now posts to {server}/api/v1/ingest/{session-start,
session-stop,achievements} (the fixed contract, matching the wrapper) via
the same generate_url()/make_authenticated_post_json() helpers
cloud_saves_commands.rs already uses, instead of an unauthenticated
bespoke HTTP client pointed at a hardcoded second host. {server} is
DB.base_url -- whatever Drop server the user actually signed into.
- database/src/models.rs: dropped the now-meaningless community_endpoint/
community_url Settings fields; kept enable_community_telemetry as the
only toggle.
- community.vue (the tab) and settings/community.vue: resolve the page URL
via the existing gen_drop_url Tauri command (same one the admin-panel
link already uses) instead of a stored/hardcoded URL.
- error.vue: the generic pre-auth error page can render before any server
is configured, so it can't resolve a per-server community link the way
community.vue does -- pointed its "Support" link at our docs instead of
the retired community.quasarke.net.
Also fixes a real release-blocking bug in process_manager.rs found while
verifying this compiles: the drop://game-launch telemetry emit held
install_dir (a reference borrowed out of db_lock via game_status) live past
the db_lock.applications.transient_statuses.insert() mutable borrow a few
lines above it -- an E0502 that fails every build, release or debug.
Fixed by cloning install_dir to an owned String before that mutable borrow
point and using the clone in the emit instead.
Verified: cargo check -p drop-app passes; full `cargo tauri build` release
build succeeds and produces a working NSIS installer (7z archive-test:
"Everything is Ok").
98 lines
3.2 KiB
Vue
98 lines
3.2 KiB
Vue
<template>
|
|
<NuxtLayout name="default">
|
|
<div
|
|
class="grid min-h-full grid-cols-1 grid-rows-[1fr,auto,1fr] lg:grid-cols-[max(50%,36rem),1fr]"
|
|
>
|
|
<header
|
|
class="mx-auto w-full max-w-7xl px-6 pt-6 sm:pt-10 lg:col-span-2 lg:col-start-1 lg:row-start-1 lg:px-8"
|
|
>
|
|
<Logo class="h-10 w-auto sm:h-12" />
|
|
|
|
</header>
|
|
<main
|
|
class="mx-auto w-full max-w-7xl px-6 py-24 sm:py-32 lg:col-span-2 lg:col-start-1 lg:row-start-2 lg:px-8"
|
|
>
|
|
<div class="max-w-lg">
|
|
<p class="text-base font-semibold leading-8 text-blue-600">
|
|
{{ error?.statusCode }}
|
|
</p>
|
|
<h1
|
|
class="mt-4 text-3xl font-bold font-display tracking-tight text-zinc-100 sm:text-5xl"
|
|
>
|
|
Oh no!
|
|
</h1>
|
|
<p
|
|
v-if="message"
|
|
class="mt-3 font-bold text-base leading-7 text-red-500"
|
|
>
|
|
{{ message }}
|
|
</p>
|
|
<p class="mt-6 text-base leading-7 text-zinc-400">
|
|
An error occurred while responding to your request. If you believe
|
|
this to be a bug, please report it. Try signing in and see if it
|
|
resolves the issue.
|
|
</p>
|
|
<div class="mt-10">
|
|
<!-- full app reload to fix errors -->
|
|
<a
|
|
href="/store"
|
|
class="text-sm font-semibold leading-7 text-blue-600"
|
|
><span aria-hidden="true">←</span> Back to store</a
|
|
>
|
|
</div>
|
|
</div>
|
|
</main>
|
|
<footer class="self-end lg:col-span-2 lg:col-start-1 lg:row-start-3">
|
|
<div class="border-t border-zinc-700 bg-zinc-900 py-10">
|
|
<nav
|
|
class="mx-auto flex w-full max-w-7xl items-center gap-x-4 px-6 text-sm leading-7 text-zinc-400 lg:px-8"
|
|
>
|
|
<NuxtLink href="/docs">Documentation</NuxtLink>
|
|
<svg
|
|
viewBox="0 0 2 2"
|
|
aria-hidden="true"
|
|
class="h-0.5 w-0.5 fill-zinc-600"
|
|
>
|
|
<circle cx="1" cy="1" r="1" />
|
|
</svg>
|
|
<!--
|
|
This is a generic pre-auth error page (can render before a
|
|
server is even configured), so it can't resolve a per-server
|
|
community URL the way community.vue does via gen_drop_url --
|
|
link to our fork's docs instead, which is a stable target
|
|
regardless of which Drop server the user is signed into.
|
|
-->
|
|
<a href="https://drop-docs.quasarke.net" target="_blank"
|
|
>Documentation & Support</a
|
|
>
|
|
</nav>
|
|
</div>
|
|
</footer>
|
|
<div
|
|
class="hidden lg:relative lg:col-start-2 lg:row-start-1 lg:row-end-4 lg:block"
|
|
>
|
|
<img
|
|
src="@/assets/wallpaper.jpg"
|
|
alt=""
|
|
class="absolute inset-0 h-full w-full object-cover"
|
|
/>
|
|
</div>
|
|
</div>
|
|
</NuxtLayout>
|
|
</template>
|
|
|
|
<script setup lang="ts">
|
|
import type { NuxtError } from "#app";
|
|
|
|
const props = defineProps({
|
|
error: Object as () => NuxtError,
|
|
});
|
|
|
|
const statusCode = props.error?.statusCode;
|
|
const message =
|
|
props.error?.statusMessage ||
|
|
props.error?.message ||
|
|
"An unknown error occurred.";
|
|
|
|
console.error(props.error);
|
|
</script>
|