34 2.2.3 Releasing and deploying a new version...37 2.3 Deployment Strategies…39 2.3.1 In-place updates...40 2.3.2 Blue-Green Deployments...42 2.4 Summary…44 Conclusion…46 Introduction As the Docker cover a work-flow for code development, continuous integration and deployment as well as zero-downtime updates. Such workflows are fairly standard in large organizations, however, we cover how to replicate version is being used by all parts of your project, test upgrades to library versions and push tested updates to all parts of your project. A related but slightly different problem is to manage environment dependencies

This can lead to loss of existing translations, use with caution. Update source strings (source) Updates source strings in bilingual translation file. This is similar to what Update PO files to match POT to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated. • There is just single exported repository with Weblate – Component URL slug Response JSON Object • locked (boolean) – whether component is locked for updates Example JSON data: string: component/lock/ Sets component lock status. Response is same as GET

This can lead to loss of existing translations, use with caution. Update source strings (source) Updates source strings in bilingual translation file. This is similar to what Update PO files to match POT to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated. • There is just single exported repository with Weblate – Component URL slug Response JSON Object • locked (boolean) – whether component is locked for updates Example JSON data: { "locked": false } ## POST /api/components/(string: project)

base.py in name(self, value) 1189 # Used in MultiIndex.levels to avoid silently ignoring name ˓→updates. 1190 raise RuntimeError( -> 1191 "Cannot set name on a level of a MultiIndex. Use " 1192 "'MultiIndex base.py in name(self, value) 1189 # Used in MultiIndex.levels to avoid silently ignoring name ˓→updates. 1190 raise RuntimeError( -> 1191 "Cannot set name on a level of a MultiIndex. Use " 1192 "'MultiIndex of data and index. >>> s is deep False >>> s.values is deep.values or s.index is deep.index False Updates to the data shared by shallow copy and original is reflected in both; deep copy remains unchanged

header support https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.6 • Invalidation after updates or deletes https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.10 • ... probably others S3FeedStorage, S3DownloadHandler and S3FilesStore (issue 1761, issue 1883). • Tons of documentation updates and related fixes (issue 1291, issue 1302, issue 1335, issue 1683, issue 1660, issue 1642, issue Patches Twisted issue while closing the connection pool on HTTPDownloadHandler (commit d0bf957) • Updates documentation on dynamic item classes. (commit eeb589a) • Merge pull request #943 from Lazar-T/patch-3

environment management system that runs on Windows, macOS, and Linux. Conda quickly installs, runs, and updates packages and their dependencies. Conda easily creates, saves, loads, and switches between environments standard RSS practice. https://anaconda.org Updates in the last two weeks en Copyright speeds from cached hostfile * base: repo1.dal.innoscale.net * extras: mirrordenver.fdcservers.net * updates: mirror.tzulo.com Resolving Dependencies --> Running transaction check ---> Package conda

Weblate • Translating documentation using Sphinx ☐ Integrating with Weblate Getting translations updates from Weblate ■ Pushing string changes to Weblate • Managing translations • Adding new translations Read the Docs and translated using Weblate. ## I ntegrating with Weblate ## Getting translations updates from Weblate To fetch updated strings from Weblate you can simply fetch the underlying repository tasks in the background. On a Unix-likesystem, this can be scheduled using cron: # Fulltext index updates */5 * * * * cd /usr/share/weblate/; ./manage.py update_index # Cleanup stale objects @daily cd

This can lead to loss of existing translations, use with caution. Update source strings (source) Updates source strings in bilingual translation file. This is similar to what Update PO files to match POT to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated. - There is just single exported repository with Weblate – Component URL slug Response JSON Object: • locked (boolean) – whether component is locked for updates Example JSON data: { "locked": false } POST /api/components/(string: project)/(string: component)/lock/

This can lead to loss of existing translations, use with caution. Update source strings (source) Updates source strings in bilingual translation file. This is similar to what Update PO files to match POT to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated. • There is just single exported repository with Weblate translations task queue might contain some info, but is usually not needed for a backup. At most you will lose updates not yet been processed to translation memory. It is recommended to perform the fulltext or repository

maintenance tasks in the background. On Unix system, this can be scheduled using cron: # Fulltext index updates */5 * * * * cd /usr/share/weblate/; ./manage.py update_index # Cleanup stale objects @daily cd corresponding environment variable: ## See also Configuration ## Updating It is recommended that you try updates on a clone of your Weblate installation before running the actual update. To create such a clone /manage.py syncdb, ./manage.py setupgroups and ./manage.py setuplang is recommended to get latest updates of privileges and language definitions. #### Upgrade from 0.9 to 1.0 On upgrade to version 1.0