You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue triage and features implementations aren't moving as fast if I expected as I spend most of my time trying to get access to the realword.io and productionready.io domains and related hosting solutions to update the currently hosted implementations.
The current situation makes the maintenance tied to private accounts owned by former maintainers.
I don't plan to leave the project but I always work taking the bus factor in consideration.
As a matter of fact, here are the planned changes to avoid having the project tied to external resources:
Front official implementation
This implementation will be hosted with Github Pages.
The related repository will be given an agnostic name to avoid being tied to the stack (ie realworld-front and not react-realworld-official-app).
Backend official implementation
The usage of the API will be limited to the official front implementation.
It'll allow maintainers to change the API without caring about the impact upon the community.
For the community, I'll provide different ways to host the API:
locally with Stackblitz
remotely with 'deploy to' buttons (Heroku, Railway...)
Such changes will help to reduce hosting costs as well.
Impacts on V1 hosted implementations
The V1 API will stay available as there are too many implementations using it.
The V1 frontend implementation will be updated to encourage people to use the V2 one when it'll be released.
The text was updated successfully, but these errors were encountered:
Issue triage and features implementations aren't moving as fast if I expected as I spend most of my time trying to get access to the realword.io and productionready.io domains and related hosting solutions to update the currently hosted implementations.
The current situation makes the maintenance tied to private accounts owned by former maintainers.
I don't plan to leave the project but I always work taking the bus factor in consideration.
As a matter of fact, here are the planned changes to avoid having the project tied to external resources:
Front official implementation
This implementation will be hosted with Github Pages.
The related repository will be given an agnostic name to avoid being tied to the stack (ie
realworld-front
and notreact-realworld-official-app
).Backend official implementation
The usage of the API will be limited to the official front implementation.
It'll allow maintainers to change the API without caring about the impact upon the community.
For the community, I'll provide different ways to host the API:
Such changes will help to reduce hosting costs as well.
Impacts on V1 hosted implementations
The V1 API will stay available as there are too many implementations using it.
The V1 frontend implementation will be updated to encourage people to use the V2 one when it'll be released.
The text was updated successfully, but these errors were encountered: