Update Path

[Stephan Krebernik]

Hi,

is it possible to Upgrade from 1.0.6 directly to 2.0.2 or is any special action required to do so?

[Scott MacDonald]

So update from 1.0.6 to 2.0.1 was relatively painless. Suggest taking a backup of your data volume after stopping the existing 1.0.6 container as a precaution.

I did note that after upgrading to 2.0.1 that the previous 30 days of delivery logs are inaccessible -- resulting in a "500 Internal Server Error" -- However, delivery logs created post update were accessible without issue.

Additionally, after the first start of the 2.0.1 container -- it seems that some of the services failed to start -- as none of the email related ports (25, 587) were listening -- however, s simply restart of the container (docker restart "image_name") corrected the issue.

[SH]

No action is required (but you should always backup data folder). Logs are still staying at data folder but we switched to another format so only new ones are readable through web...

[Scott MacDonald]

Will the log files orphaned following the upgrade to v2 and above get cleaned/cleared up once they past the new 45 day window displayed for log activity?

[SH]

Yes, there is script which will clear them but with 60 days delay