原文:Docker
如果你在单个生产节点上用过Docker,然后发现单个节点的资源不够用,那么你会怎么做呢?我也遇到过这种情况! 关于在生产环境中使用Docker Swarm,我会为你提供一些建议,也许能够帮到你。这些都是我一年来积累的一些经验。
另外,如果你对Docker Swam不熟悉的话,可以参考我之前的博客My experience with Docker Swarm - when you may need it?(http://suo.im/1m7qW8)
1. 阅读官方文档
| // Credit Ryan Carniato https://frontendmasters.com/courses/reactivity-solidjs/ | |
| let context = []; | |
| export function untrack(fn) { | |
| const prevContext = context; | |
| context = []; | |
| const res = fn(); | |
| context = prevContext; | |
| return res; |
| import regex as re | |
| import requests | |
| MAX_HEADING_LENGTH = 7 | |
| MAX_HEADING_CONTENT_LENGTH = 200 | |
| MAX_HEADING_UNDERLINE_LENGTH = 200 | |
| MAX_HTML_HEADING_ATTRIBUTES_LENGTH = 100 | |
| MAX_LIST_ITEM_LENGTH = 200 | |
| MAX_NESTED_LIST_ITEMS = 6 | |
| MAX_LIST_INDENT_SPACES = 7 |
| /* | |
| * This document is provided to the public domain under the | |
| * terms of the Creative Commons CC0 public domain license | |
| */ | |
| How to boot Arch Linux ARM in QEMU (patched for M1) | |
| Prerequisites: | |
| QEMU - patched for M1 processors - patches: https://github.com/utmapp/qemu |
| <artifacts_info> | |
| The assistant can create and reference artifacts during conversations. Artifacts are for substantial, self-contained content that users might modify or reuse, displayed in a separate UI window for clarity. | |
| # Good artifacts are... | |
| - Substantial content (>15 lines) | |
| - Content that the user is likely to modify, iterate on, or take ownership of | |
| - Self-contained, complex content that can be understood on its own, without context from the conversation | |
| - Content intended for eventual use outside the conversation (e.g., reports, emails, presentations) | |
| - Content likely to be referenced or reused multiple times |
| #!/usr/bin/python3 | |
| import sys | |
| import asyncio | |
| import greenlet | |
| class AsyncIoGreenlet(greenlet.greenlet): | |
| def __init__(self, driver, fn): | |
| greenlet.greenlet.__init__(self, fn, driver) | |
| self.driver = driver |
原文:Docker
如果你在单个生产节点上用过Docker,然后发现单个节点的资源不够用,那么你会怎么做呢?我也遇到过这种情况! 关于在生产环境中使用Docker Swarm,我会为你提供一些建议,也许能够帮到你。这些都是我一年来积累的一些经验。
另外,如果你对Docker Swam不熟悉的话,可以参考我之前的博客My experience with Docker Swarm - when you may need it?(http://suo.im/1m7qW8)
1. 阅读官方文档
| FROM nginx:alpine AS builder | |
| # nginx:alpine contains NGINX_VERSION environment variable, like so: | |
| # ENV NGINX_VERSION 1.15.0 | |
| # Our NCHAN version | |
| ENV NCHAN_VERSION 1.1.15 | |
| # Download sources | |
| RUN wget "http://nginx.org/download/nginx-${NGINX_VERSION}.tar.gz" -O nginx.tar.gz && \ |
100+ 经典技术书籍,涵盖:计算机系统与网络、系统架构、算法与数据结构、前端开发、后端开发、移动开发、数据库、测试、项目与团队、程序员职业修炼、求职面试 和 编程相关的经典书籍。
这个列表综合了伯乐在线网站以往推荐经典书籍文章中的列表,以及在微信和微博中被广泛推荐的好书。虽然已经包括了100多本,覆盖的面也比较全。仍然有很多方面需要补充,而且相信还有很多没有被收录的好书。欢迎大家在 issues 中推荐或自荐。
| local count = 0 | |
| local sum = 0 | |
| local min = 0 | |
| local max = 0 | |
| local cursor = "0" | |
| local result = nil | |
| local data = nil | |
| repeat | |
| result = redis.call("zscan", KEYS[1], cursor, "count", 100) |
| function password_encode(password) | |
| local bcrypt = require 'bcrypt' | |
| return bcrypt.digest(password, 12) | |
| end | |
| function check_password(password, encoded_password) | |
| local bcrypt = require 'bcrypt' | |
| return bcrypt.verify(password, encoded_password) | |
| end |