ã¤ã‚‰ããªã„マルãƒãƒ†ãƒŠãƒ³ã‚·ãƒ¼ã‚’求ã‚ã¦: å…¨ã¦è¦‹ã›ã¾ã™ï¼ SmartHR データベース移行プãƒã‚¸ã‚§ã‚¯ãƒˆã®è£å´ / builderscon 2018
ã¤ã‚‰ããªã„マルãƒãƒ†ãƒŠãƒ³ã‚·ãƒ¼ã‚’求ã‚ã¦: å…¨ã¦è¦‹ã›ã¾ã™ï¼ SmartHR データベース移行プãƒã‚¸ã‚§ã‚¯ãƒˆã®è£å´ / builderscon 2018
ã¤ã‚‰ããªã„マルãƒãƒ†ãƒŠãƒ³ã‚·ãƒ¼ã‚’求ã‚ã¦: å…¨ã¦è¦‹ã›ã¾ã™ï¼ SmartHR データベース移行プãƒã‚¸ã‚§ã‚¯ãƒˆã®è£å´ / builderscon 2018
Managing db schema changes without downtime
At Discourse we have always been huge fans of continuous deployment. Every commit we make heads to our continuous integration test suite. If all the tests pass (ui, unit, integration, smoke) we automatically deploy the latest version of our code to https://meta.discourse.org. This pattern and practice we follow allows the thousands self-installers out there to safely upgrade to the tests-passed ve
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
処ç†ã‚’実行ä¸ã§ã™
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}