Skip to content

Update GitHub Actions workflow for deployment - #1

Open
DSK369 wants to merge 9 commits into
astro-engine-v2-updatesfrom
DSK369-patch-1.5
Open

Update GitHub Actions workflow for deployment#1
DSK369 wants to merge 9 commits into
astro-engine-v2-updatesfrom
DSK369-patch-1.5

Conversation

@DSK369

@DSK369 DSK369 commented Aug 12, 2026

Copy link
Copy Markdown
Owner

No description provided.

DSK369 added 2 commits August 15, 2026 18:54
Introduces i18n support (LanguageProvider, i18n.js, language.js) with an
English/Hindi toggle in the app header, wires translated strings through
the main app sections and tables, and adds label-fit sizing (labelFit.js)
plus geometry tweaks for North/South Indian charts to keep translated
labels legible.
Moves the astro-engine FastAPI service (core/, services/app.py,
ephemeris data) into this repo instead of a separate one, so the
frontend and the backend it depends on live and deploy together.
Adds render.yaml (rootDir: backend) so Render's Blueprint deploy picks
it up as a standalone Python web service.
DSK369 added 3 commits August 15, 2026 19:36
.env.production sets VITE_API_BASE_URL so the GitHub Pages build calls
the live astro-engine-api service instead of the localhost-only
fallback. Backend CORS now allows the Pages origin plus any localhost
port for dev, instead of a wildcard.
npm ci was failing in CI (lock file listed @emnapi/wasi-threads@1.2.2
and was missing @emnapi/core, @emnapi/runtime — transitive deps that
drifted out of sync with package.json), which meant every GitHub Pages
deploy since this drifted has been failing at the install step.
npm ci was failing on the Linux runner with "Missing: @emnapi/core,
@emnapi/runtime from lock file" even against a freshly regenerated
lock file. Those packages are transitive deps of the wasm32-wasi
optional binary variant of rolldown/oxlint; npm's lockfile generation
on Windows doesn't reliably record a wasm32-only package's own
dependencies since that variant isn't installed locally, so a
Windows-generated lock file can't satisfy npm ci's strict validation
on Linux CI regardless of how many times it's regenerated. npm install
resolves what's actually needed instead of requiring an exact match.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant