This step provides the server information needed to make technical decisions or prepare server resources in advance.
- In the TRANFU AI Opportunities group, mention the server operations bot and send it a message.
Sample message
I plan to build a ___ . Please give me a technical solution.
For example:
I plan to build a multimedia dashboard. Please give me a technical solution.
Preparation Before Release
Repository requirements
-
The repository must not be under your personal account.
-
It must be under the company account.
-
It can be either
publicorprivate.
For example:
https://github.com/tranfu-labs/alphaos-app
Naming requirements
-
Use lowercase letters only.
-
End the name with
-app. -
Separate words with hyphens (
-).
The following names meet the requirements:
alphaos-app news-app
You no longer need to install the coolify-deploy skill locally.
Start Deployment
- In the TRANFU group, mention the server operations bot and send it a message.
Sample message
Remember to replace the URL and environment variables with your own.
Deploy project: https://github.com/tranfu-labs/alphaos-app Environment variables: ALPHAOS_SEARCH_PROVIDER=tavily # tavily | exa | fixture (no keys → fixture, hermetic)
ALPHAOS_SEARCH_API_KEYS=your_tavily_api_key ALPHAOS_SEARCH_BASE_URL= # optional override (proxy / Exa endpoint); blank = vendor default ALPHAOS_SEARCH_MAX_RESULTS=5 # top-k hits per query ALPHAOS_SEARCH_RECENCY_DAYS=30 # recent-news window (days); blank = no recency filter ALPHAOS_SEARCH_DEPTH=basic # tavily search_depth: basic | advanced ALPHAOS_SEARCH_TIMEOUT=8 # per-search seconds
ENV Changes
You can now ask an Internal team member directly to change a specific ENV variable. We will consider narrowing the permissions over time.
Frequently Asked Questions
Why Didn't the Hermes Agent Conversation Continue?
By default, the session is reset after 24 hours without a message and also every day at 4:00 a.m. local time, whichever comes first. In other words, with the default configuration, the group-message context is not retained forever. The settings are session_reset.mode: both, idle_minutes: 1440, and at_hour: 4. After a reset, a new conversation context is created, but Hermes first attempts to write important information to long-term memory. hermes-agent/cli-config.yaml.example at main · NousResearch/hermes-agent
Live Projects
This section will not be maintained for now. A website operations bot will handle it in the future.
| Project Name | Maintainer | Launch Status | GitHub Link | Live Link |
|---|---|---|---|---|
| alphaos | Internal team member | ✅ Live | https://github.com/tranfu-labs/alphaos-app | https://alphaos-app.tranfu.com/ |
| news | Internal team member | 🚀 Launching | https://github.com/tranfu-labs/news-app | |
| markdown-kits-app | Internal team memberInternal team member | ✅ Live | https://github.com/tranfu-labs/markdown-kits-app | https://markdown-kits-app.tranfu.com/ |
Archived Documentation
Technical Framework Conventions
Database: Use a local SQLite database. We do not use services such as Supabase because they can become expensive as the number of projects grows, while about 90% of our projects will most likely have few visitors and small amounts of data.
Note: We need version control for the database.
Use Prism for JavaScript.
Authentication: Implement simple email-and-password authentication with SQLite.
Server-side reverse proxy: You do not need to handle this when developing the project because it is already configured on the server.
Port management: You can choose a default port initially. If it conflicts with another port during deployment, an Internal team member will change it.
AI services: For now, configure your own .env file and access the services directly.
What You Will Get After a Successful Deployment
-
A domain name, such as szu-gokaku-app.tranfu.com.
-
A listing in the product list on the home page.
Automation
TODO list for future iterations:
| Workflow | Automated? | |
|---|---|---|
| Prepare a project for deployment after building it with your own Agent | 1. Prepare GitHub and its CI bot1. Prepare the deployment documentation1. Configure the relevant secret through gh | |
| Perform the relevant operations on the server | 1. Automatically detect the creation of a new project1. Add the domain and its DNS records1. Ensure CI is connected and the local service is running1. Run basic connectivity and accessibility tests1. Add the project to the website | |
| Automatic optimization | 1. Provide codebase optimization suggestions during the initial deployment1. Provide product experience suggestions during the initial deployment (web only for now)1. Run automated end-to-end tests and produce screenshots and videos | |
| Long-term maintenance | 1. Respond automatically to CI failures1. Add server status alerts similar to https://www.githubstatus.com/ |
Related Development Documentation
- Automated project deployment documentation