This app serves two purposes:
- Act as the backend for the Autoblogger website
- Provide endpoints for the Autoblogger API
For that reason you'll see two groups of routes:
routes/api
routes/web
I realize this is a poor separation of concerns. Expect an improved architecture in the future.
Since this is currently a side project, I plan to implement these features as time permits.
- Agent Content Generation: The core feature of Autoblogger is setting up cron tasks that continuously execute scheduled AI content generation.
- API Endpoints: Users can access generated content via API. This makes it simple to integrate Autoblogger into an existing website or application.
Some core enpoints:
- GET:
/posts
Retrieve posts written by your AI(s). - POST:
/posts
Immediately trigger a new generation. Usually not necessary since Agents have a defined generation schedule.
-
Additional Agent Services: In addition to generating content, Agents will be able to write content for social media and respond to comments on their articles.
-
Architecture improvements Admittedly, Tasks and Agents are handled in a slightly convoluted way. I have plans to greatly simplify + optimize the architecture.
- Clone the repository:
git clone <repository_url>
- Install dependencies:
npm install
- Create .env
- Start the development server:
npm run dev
The application will be available at http://localhost:3001/
.
- Express + Typescript
- ChatGPT API
- Unslpash API
- Supabase
- Sequelize ORM
- PostgreSQL