-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitError: fatal: not a git repository (or any of the parent directories): .git #166
Comments
Thanks for the report @Adammatthiesen, could you try upgrading to the Lunaria v1 prerelease?
The specific part of the code in the stack trace doesn't exist anymore in the prerelease and that might solve it, from your PR I can also see you're using root locale in Starlight which wasn't supported in v0.1 but is in v1, so I guess there's no escaping the upgrade in this case. There's no docs for it yet, but you can see how we migrated in Docs here: That would mean bringing all the dashboard code to the repo for the time being, as it is still WIP for the v1 version, but what we did in the Astro Docs repo is all you need. In the v1 branch there's also an example of how to set up for root locale in Starlight: |
Well, i've managed to get things migrated over to your v1 package... getting the following error when running the build script
Also during local testing, it only seems to be able to read the These updates are available on the branch (PR) |
was able to use Github actions and pages to create a Lunaria deployment pipeline... but still having the weirdness of it not detecting the primary content, see https://i18n.docs.studiocms.dev/ (Commented out all the extra langs, so it gives a simpler test now) |
nvm i forgot about the tracking system 😅 |
What package manager are you using?
pnpm
What operating system are you using?
Linux (nixpacks deployment container)
Describe the bug
I am attempting to deploy to my Coolify server which uses nixpacks and handles the cloning process itself to account for being able to do PR deployments and am getting the following error:
This is for trying to build Lunaria for our docs from our deployment pipeline on StudioCMS while trying to build and output only the Lunaria files.
The following PR to our docs contains the config files currently being used withstudiocms/studiocms#386
I have also used the PR link for the minimal reproduction since this is a deployment bug, and works locally without an issue, so i would assume/hope there would be a way to work around this through a update?
Link to minimal reproducible example
withstudiocms/studiocms#386
Participation
The text was updated successfully, but these errors were encountered: