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
Since some months ago, there are some dockerfiles available in the openstreetmap-website repository. These dockerfiles are even used in the test suite. Although I don't know how ready for production they are, I believe they give us some confidence that it will be always compatible with the latest versions.
Should we consider switching to it? Their dockerfile seems much simpler than the osm-seed one, and probably would make it easier for us to keep it updated.
The text was updated successfully, but these errors were encountered:
willemarcel
changed the title
Switch to docker file provided by openstreetmap-website
Switch to dockerfile provided by openstreetmap-website
Nov 26, 2021
I'm really hoping we can simplify our Dockerfile. However, am fairly certain that the container provided on the openstreetmap-website repo is for development use and not suitable for production. @Rub21 do you have a better idea? I can also do a bit more reading, but that seemed to be the case the last time I checked.
@batpad@willemarcel , It think this is something that we should try, the current Dockerfile does not support the latest version of openstreetmap-website and it is a disadvantage of osm-seed, i think for make it available for production we may need to consider some extra libraries such as. Passenger + Apache modulo .
Since some months ago, there are some dockerfiles available in the openstreetmap-website repository. These dockerfiles are even used in the test suite. Although I don't know how ready for production they are, I believe they give us some confidence that it will be always compatible with the latest versions.
Should we consider switching to it? Their dockerfile seems much simpler than the osm-seed one, and probably would make it easier for us to keep it updated.
cc @batpad @Rub21
The text was updated successfully, but these errors were encountered: