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
Relying on community resources is fine for development, but for long term production environments it may not be the greatest approach, especially since many projects may inadvertently publish breaking updates with the same tags (even internal ones, such as docker-postgis).
Making sure that there are tagged releases, which includes additional support for for all the upstream services as well, is recommended, although there may be certain limitations on the available free services and infrastructure etc.
Vulnerability scanning #100 will be an important prerequisite for this approach
The text was updated successfully, but these errors were encountered:
Relying on community resources is fine for development, but for long term production environments it may not be the greatest approach, especially since many projects may inadvertently publish breaking updates with the same tags (even internal ones, such as docker-postgis).
Making sure that there are tagged releases, which includes additional support for for all the upstream services as well, is recommended, although there may be certain limitations on the available free services and infrastructure etc.
Vulnerability scanning #100 will be an important prerequisite for this approach
The text was updated successfully, but these errors were encountered: