Dears, over the past few weeks we have been working on developing a mechanism to provide Editoria (and all of it’s flavors) as a Service on demand, similar to how we provide other platforms. As you already know, there are pieces of documentation for Editoria in need of further updates, which generated delays on our part in terms of implementation. To add more to it, more time spend on R&D also contributed having a process that took us longer than expected, especially while testing out every approach we could think of, to make it more scalable.
There proposed setup is as follows:
- Editoria dependencies
- De-dockerized version of postgresql
The reason we are adamant on using non dockerized version of postgres, is because this way we can provide more accurate backups and security patches. While docker makes sense in a development environment, we don’t recommend it in a production environment, as it also adds unnecessary computations, increasing the load time.
We’ve noted a couple points that might be considered to be an issue regarding the deployment of Editoria on a bigger scale, which is the ultimate goal:
- Editoria’s dependencies all rely on dockerized version of postgres, whereas we need to use the non-dockerized version of it. This prevents users from uploading .docx, export pdf and so on;
- We are unclear if there is a way to serve Editoria with NODE_ENV=production, which would help bring the load times down by a large margin.
How we propose to proceed:
We are working on patching it up for now, however an approach where the services that Editoria needs are not hard-binded to Docker’s postgresql container is the best possible solution to this. With that said, @kominoshja and myself will talk to @alexgeorg about this and will update you. The idea is to review the proposed setup together and see if there’s anything that can be improved from our side in terms of the approach we are proposing.
I’ll will update you about the progress.