FAQ

FAQ

1. What is the default admin URL and account?

• Admin URL: /geo_admin/
• Default admin username: admin
• Default admin password: password

After first login, change the admin password immediately. For source deployments, make sure Laravel APP_KEY has been generated with php artisan key:generate or by the Docker init service.

2. Is Docker required?

No.

You can:

• use Docker Compose for postgres + redis + init + app + queue + scheduler + reverb
• or run PHP and PostgreSQL locally

If the goal is to get started quickly and predictably, Docker is the safer option.

3. Is PostgreSQL required at runtime?

Yes.

The current public runtime database is PostgreSQL.
The repository does not include production databases or sample business data.

4. Why are image libraries, knowledge files, and article data not included?

Because those are runtime or business assets, such as:

• image-library contents
• raw knowledge-base files
• generated articles
• logs and backups

The public repository only includes source code and configuration templates.

5. How do I connect an AI model?

Go to:

AI Configurator -> AI Model Settings

Then fill in:

• API URL
• Model ID
• Bearer Token

The system supports OpenAI-style interfaces and handles provider base URLs as well as full endpoint URLs. It also adapts non-/v1 versioned providers such as Zhipu /api/paas/v4 and Volcengine Ark /api/v3.

For knowledge-base RAG, also configure an embedding model and set it as the default embedding model.

6. What is the content-generation pipeline?

The core flow is:

1. Configure models and prompts
2. Prepare knowledge, title, keyword, image, and author libraries
3. Create a task with generation limits and publishing cadence
4. Let the scheduler enqueue it
5. Let the worker execute generation
6. Route content through draft / review / publish
7. Deliver the result to the frontend

7. Is there a CLI or companion skill support?

Yes.

• CLI docs are available in the project documentation
• Companion skill repository: yaojingang/yao-geo-skills
• Public skills currently include:
  • geoflow-cli-ops
  • geoflow-template

8. When is GEOFlow a good fit?

It is a good fit for:

• independent GEO websites
• GEO sub-channels inside official sites
• internal GEO content operations
• knowledge-base-driven content production
• multi-section or multi-site content operations

9. Why does a knowledge base show chunks but zero vectors?

This usually means no usable embedding model has been configured yet.

GEOFlow can still split the knowledge document into chunks, but vector writing requires:

• an enabled model whose type is embedding
• a valid API key
• a provider endpoint that supports embeddings
• the model set as the default embedding model

After configuring it, re-save or re-upload the knowledge base so vectors can be written.

10. Why do old article images fail after migration?

Older records may store paths like /uploads/...; the Laravel rewrite serves uploaded public files through /storage/uploads/....

Current code normalizes these paths at render time, but the actual files must still exist under storage/app/public/uploads/... and php artisan storage:link must be valid.

11. What is the recommended first workflow?

Use the dashboard quick-start path:

1. configure API
2. configure materials, including authors
3. create a task

Start with draft or review mode before enabling full automatic publishing.

• GEO source sites
• internal GEO content backends
• multi-site or multi-channel content operations

It is not a good fit if the goal is mass-producing low-value pages.

9. Why is the knowledge base treated as a priority?

Because GEOFlow is only as trustworthy as the knowledge assets behind it.
If the knowledge layer is weak, automation only scales noise.

10. Which pages should I read first?

Recommended order:

1. Getting Started
2. What Is GEOFlow
3. GEOFlow Methodology
4. Principles and Content Boundaries
5. Use Cases