Davide Scaini
be772bd3df
Four related issues made uploading 271+ activities unreliable: 1. merge_all/write_combined_feed were inside the extraction try/except — any merge race returned 422 even though the file was on disk, causing the mobile app to permanently mark the upload as failed. Fixed by moving them to a separate best-effort try/except after the extraction block. Switch to merge_one (single-activity symlink) instead of merge_all (full rebuild) so each upload is O(1) FS ops, not O(N). 2. The dev watcher fired merge_all for every activity .json write AND the upload endpoint also ran merge_all — O(N²) symlink operations during bulk uploads. Watcher now skips activities/*.json changes (upload endpoint handles those directly). 3. Vite/Chokidar followed the public/data symlink and opened a handle per activity file; constant merge rebuilds exhausted file descriptors and crashed the Astro dev server. Fixed with watch.ignored on public/data. 4. _write_year_shards and write_combined_feed used f.unlink() without missing_ok=True — concurrent callers racing the same file threw FileNotFoundError which propagated as a false extraction failure.
79 lines
2.9 KiB
JavaScript
79 lines
2.9 KiB
JavaScript
import { defineConfig } from "astro/config";
|
|
import { loadEnv } from "vite";
|
|
import svelte from "@astrojs/svelte";
|
|
import tailwind from "@astrojs/tailwind";
|
|
|
|
const env = loadEnv(process.env.NODE_ENV ?? 'development', process.cwd(), '');
|
|
// PUBLIC_EDIT_URL: non-empty → bincio edit URL; empty → proxy to bincio serve.
|
|
// VITE_API_PORT lets `bincio dev` override the serve port without touching .env.
|
|
const apiPort = process.env.VITE_API_PORT || '4041';
|
|
const serveTarget = env.PUBLIC_EDIT_URL || `http://localhost:${apiPort}`;
|
|
|
|
// In production, nginx serves activity/index.html for all /activity/<id>/ URLs
|
|
// via try_files. In dev (Astro dev server), no nginx — this plugin replicates it.
|
|
const activityFallbackPlugin = {
|
|
name: 'activity-shell-fallback',
|
|
configureServer(server) {
|
|
server.middlewares.use((req, _res, next) => {
|
|
if (req.url && /^\/activity\/[^/]+\/?(\?|$)/.test(req.url)) {
|
|
req.url = '/activity/';
|
|
}
|
|
next();
|
|
});
|
|
},
|
|
};
|
|
|
|
export default defineConfig({
|
|
integrations: [svelte(), tailwind()],
|
|
devToolbar: { enabled: false },
|
|
output: "static",
|
|
// When hosting at a subdirectory (e.g. GitHub Pages project site), set:
|
|
// base: "/repo-name",
|
|
vite: {
|
|
plugins: [activityFallbackPlugin],
|
|
optimizeDeps: {
|
|
include: ['maplibre-gl'],
|
|
esbuildOptions: { target: 'es2022' },
|
|
},
|
|
build: { target: 'es2022' },
|
|
// Proxy /api/* to bincio serve/edit so cookies work same-origin in dev.
|
|
// In production nginx handles this — same pattern, no code change needed.
|
|
server: {
|
|
watch: {
|
|
// public/data is a symlink to the live data dir; Chokidar follows it and
|
|
// opens a handle per file, which causes EMFILE during bulk uploads as
|
|
// activity count grows. Data files don't need HMR — exclude them.
|
|
ignored: ['**/public/data/**'],
|
|
},
|
|
proxy: {
|
|
// Both /api/upload and /api/upload/strava-zip return SSE streams in response
|
|
// to POST requests. Vite's default proxy buffers the full body before forwarding,
|
|
// which breaks streaming and causes EPIPE on long uploads.
|
|
// selfHandleResponse + manual pipe sends chunks as they arrive.
|
|
'/api/upload': {
|
|
target: serveTarget,
|
|
changeOrigin: true,
|
|
selfHandleResponse: true,
|
|
configure: (proxy) => {
|
|
proxy.on('proxyRes', (proxyRes, req, res) => {
|
|
res.writeHead(proxyRes.statusCode ?? 200, proxyRes.headers);
|
|
proxyRes.pipe(res, { end: true });
|
|
});
|
|
proxy.on('error', (err, _req, res) => {
|
|
if (err.code === 'EPIPE' || err.code === 'ECONNRESET') return;
|
|
if (!res.headersSent) {
|
|
res.writeHead(502);
|
|
res.end('proxy error');
|
|
}
|
|
});
|
|
},
|
|
},
|
|
'/api': {
|
|
target: serveTarget,
|
|
changeOrigin: true,
|
|
},
|
|
},
|
|
},
|
|
},
|
|
});
|