20 Commits

Author SHA1 Message Date
98dcd7becb README updates
Some checks failed
Build and Push Image / Build and push image (push) Has been cancelled
2025-07-23 13:46:49 +10:00
f7506b4f20 README updates
Some checks failed
Build and Push Image / Build and push image (push) Has been cancelled
2025-07-23 13:45:55 +10:00
2b8cada173 remove config
Some checks failed
Build and Push Image / Build and push image (push) Has been cancelled
2025-07-23 13:36:30 +10:00
ea91c3e495 Merge pull request 'config_builder' (#1) from config_builder into master
All checks were successful
Build and Push Image / Build and push image (push) Successful in 22m49s
Reviewed-on: #1
2025-07-23 13:05:12 +10:00
df7d084450 merge conclicts fix 2025-07-23 13:03:32 +10:00
d313132c97 fix dockerfile 2025-07-23 13:00:34 +10:00
1ac41690c0 first iteration of the service 2025-07-23 12:53:08 +10:00
91f070c985 initial 2025-07-23 12:52:19 +10:00
d442093f39 remopve config 2025-07-23 12:44:59 +10:00
8d5c358d6e set up for public 2025-07-23 12:42:18 +10:00
fc0650b57c update to create kube config
All checks were successful
Build and Push Image / Build and push image (push) Successful in 23m17s
2025-07-22 22:36:39 +10:00
53616299af update to create kube config 2025-07-22 22:36:39 +10:00
31b53b5b49 human readme edit
Some checks failed
Build and Push Image / Build and push image (push) Failing after 36s
2025-07-22 22:11:54 +10:00
e7c2802c10 human readme edit 2025-07-22 22:11:54 +10:00
53241b7d1d <think>
Okay, the user wants me to generate a commit message based on the diffs provided. Let me look at the changes in the README.md file.

The diff shows that a new README.md file was added. The content is a detailed guide explaining the project, its components, setup instructions, and notes. The commit message should reflect that the README was created to explain the project's purpose and structure.

The user's initial request was to edit the README.md, but in the latest interaction, they added the gitea_mcp_set.sh file and asked for the README.md. The assistant provided a new README.md, so the commit is about creating that file.

The type should be "docs" because it's adding documentation. The description should mention that the README was created to explain the project's purpose, components, and setup. Keeping it concise and under 72 characters.

So the commit message would be: "docs: create README.md to explain project purpose, components, and setup"
</think>

docs: create README.md to explain project purpose, components, and setup

Co-authored-by: aider (ollama_chat/qwen3:4b) <aider@aider.chat>
2025-07-22 22:09:50 +10:00
8e744d96fa <think>
Okay, the user wants me to generate a commit message based on the diffs provided. Let me look at the changes in the README.md file.

The diff shows that a new README.md file was added. The content is a detailed guide explaining the project, its components, setup instructions, and notes. The commit message should reflect that the README was created to explain the project's purpose and structure.

The user's initial request was to edit the README.md, but in the latest interaction, they added the gitea_mcp_set.sh file and asked for the README.md. The assistant provided a new README.md, so the commit is about creating that file.

The type should be "docs" because it's adding documentation. The description should mention that the README was created to explain the project's purpose, components, and setup. Keeping it concise and under 72 characters.

So the commit message would be: "docs: create README.md to explain project purpose, components, and setup"
</think>

docs: create README.md to explain project purpose, components, and setup

Co-authored-by: aider (ollama_chat/qwen3:4b) <aider@aider.chat>
2025-07-22 22:09:50 +10:00
d186565790 first iteration of the service 2025-07-22 21:44:05 +10:00
32c1e3936c first iteration of the service 2025-07-22 21:44:05 +10:00
96cfef7d7c initial 2025-07-22 15:52:55 +10:00
a1465c89e6 initial 2025-07-22 15:52:55 +10:00