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
We're looking into using uwazi for different projects in Digital History at our research center. As these projects are very diverse by nature and come with a lot of different data, it would make sense for us to create different Uwazi instances.
We usually use Docker for these purposes and we started to build our own Docker compose (that we would be happy to contribute to the project) but we were wondering why you decided against Docker in production. Is there a specific reason for that?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're looking into using uwazi for different projects in Digital History at our research center. As these projects are very diverse by nature and come with a lot of different data, it would make sense for us to create different Uwazi instances.
We usually use Docker for these purposes and we started to build our own Docker compose (that we would be happy to contribute to the project) but we were wondering why you decided against Docker in production. Is there a specific reason for that?
All the best,
Beta Was this translation helpful? Give feedback.
All reactions