peter-mghendi / yap

Yet Another Platform. A PostgreSQL-backed blog engine exposing a secure RESTful API.

yap

Yet Another Platform. Yet another blog/forum backend.

yap's Issues

Podcast support

Work on bringing podcasts to yap as an additional content type.

Rollback forum-oriented additions

Remove forum-oriented additions while keeping quality changes.

Database Compatibility

As of now, the project uses some non-critical PostgreSQL specific features, which lock out other SQL dialects, even though they are well supported by the database infrastructure. Some changes to the models would create a schema that uses only standard SQL features thus making use of gorm's current support for MySQL, SQL Server and SQLite, and possible upcoming CockroachDB support.

To introduce support for Redis and MongoDB, as proposed in Gorm v2, the database layer would have to be improved or rewritten.

Project Roadmap

I realize this project has been stagnant for a while, and yes, development efforts are continuing and this has largely been due to issues on the database layer.

I considered migrating database operations to sqlx or dbr or even the standard library.

However, as much as it may be an unhealthy dependency, I will continue to use gorm, after it's v2 release. Incidentally, this provides a fix for #5.

Confirm account and password reset systems

Hermes has handled this very well, in the past, when used with Gomail.

Utilize relational data

Model relations are defined, but unutilized. They could be used to significantly reduce the API surface.

Logging

As it stands, logging in the project is a complete mess. Each library has it's own logger, which makes for messy output from different parts of the application, rather than a single standardized output stream. Logging is a vital part of the application and should be implemented as soon as possible.