How to setup my local git repository?

[asdromundo]

I'm trying to use SveltiaCMS as local using the Edge browser , but following the documentation I think that it should be asking me for the root of the directory instead of asking me to write it in the config file.

This is my config file

backend:
  name: local

media_folder: "static/images/uploads"
public_folder: "/images/uploads"

collections:
  - name: "Blog" # Used in routes, e.g., /admin/collections/blog
    label: "Blog" # Used in the UI
    folder: "../src/Blog" # The path to the folder where the documents are stored
    create: true # Allow users to create new documents in this collection
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}" # Filename template, e.g., YYYY-MM-DD-title.md
    fields: # The fields for each document, usually in front matter
      - { label: "Title", name: "title", widget: "string" }
      - { label: "Publish Date", name: "date", widget: "datetime" }
      - { label: "Featured Image", name: "thumbnail", widget: "image" }
      - { label: "Descripción", name: "description", widget: "string" }
      - { label: "Body", name: "body", widget: "markdown" }

Without the backend lines it says that no backend is defined in the config. After adding this lines it shows:

In no case I'm seeing an option to select a root for the directory.

I'm using Windows 11, no WSL. Tried with Brave with flag options and Edge.

[kyoshino]

As described in the Decap CMS doc, the backend config has to be:

backend:
  name: github # or gitlab
  repo: owner-name/repo-name # path to your repo

Looks like name: local or name: proxy could be used in Netlify/Decap CMS as per decaporg/decap-cms#7217. I’ll later add compatibility for these legacy, undocumented backend names.

[asdromundo]

@kyoshino Thank you for your quick answer.
I wasn't following the Decap CMS that you provided as they have a separate method for a local git repository.

# when using the default proxy server port
local_backend: true

backend:
  name: git-gateway

This is not equivalent to the Sveltia CMS, as we don't have the git-gateway and DecapCMS doesn't require a repo. This difference is not mentioned in the README section of local repositories. So maybe it would be worthwhile to add the example.

Thank you again.

[kyoshino]

You’re right. We’ll improve README and eventually create our own docs.

But interesting — how did you come up with name: local?

[asdromundo]

Looking for previous answers, I found this recently closed issue:

And the comment on the second function reads as

 // Netlify/Decap CMS uses `proxy` as the backend name when running the local proxy server and 
 // leaves it in local storage. Sveltia CMS uses `local` instead. 
 const _backendName = 
   _user?.backendName?.replace('proxy', 'local') ?? 
   (isLocal ? 'local' : get(siteConfig)?.backend?.name); 

So I figured out SveltiaCMS (and actually confirmed) does accept local as a valid backend name, it just complies about not having a repo as the screenshot provided in the original question.

Furthermore, from your reply I found out that it does run given a repo name:.

I don't see the repo actually be used anywhere, but it does work as intended. (Beyond having 2 buttons with the same functionality)

[kyoshino]

I see. Sorry to confuse you. The repository name is used in some places even when the local backend is in use, like the Git Repository link under the Account menu, and more importantly, an IndexedDB database name. This is because developers may run different sites on the same localhost, so the CMS needs a way to distinguish between them. (I myself need it because I work on different client projects locally, which are mostly SvelteKit running on localhost:5173.)

[asdromundo]

@kyoshino Thank you for the explanation and the fine job with Sveltia.