MatthiesenXYZ / astro-ghostcms

Easily migrate your Ghost Site to Astro, an Astro Integration that turns your Ghost server into a Headless CMS
https://astro-ghostcms.xyz/
MIT License
18 stars 3 forks source link

feat: ✨ Index.html not being created during npm run build step #151

Closed create-issue-branch[bot] closed 1 month ago

create-issue-branch[bot] commented 1 month ago
Original issue description First, excellent project here. When running npm run build and then npm run preview, there is no resource created for / resulting in 404 page showing in browsers. Any known path always results in the 404 page. - OS: Everything is a VirtualBox Guest, Windows 11 for running the project , Ubuntu 20 for Ghost instance, Debian for MariaDB. - Browsers Chrome, Firefox, Falkon(with javascript disabled) - Version **Additional context** Also, I used the manual method to install this fine tool, although, I installed it over an existing Astro project with basic html content. Here is my package.json { "name": "static-app", "type": "module", "version": "0.0.1", "scripts": { "dev": "astro dev", "start": "astro dev", "build": "astro check && astro build", "preview": "astro preview", "deploy": "shx cp -r dist/* ../client-app/public", "astro": "astro" }, "dependencies": { "@astrojs/check": "^0.7.0", "@matthiesenxyz/astro-ghostcms": "^3.3.5", "astro": "^4.9.1", "typescript": "^5.4.5" }, "devDependencies": { "shx": "^0.3.4" } } astro.config.mjs import { defineConfig } from 'astro/config'; import astroGhostCMS from '@matthiesenxyz/astro-ghostcms'; // https://astro.build/config export default defineConfig({ server: { host: "127.0.0.1", port: 8088 }, site: 'https://example.com', integrations: [ astroGhostCMS({ // `ghostURL` Recommended to set here, Can also set in .env as CONTENT_API_URL ghostURL: "http://ghostcms.meikos.internal", }) ] });

closes #140

changeset-bot[bot] commented 1 month ago

⚠️ No Changeset found

Latest commit: a5c67c5ac0d3bf8f86755169af7ae0e352922d4a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR