Coding

在VS Code中调试PHP

Thu, 15 Sep 2022 19:42:11 +0000

php安装xdebug

将phpinfo()页面html源代码粘贴到Xdebug Installation Wizard。
xdebug会根据你本地的php环境提供相应的版本下载及配置说明。
安装配置成功后，可以通过xdebug_info()查看。

VS Code配置

安装PHP Debug插件
Run And Debug中Open ’launch.json'

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Listen for Xdebug",
            "type": "php",
            "request": "launch",
            "port": 9003
        },
        {
            "name": "Launch currently open script",
            "type": "php",
            "request": "launch",
            "program": "${file}",
            "cwd": "${fileDirname}",
            "port": 0,
            "runtimeArgs": [
                "-dxdebug.start_with_request=yes"
            ],
            "env": {
                "XDEBUG_MODE": "debug,develop",
                "XDEBUG_CONFIG": "client_port=${port}"
            }
        },
        {
            "name": "Launch Built-in web server",
            "type": "php",
            "request": "launch",
            "runtimeArgs": [
                "-dxdebug.mode=debug",
                "-dxdebug.start_with_request=yes",
                "-S",
                "localhost:0"
            ],
            "program": "",
            "cwd": "${workspaceRoot}",
            "port": 9003,
            "serverReadyAction": {
                "pattern": "Development Server \\(http://localhost:([0-9]+)\\) started",
                "uriFormat": "http://localhost:%s",
                "action": "openExternally"
            }
        }
    ]
}

通过Start Debugging启动即可。

小程序组件嵌套防止事件冒泡

Sat, 09 May 2020 00:00:00 +0000

在实际使用中，遇到下面这种情况。在父View的绑定事件openImgDialog实现图片预览，子View绑定事件delImage实现删除图片。如下图效果：

<view class="bg-white padding">
  <view class="grid col-4 grid-square">
    <view class="bg-img" wx:for="{{detail.imgInfo}}" wx:key style="background-image:url({{item.url}});" bindtap="openImgDialog" data-url="{{item.url}}">
      <view class="is-tag bg-red" bindtap="delImage" data-id="{{item.id}}">
        <text class="isIcon-close"></text>
      </view>
    </view>
  </view>
</view>

在点击子View删除图片事件时，会同时触发父View预览事件。如下图所示：

事件分为冒泡事件和非冒泡事件：

冒泡事件：当一个组件上的事件被触发后，该事件会向父节点传递。
非冒泡事件：当一个组件上的事件被触发后，该事件不会向父节点传递。

小程序官方文档-事件

使用Vue CLI构建Vue项目

Mon, 27 Apr 2020 00:00:00 +0000

全局安装vue-cli

npm install -g @vue/cli
# OR
yarn global add @vue/cli

Usage: vue <command> [options]

Options:
  -V, --version                              output the version number
  -h, --help                                 output usage information

Commands:
  create [options] <app-name>                create a new project powered by vue-cli-service
  add [options] <plugin> [pluginOptions]     install a plugin and invoke its generator in an already created project
  invoke [options] <plugin> [pluginOptions]  invoke the generator of a plugin in an already created project
  inspect [options] [paths...]               inspect the webpack config in a project with vue-cli-service
  serve [options] [entry]                    serve a .js or .vue file in development mode with zero config
  build [options] [entry]                    build a .js or .vue file in production mode with zero config
  ui [options]                               start and open the vue-cli ui
  init [options] <template> <app-name>       generate a project from a remote template (legacy API, requires @vue/cli-init)
  config [options] [value]                   inspect and modify the config
  outdated [options]                         (experimental) check for outdated vue cli service / plugins
  upgrade [options] [plugin-name]            (experimental) upgrade vue cli service / plugins
  migrate [options] [plugin-name]            (experimental) run migrator for an already-installed cli plugin
  info                                       print debugging information about your environment

  Run vue <command> --help for detailed usage of given command.

可以通过vue init或vue create创建项目。 Vue CLI的包名称由vue-cli改成了@vue/cli。如果你已经全局安装了旧版本的vue-cli (1.x 或 2.x)，你需要先通过npm uninstall vue-cli -g或yarn global remove vue-cli卸载它。

小程序子组件列表下拉刷新

Wed, 15 Apr 2020 00:00:00 +0000

最近，研究小程序的过程中，遇到一个问题：小程序的组件Component并没有的Page下拉监听事件：

onPullDownRefresh 监听用户下拉动作
onReachBottom 页面上拉触底事件的处理函数

比如说，下面这样的结构：

index page 引用search-head组件
search-head component 引用search-list组件
search-list component 显示列表数据

那如何才能刷新组件的列表呢：

search-head提供搜索、翻页方法，传递数据给search-list。
search-list组件只显示数据。
page监听onReachBottom事件，然后调用search-head中的方法。

search-head

搜索头部组件，此组件内引用搜索列表组件。在这个组件内，实现搜索、翻页功能。通过组件将数据传递给子组件。

优雅的关闭springboot程序

Sat, 26 Oct 2019 00:00:00 +0000

使用jar形式部署springboot程序后，通过kill进程关闭程序，总是不踏实。好在，官方提供了优雅关闭应用程序的方式。

引入依赖

首先，在POM中引入依赖

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-actuator</artifactId>
</dependency>

配置application

以2.1.8.RELEASE为例，application.yml配置如下：

management:
  endpoint:
    shutdown:
      enabled: true
  endpoints:
    web:
      exposure:
        include: "*"
      base-path: /actuator

发送POST请求

curl -d "" --header "Content-Type:application/json" http://127.0.0.1:8080/actuator/shutdown
{"message":"Shutting down, bye..."}

Spring Boot Actuator

actuator可以帮助你监控和管理Spring Boot应用，比如健康检查、审计、统计和HTTP追踪等。所有的这些特性可以通过JMX或者HTTP endpoints来获得。
Actuator通过创建Endpoint来暴露HTTP或者JMX来监控和管理应用。

mybatis sql中使用<或<=时报错SAXParseException

Thu, 10 Oct 2019 00:00:00 +0000

使用mybatis时，当sql中使用<或<=时：

SELECT * FROM user WHERE age < 36
SELECT * FROM user WHERE age <= 36

会报错SAXParseException: 元素内容必须由格式正确的字符数据或标记组成。

org.apache.ibatis.builder.BuilderException: Error creating document instance.  Cause: org.xml.sax.SAXParseException; lineNumber: 7; columnNumber: 37; 元素内容必须由格式正确的字符数据或标记组成。
	at org.mybatis.spring.SqlSessionFactoryBean.buildSqlSessionFactory(SqlSessionFactoryBean.java:596) ~[mybatis-spring-2.0.2.jar:2.0.2]
	at org.mybatis.spring.SqlSessionFactoryBean.afterPropertiesSet(SqlSessionFactoryBean.java:475) ~[mybatis-spring-2.0.2.jar:2.0.2]
	at org.mybatis.spring.SqlSessionFactoryBean.getObject(SqlSessionFactoryBean.java:616) ~[mybatis-spring-2.0.2.jar:2.0.2]
	at org.mybatis.spring.boot.autoconfigure.MybatisAutoConfiguration.sqlSessionFactory(MybatisAutoConfiguration.java:180) ~[mybatis-spring-boot-autoconfigure-2.1.0.jar:2.1.0]
	at org.mybatis.spring.boot.autoconfigure.MybatisAutoConfiguration$$EnhancerBySpringCGLIB$$9adef889.CGLIB$sqlSessionFactory$1(<generated>) ~[mybatis-spring-boot-autoconfigure-2.1.0.jar:2.1.0]
	at org.mybatis.spring.boot.autoconfigure.MybatisAutoConfiguration$$EnhancerBySpringCGLIB$$9adef889$$FastClassBySpringCGLIB$$abadc28a.invoke(<generated>) ~[mybatis-spring-boot-autoconfigure-2.1.0.jar:2.1.0]
	at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:244) ~[spring-core-5.1.9.RELEASE.jar:5.1.9.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:363) ~[spring-context-5.1.9.RELEASE.jar:5.1.9.RELEASE]
	at org.mybatis.spring.boot.autoconfigure.MybatisAutoConfiguration$$EnhancerBySpringCGLIB$$9adef889.sqlSessionFactory(<generated>) ~[mybatis-spring-boot-autoconfigure-2.1.0.jar:2.1.0]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_172]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_172]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_172]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_172]
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154) ~[spring-beans-5.1.9.RELEASE.jar:5.1.9.RELEASE]
	... 44 common frames omitted
Caused by: org.apache.ibatis.builder.BuilderException: Error creating document instance.  Cause: org.xml.sax.SAXParseException; lineNumber: 7; columnNumber: 37; 元素内容必须由格式正确的字符数据或标记组成。
	at org.apache.ibatis.parsing.XPathParser.createDocument(XPathParser.java:260) ~[mybatis-3.5.2.jar:3.5.2]
	at org.apache.ibatis.parsing.XPathParser.<init>(XPathParser.java:126) ~[mybatis-3.5.2.jar:3.5.2]
	at org.apache.ibatis.builder.xml.XMLMapperBuilder.<init>(XMLMapperBuilder.java:80) ~[mybatis-3.5.2.jar:3.5.2]
	at org.mybatis.spring.SqlSessionFactoryBean.buildSqlSessionFactory(SqlSessionFactoryBean.java:593) ~[mybatis-spring-2.0.2.jar:2.0.2]
	... 57 common frames omitted
Caused by: org.xml.sax.SAXParseException: 元素内容必须由格式正确的字符数据或标记组成。
	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1472) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.startOfMarkup(XMLDocumentFragmentScannerImpl.java:2635) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2732) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:842) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:243) ~[na:1.8.0_172]
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339) ~[na:1.8.0_172]
	at org.apache.ibatis.parsing.XPathParser.createDocument(XPathParser.java:258) ~[mybatis-3.5.2.jar:3.5.2]
	... 60 common frames omitted

这是由于mybatis的SQL配置在XML中，一些特殊符号在XML解析时被转义。

maven加载本地jar包

Sun, 29 Sep 2019 00:00:00 +0000

添加引用，开发已经没有问题。

<dependency>
    <groupId>org.bouncycastle</groupId>
    <artifactId>bcpkix-jdk15on</artifactId>
    <version>152</version>
    <scope>system</scope>
    <systemPath>${project.basedir}/src/main/resources/lib/xxxx.jar</systemPath>
</dependency>

打包如果是springboot项目，只需要配上includeSystemScope即可：

<build>
    <plugins>
        <plugin>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-maven-plugin</artifactId>
            <configuration>
                <includeSystemScope>true</includeSystemScope>
            </configuration>
        </plugin>
    <plugins>
</build>

springboot整合mybatis

Wed, 25 Sep 2019 00:00:00 +0000

添加Maven依赖

<dependency>
    <groupId>org.mybatis.spring.boot</groupId>
    <artifactId>mybatis-spring-boot-starter</artifactId>
    <version>RELEASE</version>
</dependency>

<dependency>
    <groupId>mysql</groupId>
    <artifactId>mysql-connector-java</artifactId>
    <scope>runtime</scope>
</dependency>

<dependency>
    <groupId>com.alibaba</groupId>
    <artifactId>druid</artifactId>
    <version>RELEASE</version>
</dependency>

在application.yml中配置数据源和mybatis

server:
  port: 8080

spring:
  datasource:
    type: com.alibaba.druid.pool.DruidDataSource
    url: jdbc:mysql://127.0.0.1:3306/test1?jdbcCompliantTruncation=false&allowMultiQueries=true&useUnicode=true&characterEncoding=UTF-8&serverTimezone=GMT
    driver-class-name: com.mysql.cj.jdbc.Driver
    username: root
    password: root

mybatis:
  mapper-locations: classpath:mapper/*.xml

mysql

CREATE TABLE `user` (
	`id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT,
	`name` VARCHAR(50) NULL DEFAULT NULL,
	`age` INT(11) UNSIGNED NULL DEFAULT NULL,
	PRIMARY KEY (`id`)
)
COLLATE='utf8_general_ci'
ENGINE=InnoDB
AUTO_INCREMENT=3;

INSERT INTO `user` (`id`, `name`, `age`) VALUES (1, 'alita', 23);
INSERT INTO `user` (`id`, `name`, `age`) VALUES (2, 'sofia', 33);

DAO

├─main
│  ├─java
│  │  └─top
│  │      └─guoj
│  │          └─springboot
│  │              ├─controller
│  │              ├─dao
│  │              ├─entity
│  │              └─service
│  └─resources
│      └─mapper

UserDao.java

package top.guoj.springboot.dao;

import org.apache.ibatis.annotations.Mapper;

import java.util.List;
import java.util.Map;

@Mapper
public interface UserDao {
	List<Map<String, Object>> getUser();
}

UserDao.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mapper PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN" "http://mybatis.org/dtd/mybatis-3-mapper.dtd">

<mapper namespace="top.guoj.springboot.dao.UserDao">

    <select id="getUser" resultType="java.util.HashMap">
      select * from user;
    </select>

</mapper>

使用

package top.guoj.springboot.controller;

import com.alibaba.fastjson.JSONObject;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;
import top.guoj.springboot.dao.UserDao;

import java.util.List;
import java.util.Map;

@RestController
public class HelloController {

	@Autowired
	private UserDao userDao;

	@RequestMapping("/mybatis")
	String mybatis() {
		List<Map<String, Object>> users = userDao.getUser();
		return JSONObject.toJSONString(users);
	}
}

在配置application.yml文件中使用自定义属性

Wed, 25 Sep 2019 00:00:00 +0000

引入springboot依赖

pom.xml

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-configuration-processor</artifactId>
    <optional>true</optional>
</dependency>

自定义属性

在application.properties中配置自定义属性。

top.guoj.user-name=hello
top.guoj.pass-word=word

## OR
top.guoj.userName=hello
top.guoj.passWord=word

新建映射类

通过@ConfigurationProperties注解并配置prefix属性。

@Component
@ConfigurationProperties(prefix = "top.guoj")
public class Configure {

	private String userName;
	private String passWord;

	public String getUserName() {
		return userName;
	}

	public void setUserName(String userName) {
		this.userName = userName;
	}

	public String getPassWord() {
		return passWord;
	}

	public void setPassWord(String passWord) {
		this.passWord = passWord;
	}
}

使用

@RestController
public class HelloController {

	@Autowired
	private Configure configure;

	@RequestMapping("/configure")
	String configure() {
		return configure.getUserName() + configure.getPassWord();
	}
}

Dubbo配置

Wed, 08 Aug 2018 02:28:29 +0000

Dubbo配置可以使用XML、Properties、API、Annotation。

XML配置

Provider

<beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
	xmlns="http://www.springframework.org/schema/beans"
	xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd
       http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
	<dubbo:application name="demo-provider" />
	<dubbo:registry address="multicast://224.5.6.7:1234" />
	<bean id="helloService" class="top.guoj.provider.HelloServiceImpl" />
	<dubbo:service interface="top.guoj.api.HelloService" timeout="5000"
		ref="helloService" />
</beans>

Consumer

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
	xmlns="http://www.springframework.org/schema/beans"
	xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd
       http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
	<dubbo:application name="dubbo-consumer" />
	<dubbo:registry address="multicast://224.5.6.7:1234" />
	<dubbo:reference id="helloService" check="false" timeout="1500" retries="1"
		interface="top.guoj.api.HelloService" />
</beans>

Properties配置

API配置

Provider

HelloService helloService = new HelloServiceImpl();

ApplicationConfig application = new ApplicationConfig();
application.setName("dubbo-provider");

RegistryConfig registry = new RegistryConfig();
registry.setAddress("multicast://224.5.6.7:1234");

ServiceConfig<HelloService> service = new ServiceConfig<HelloService>(); 
service.setApplication(application);
service.setRegistry(registry);
service.setInterface(HelloService.class);
service.setRef(helloService);
//service.setVersion("1.0.0");

service.export();

System.out.println("Provider started.");
System.in.read();

Consumer

ApplicationConfig application = new ApplicationConfig();
application.setName("dubbo-consumer");

RegistryConfig registry = new RegistryConfig();
registry.setAddress("multicast://224.5.6.7:1234");

ReferenceConfig<HelloService> reference = new ReferenceConfig<>();
reference.setApplication(application);
reference.setRegistry(registry);
reference.setInterface(HelloService.class);
//reference.setVersion("1.0.0");

HelloService demoService = reference.get();
System.out.println(demoService.sayHello("world"));

provider与consumer的设置要保持一致。比如 provider设置了setVersion，consumer也需要同时设置，否则抛出异常：

Dubbo注册中心Resitry之Redis

Mon, 06 Aug 2018 01:40:32 +0000

<dubbo:registry address="redis://10.20.153.10:6379" />
<dubbo:registry address="redis://10.20.153.10:6379?backup=10.20.153.11:6379,10.20.153.12:6379" />

<dubbo:registry protocol="redis" address="10.20.153.10:6379" />
<dubbo:registry protocol="redis" address="10.20.153.10:6379,10.20.153.11:6379,10.20.153.12:6379" />

数据结构

使用Redis的Hash结构存储数据

主Key为服务名和类型。
Map中的Key为URL地址。
Map中的Value为过期时间，用于判断脏数据，脏数据由监控中心删除。

使用Redis的Publish/Subscribe事件通知数据变更

通过事件的值区分事件类型：register、unregister、subscribe、unsubscribe。
consumer订阅指定的provider，只会收到指定provider的register、unregister事件。
监控中心订阅/dubbo/*，会收到所有服务的所有变更事件。

调用过程

provider启动时，向Key:/dubbo/top.guoj.api.HelloService/providers下，添加当前提供者的地址。
并向Channel:/dubbo/top.guoj.api.HelloService/providers发送register事件。
服务消费方启动时，从Channel:/dubbo/com.foo.BarService/consumers订阅register和unregister事件。
并向Key:/dubbo/com.foo.BarService/consumers下，添加当前消费者的地址。
服务消费方收到register和unregister事件后，从Key:/dubbo/com.foo.BarService/providers下获取提供者地址列表。
服务监控中心启动时，从Channel:/dubbo/*订阅register和unregister，以及subscribe和unsubsribe事件。
服务监控中心收到register和unregister事件后，从Key:/dubbo/com.foo.BarService/providers下获取提供者地址列表。
服务监控中心收到subscribe和unsubsribe事件后，从Key:/dubbo/com.foo.BarService/consumers下获取消费者地址列表。

启动provdier

127.0.0.1:6379> keys *
1) "/dubbo/top.guoj.api.HelloService/providers"
127.0.0.1:6379> type /dubbo/top.guoj.api.HelloService/providers
hash
127.0.0.1:6379> hgetall /dubbo/top.guoj.api.HelloService/providers
1) "dubbo://192.168.100.61:20880/top.guoj.api.HelloService?anyhost=true&application=demo-provider&dubbo=2.6.2&generic=false&interface=top.guoj.api.HelloService&methods=sayHello&pid=5252&side=provider&timestamp=1533106855687"
2) "1533106976445"

启动consumer

127.0.0.1:6379> keys *
1) "/dubbo/top.guoj.api.HelloService/consumers"
2) "/dubbo/top.guoj.api.HelloService/providers"
127.0.0.1:6379> type /dubbo/top.guoj.api.HelloService/consumers
hash
127.0.0.1:6379> hgetall /dubbo/top.guoj.api.HelloService/consumers
1) "consumer://192.168.100.61/top.guoj.api.HelloService?application=dubbo-consumer&category=consumers&check=false&dubbo=2.6.2&interface=top.guoj.api.HelloService&methods=sayHello&pid=7196&side=consumer&timestamp=1533107247126"
2) "1533107337246"
127.0.0.1:6379>

选项

可通过<dubbo:registry group=“dubbo”/>设置redis中key的前缀，缺省为dubbo。
可通过<dubbo:registry cluster=“replicate”/>设置redis集群策略，缺省为failover。
- failover: 只写入和读取任意一台，失败时重试另一台，需要服务器端自行配置数据同步。
- replicate: 在客户端同时写入所有服务器，只读取单台，服务器端不需要同步，注册中心集群增大，性能压力也会更大。

Dubbo注册中心Registry之Zookeeper

Fri, 03 Aug 2018 01:12:56 +0000

Zookeeper

在dubbo提供的4种注册方式中，官方推荐使用apache开源项目 Zookeeper

以服务接口为例：

<dubbo:service interface="top.guoj.api.HelloService" ref="helloService" />

Provider启动：在zookeeper路径/dubbo/top.guoj.api.HelloService/providers写入自己的URL地址。
Consumer启动：订阅/dubbo/top.guoj.api.HelloService/providers目录下的URL地址，并在/dubbo/com.foo.BarService/consumers目录写入自己的URL地址。
Monitor Center启动：订阅/dubbo/top.guoj.api.HelloService/consumers和/dubbo/top.guoj.api.HelloService/providers下的所有URL地址。

启动Provider

[zk: localhost:2181(CONNECTED) 46] ls /
[dubbo, zookeeper]
[zk: localhost:2181(CONNECTED) 47] ls /dubbo
[top.guoj.api.HelloService]
[zk: localhost:2181(CONNECTED) 48] ls /dubbo/top.guoj.api.HelloService
[configurators, providers]
[zk: localhost:2181(CONNECTED) 51] ls /dubbo/top.guoj.api.HelloService/providers
[dubbo%3A%2F%2F192.168.100.61%3A20880%2Ftop.guoj.api.HelloService%3Fanyhost%3Dtrue%26application%3Ddemo-provider%26dubbo%3D2.6.2%26generic%3Dfalse%26interface%3Dtop.guoj.api.HelloService%26methods%3DsayHello%26pid%3D8140%26side%3Dprovider%26timestamp%3D1533023619863]

启动Consumer

[zk: localhost:2181(CONNECTED) 49] ls /dubbo/top.guoj.api.HelloService
[consumers, configurators, routers, providers]
[zk: localhost:2181(CONNECTED) 50] ls /dubbo/top.guoj.api.HelloService/consumers
[consumer%3A%2F%2F192.168.100.61%2Ftop.guoj.api.HelloService%3Fapplication%3Ddubbo-consumer%26category%3Dconsumers%26check%3Dfalse%26dubbo%3D2.6.2%26interface%3Dtop.guoj.api.HelloService%26methods%3DsayHello%26pid%3D11136%26side%3Dconsumer%26timestamp%3D1533023700514]

当提供者出现断电等异常停机时，注册中心能自动删除提供者信息。
当注册中心重启时，能自动恢复注册数据，以及订阅请求。
当会话过期时，能自动恢复注册数据，以及订阅请求。
当设置<dubbo:registry check=“false”/>时，记录失败注册和订阅请求，后台定时重试。
可通过<dubbo:registry username=“admin” password=“1234”/>设置zookeeper登录信息。
可通过<dubbo:registry group=“dubbo”/>设置zookeeper的根节点，默认是dubbo。
支持*号通配符<dubbo:reference group="" version=""/>，可订阅服务的所有分组和所有版本的提供者。

<dubbo:registry address="zookeeper://192.168.100.61:2181" group="test1" />
<dubbo:registry address="zookeeper://192.168.100.61:2181" group="test2" />
<bean id="helloService" class="top.guoj.provider.HelloServiceImpl" />
<dubbo:service interface="top.guoj.api.HelloService" ref="helloService" />

启动上面配置的Provider：

[zk: localhost:2181(CONNECTED) 36] ls /
[test2, zookeeper, test1]
[zk: localhost:2181(CONNECTED) 37] ls /test1/top.guoj.api.HelloService
[configurators, providers]
[zk: localhost:2181(CONNECTED) 38] ls /test2/top.guoj.api.HelloService
[configurators, providers]
[zk: localhost:2181(CONNECTED) 39] ls /test1/top.guoj.api.HelloService/providers
[dubbo%3A%2F%2F192.168.100.61%3A20880%2Ftop.guoj.api.HelloService%3Fanyhost%3Dtrue%26application%3Ddemo-provider%26dubbo%3D2.6.2%26generic%3Dfalse%26interface%3Dtop.guoj.api.HelloService%26methods%3DsayHello%26pid%3D7492%26side%3Dprovider%26timestamp%3D1533023167412]
[zk: localhost:2181(CONNECTED) 40] ls /test2/top.guoj.api.HelloService/providers
[dubbo%3A%2F%2F192.168.100.61%3A20880%2Ftop.guoj.api.HelloService%3Fanyhost%3Dtrue%26application%3Ddemo-provider%26dubbo%3D2.6.2%26generic%3Dfalse%26interface%3Dtop.guoj.api.HelloService%26methods%3DsayHello%26pid%3D7492%26side%3Dprovider%26timestamp%3D1533023167412]

客户端

支持zkclient和curator两种客户端实现。从2.2.0起默认使用zkclient。2.3.0后支持curator。

Dubbo注册中心Registry之Multicast

Thu, 02 Aug 2018 01:26:45 +0000

Dubbo的注册中心Registry主要有下面四种方式，官方推荐使用Zookeeper。

Multicast

类似IP地址广播。不需要启动任何中心节点，只要广播地址一样，就可以互相发现。组播受网络结构限制，只适合小规模应用或开发阶段使用。组播地址段: 224.0.0.0 - 239.255.255.255。

Provider启动时，广播它的地址。
Consumer启动时，广播它的订阅请求。
当Provider接收到订阅请求，单播自己的地址给Consumer，若unicast=false ，则使用广播给Consumer。

Dubbo管理控制台

Wed, 01 Aug 2018 01:03:00 +0000

下载代码

git clone https://github.com/apache/incubator-dubbo-ops

Maven打包

cd incubator-dubbo-ops && mvn package

修改配置\BOOT-INF\classes\application.properties

server.port=7001
spring.velocity.cache=false
spring.velocity.charset=UTF-8
spring.velocity.layout-url=/templates/default.vm
spring.messages.fallback-to-system-locale=false
spring.messages.basename=i18n/message
#root用户密码
spring.root.password=root
#guest用户密码
spring.guest.password=guest

运行

最新版已是spring boot应用程序，直接运行jar包即可。

java -jar dubbo-admin/target/dubbo-admin-0.0.1-SNAPSHOT.jar

Dubbo通讯之zookeeper

Mon, 30 Jul 2018 03:35:41 +0000

Zookeeper

zoo.cfg

tickTime=2000
initLimit=10
syncLimit=5
dataDir=/var/data/zookeeper
clientPort=2181

Maven Properties

<properties>
	<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	<dubbo.version>2.6.2</dubbo.version>
	<zookeeper.version>3.4.6</zookeeper.version>
	<curator.version>2.8.0</curator.version>
	<log4j.version>1.2.17</log4j.version>
	<slf4j.version>1.7.2</slf4j.version>
</properties>

Provider

provider.pom

<?xml version="1.0"?>
<project
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"
	xmlns="http://maven.apache.org/POM/4.0.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>top.guoj</groupId>
		<artifactId>dubbo-demo</artifactId>
		<version>0.0.1-SNAPSHOT</version>
	</parent>
	<groupId>top.guoj</groupId>
	<artifactId>dubbo-provider</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>dubbo-provider</name>
	<url>http://maven.apache.org</url>
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	</properties>
	<dependencies>
		<dependency>
			<groupId>com.alibaba</groupId>
			<artifactId>dubbo</artifactId>
			<version>${dubbo.version}</version>
		</dependency>
		<dependency>
			<groupId>top.guoj</groupId>
			<artifactId>dubbo-api</artifactId>
			<version>0.0.1-SNAPSHOT</version>
		</dependency>
		<dependency>
			<groupId>log4j</groupId>
			<artifactId>log4j</artifactId>
			<version>${log4j.version}</version>
			<exclusions>
				<exclusion>
					<groupId>javax.jms</groupId>
					<artifactId>jms</artifactId>
				</exclusion>
				<exclusion>
					<groupId>com.sun.jdmk</groupId>
					<artifactId>jmxtools</artifactId>
				</exclusion>
				<exclusion>
					<groupId>com.sun.jmx</groupId>
					<artifactId>jmxri</artifactId>
				</exclusion>
			</exclusions>
		</dependency>
		<dependency>
			<groupId>org.apache.zookeeper</groupId>
			<artifactId>zookeeper</artifactId>
			<version>${zookeeper.version}</version>
			<exclusions>
				<exclusion>
					<groupId>log4j</groupId>
					<artifactId>log4j</artifactId>
				</exclusion>
				<exclusion>
					<groupId>io.netty</groupId>
					<artifactId>netty</artifactId>
				</exclusion>
			</exclusions>
		</dependency>
		<dependency>
			<groupId>org.slf4j</groupId>
			<artifactId>slf4j-nop</artifactId>
			<version>${slf4j.version}</version>
		</dependency>
		<dependency>
			<groupId>org.apache.curator</groupId>
			<artifactId>curator-framework</artifactId>
			<version>${curator.version}</version>
		</dependency>
		<dependency>
			<groupId>org.apache.curator</groupId>
			<artifactId>curator-recipes</artifactId>
			<version>${curator.version}</version>
		</dependency>
	</dependencies>
</project>

provider.xml

<beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
	xmlns="http://www.springframework.org/schema/beans"
	xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd
       http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">
	<dubbo:application name="demo-provider" />
	<dubbo:registry address="zookeeper://192.168.100.61:2181" />
	<bean id="helloService" class="top.guoj.provider.HelloServiceImpl" />
	<dubbo:service interface="top.guoj.api.HelloService" ref="helloService" />
</beans>

Consumer

consumer.pom

<?xml version="1.0"?>
<project
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"
	xmlns="http://maven.apache.org/POM/4.0.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>top.guoj</groupId>
		<artifactId>dubbo-demo</artifactId>
		<version>0.0.1-SNAPSHOT</version>
	</parent>
	<groupId>top.guoj</groupId>
	<artifactId>dubbo-consumer</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>dubbo-consumer</name>
	<url>http://maven.apache.org</url>
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	</properties>
	<dependencies>
		<dependency>
			<groupId>com.alibaba</groupId>
			<artifactId>dubbo</artifactId>
			<version>${dubbo.version}</version>
		</dependency>
		<dependency>
			<groupId>top.guoj</groupId>
			<artifactId>dubbo-api</artifactId>
			<version>0.0.1-SNAPSHOT</version>
		</dependency>
		<dependency>
			<groupId>log4j</groupId>
			<artifactId>log4j</artifactId>
			<version>${log4j.version}</version>
			<exclusions>
				<exclusion>
					<groupId>javax.jms</groupId>
					<artifactId>jms</artifactId>
				</exclusion>
				<exclusion>
					<groupId>com.sun.jdmk</groupId>
					<artifactId>jmxtools</artifactId>
				</exclusion>
				<exclusion>
					<groupId>com.sun.jmx</groupId>
					<artifactId>jmxri</artifactId>
				</exclusion>
			</exclusions>
		</dependency>
		<dependency>
			<groupId>org.apache.zookeeper</groupId>
			<artifactId>zookeeper</artifactId>
			<version>${zookeeper.version}</version>
			<exclusions>
				<exclusion>
					<groupId>log4j</groupId>
					<artifactId>log4j</artifactId>
				</exclusion>
				<exclusion>
					<groupId>io.netty</groupId>
					<artifactId>netty</artifactId>
				</exclusion>
			</exclusions>
		</dependency>
		<dependency>
			<groupId>org.slf4j</groupId>
			<artifactId>slf4j-nop</artifactId>
			<version>${slf4j.version}</version>
		</dependency>
		<dependency>
			<groupId>org.apache.curator</groupId>
			<artifactId>curator-framework</artifactId>
			<version>${curator.version}</version>
		</dependency>
		<dependency>
			<groupId>org.apache.curator</groupId>
			<artifactId>curator-recipes</artifactId>
			<version>${curator.version}</version>
		</dependency>
	</dependencies>
</project>

consumer.xml

Dubbo之helloword

Thu, 26 Jul 2018 03:24:10 +0000

Dubbo是阿里开源一个分布式服务RPC框架。现已进入apache孵化。

Provider: 服务提供方。
Consumer: 服务消费方。
Registry: 服务注册与发现的注册中心。
Monitor: 统计服务的调用次调和调用时间的监控中心。
Container: 服务运行容器。

dubbo-demo

pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>top.guoj</groupId>
	<artifactId>dubbo-demo</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<packaging>pom</packaging>
	<name>dubbo-demo</name>
	<url>http://maven.apache.org</url>
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	</properties>
	<dependencies>
		<dependency>
			<groupId>junit</groupId>
			<artifactId>junit</artifactId>
			<version>3.8.1</version>
			<scope>test</scope>
		</dependency>
	</dependencies>
	<modules>
		<module>dubbo-api</module>
		<module>dubbo-provider</module>
		<module>dubbo-consumer</module>
	</modules>
</project>

dubbo-api

├─src
│  ├─main
│  │  ├─java
│  │  │  └─top
│  │  │      └─guoj
│  │  │          └─api
│  │  └─resources
│  └─test
│      ├─java
│      └─resources
└─target
    ├─classes
    └─test-classes

HelloService.java

package top.guoj.api;

public interface HelloService {
	String sayHello(String name);
}

pom.xml

<?xml version="1.0"?>
<project
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"
	xmlns="http://maven.apache.org/POM/4.0.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>top.guoj</groupId>
		<artifactId>dubbo-demo</artifactId>
		<version>0.0.1-SNAPSHOT</version>
	</parent>
	<groupId>top.guoj</groupId>
	<artifactId>dubbo-api</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>dubbo-api</name>
	<url>http://maven.apache.org</url>
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	</properties>
	<dependencies>
	</dependencies>
</project>

dubbo-provider

├─src
│  ├─main
│  │  ├─java
│  │  │  └─top
│  │  │      └─guoj
│  │  │          └─provider
│  │  └─resources
│  └─test
│      ├─java
│      └─resources
└─target
    ├─classes
    └─test-classes

HelloServiceImpl.java

package top.guoj.provider;

import top.guoj.api.HelloService;

public class HelloServiceImpl implements HelloService {

	@Override
	public String sayHello(String name) {
		return "hello dubbo";
	}

}

Provider.java

package top.guoj.provider;

import org.springframework.context.support.ClassPathXmlApplicationContext;

public class Provider {

    public static void main(String[] args) throws Exception {
        System.setProperty("java.net.preferIPv4Stack", "true");
        ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(new String[]{"provider.xml"});
        context.start();
        System.out.println("Provider started.");
        System.in.read(); 
    }
}

provider.xml

<beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
	xmlns="http://www.springframework.org/schema/beans"
	xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd
       http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">

	<!-- provider's application name, used for tracing dependency relationship -->
	<dubbo:application name="dubbo-provider" />
	<!-- use multicast registry center to export service -->
	<dubbo:registry address="multicast://224.5.6.7:1234" />
	<!-- use dubbo protocol to export service on port 20880 -->
	<dubbo:protocol name="dubbo" port="20880" />
	<!-- service implementation, as same as regular local bean -->
	<bean id="helloService" class="top.guoj.provider.HelloServiceImpl" />
	<!-- declare the service interface to be exported -->
	<dubbo:service interface="top.guoj.api.HelloService"
		ref="helloService" />
</beans>

pom.xml

<?xml version="1.0"?>
<project
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"
	xmlns="http://maven.apache.org/POM/4.0.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>top.guoj</groupId>
		<artifactId>dubbo-demo</artifactId>
		<version>0.0.1-SNAPSHOT</version>
	</parent>
	<groupId>top.guoj</groupId>
	<artifactId>dubbo-provider</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>dubbo-provider</name>
	<url>http://maven.apache.org</url>
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	</properties>
	<dependencies>
		<dependency>
			<groupId>com.alibaba</groupId>
			<artifactId>dubbo</artifactId>
			<version>2.6.2</version>
		</dependency>
		<dependency>
			<groupId>top.guoj</groupId>
			<artifactId>dubbo-api</artifactId>
			<version>0.0.1-SNAPSHOT</version>
		</dependency>
	</dependencies>
</project>

dubbo-consumer

├─src
│  ├─main
│  │  ├─java
│  │  │  └─top
│  │  │      └─guoj
│  │  │          └─consumer
│  │  └─resources
│  └─test
│      ├─java
│      └─resources
└─target
    ├─classes
    └─test-classes

Consumer.java

package top.guoj.consumer;

import org.springframework.context.support.ClassPathXmlApplicationContext;

import top.guoj.api.HelloService;

public class Consumer {
	public static void main(String[] args) throws Exception {
		ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(
				new String[] { "consumer.xml" });
		context.start();
		// Obtaining a remote service proxy
		HelloService demoService = (HelloService) context.getBean("helloService");
		// Executing remote methods
		String hello = demoService.sayHello("world");
		// Display the call result
		System.out.println(hello);
	}
}

consumer.xml

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:dubbo="http://dubbo.apache.org/schema/dubbo"
	xmlns="http://www.springframework.org/schema/beans"
	xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.3.xsd
       http://dubbo.apache.org/schema/dubbo http://dubbo.apache.org/schema/dubbo/dubbo.xsd">

	<!-- consumer's application name, used for tracing dependency relationship 
		(not a matching criterion), don't set it same as provider -->
	<dubbo:application name="dubbo-consumer" />
	<!-- use multicast registry center to discover service -->
	<dubbo:registry address="multicast://224.5.6.7:1234" />
	<!-- generate proxy for the remote service, then demoService can be used 
		in the same way as the local regular interface -->
	<dubbo:reference id="helloService" check="false"
		interface="top.guoj.api.HelloService" />
</beans>

pom.xml

<?xml version="1.0"?>
<project
	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"
	xmlns="http://maven.apache.org/POM/4.0.0"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<modelVersion>4.0.0</modelVersion>
	<parent>
		<groupId>top.guoj</groupId>
		<artifactId>dubbo-demo</artifactId>
		<version>0.0.1-SNAPSHOT</version>
	</parent>
	<groupId>top.guoj</groupId>
	<artifactId>dubbo-consumer</artifactId>
	<version>0.0.1-SNAPSHOT</version>
	<name>dubbo-consumer</name>
	<url>http://maven.apache.org</url>
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	</properties>
	<dependencies>
		<dependency>
			<groupId>com.alibaba</groupId>
			<artifactId>dubbo</artifactId>
			<version>2.6.2</version>
		</dependency>
		<dependency>
			<groupId>top.guoj</groupId>
			<artifactId>dubbo-api</artifactId>
			<version>0.0.1-SNAPSHOT</version>
		</dependency>
	</dependencies>
</project>

eclipse中搭建springboot helloword

Fri, 06 Jul 2018 00:00:00 +0000

安装sts(Spring Tools)

新建Spring Starter Project

项目结构如下：

application.yml

server:
  port: 8080</pre>

pom.xml

<project xmlns="http://maven.apache.org/POM/4.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.example</groupId>
    <artifactId>demo</artifactId>
    <version>0.0.1-SNAPSHOT</version>
    <packaging>jar</packaging>
    <name>demo</name>
    <description>Demo project for Spring Boot</description>
    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>2.0.2.RELEASE</version>
        <relativePath /> <!-- lookup parent from repository -->
    </parent>
    <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
        <java.version>1.8</java.version>
    </properties>
    <dependencies>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-web</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-test</artifactId>
            <scope>test</scope>
        </dependency>
    </dependencies>
    <build>
        <plugins>
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
            </plugin>
        </plugins>
    </build>
</project>

新建HelloController.java

import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
import org.springframework.web.bind.annotation.RestController;

@RestController
public class HelloController {

	@RequestMapping(value = "/hello", method = RequestMethod.GET)
	public String HelloController() {
		return "Hello World!";
	}

}

运行Run As->Spring Boot App

Cesium之地形

Thu, 05 Jul 2018 01:54:11 +0000

Cesium支持对海洋，湖泊和河流的全球高分辨率地形和水影像进行流式传输和可视化。

支持多种地形provider来接收地形数据，大多数provider使用rest类型的接口来请求地形瓦片。

缺省情况下, 地球是一个 WGS84 椭球体。要添加Cesium的世界地形, 添加下面代码，珠穆朗玛峰显示如下：

viewer.terrainProvider = Cesium.createWorldTerrain();

Cesium世界地形还包括地形照明数据以及水效应所需的海岸线数据。默认情况下, 地形服务器不发送照明或海岸线数据与地形瓦片。在构造 CesiumTerrainProvider 时, 要启用地形照明, 从地形服务器请求 VertexNormals 扩展, 并启用全球照明。开启照明后珠穆朗玛峰显示如下：

Cesium之图像图层

Tue, 03 Jul 2018 15:56:07 +0000

Cesium支持从多种标准服务中绘制和分层高分辨率图像。层可以单独, 并混合在一起。每个层的亮度、对比度、伽玛、色相和饱和度都可以动态改变。

首先通过imageryProvider使用Esri ArcGIS MapServer中的图层:

var viewer = new Cesium.Viewer('cesiumContainer', {
    imageryProvider : new Cesium.ArcGisMapServerImageryProvider({
        url : '//services.arcgisonline.com/ArcGIS/rest/services/World_Street_Map/MapServer'
    }),
    baseLayerPicker : false
});

添加另一个图层：使用NASA Black Marble imagery的 Tile Map Service (TMS):

var layers = viewer.scene.imageryLayers;
var blackMarble = layers.addImageryProvider(new Cesium.createTileMapServiceImageryProvider({
    url : '//cesiumjs.org/tilesets/imagery/blackmarble',
    maximumLevel : 8,
    credit : 'Black Marble imagery courtesy NASA Earth Observatory'
}));

后添加的NASA层覆盖了先添加的Esri层，可以通过blackMarble.alpha使二者融合。

blackMarble.alpha = 0.5; // 0.0 is transparent.  1.0 is opaque.

Cesium之绘制图形

Mon, 02 Jul 2018 06:35:45 +0000

首先通过viewer.entities.add创建了一个entity(坐标定位在北京，根据坐标绘制了一个多边形)，然后通过zoomto确保entity在视图中。

var viewer = new Cesium.Viewer('cesiumContainer');
var beijing = viewer.entities.add({
  name: 'Beijing',
  polygon: {
    hierarchy: Cesium.Cartesian3.fromDegreesArray([
      116.4, 39.9,
      116.38, 39.9,
      116.37, 39.92]),
    height: 0,
    material: Cesium.Color.RED.withAlpha(0.5),
    outline: true,
    outlineColor: Cesium.Color.BLACK
  }
});
viewer.zoomTo(beijing);

运行上面的代码，效果如下：

下面代码，将多边形高度提升到了地球20万米上空。

beijing.polygon.height = 200000;

如果height为undefined,则体积从0开始，下面代码创建从20万米开始并延伸到25万米，就意味着体本身达到5万米。

beijing.polygon.height = 200000;
beijing.polygon.extrudedHeight = 250000;

除了多边形，还有下面这些形状的实体：

Cesium之Viewer

Mon, 02 Jul 2018 03:07:55 +0000

Viewer用于构建应用程序的基本构件。它将所有标准Cesium小部件合成为一个可重用的包。

new Cesium.Viewer(container, options)

参数	类型	说明
container	Element\|String	用于包含viewer组件的DOM对象或者容器ID
options	Object	选项

var viewer = new Cesium.Viewer('cesiumContainer', {
    //Start in Columbus Viewer
    sceneMode : Cesium.SceneMode.SCENE3D, //COLUMBUS_VIEW|MORPHING|SCENE2D|SCENE3D
    animation:true, 
    baseLayerPicker:true,
    fullscreenButton:true,
    geocoder:true,
    homeButton:true,
    infoBox:true,
    selectionIndicator:true,
    timeline:true,
    vrButton:true,
});

成员

Scene ：new Cesium.Scene(options)

虚拟场景中所有3D 图形对象和状态的容器。

var scene = viewer.scene;

var scene = new Cesium.Scene({
  canvas : canvas,
  contextOptions : {
    allowTextureFilterAnisotropic : false
}});

Camera：new Cesium.Camera(scene)

方法

flyto

flyTo(target, options) → Promise.<Boolean>

飞向提供的实体、实体或数据源。如果数据源仍在加载过程中, 或者可视化仍在加载, 则此方法等待数据在执行该飞行之前准备就绪。

capistrano简介

Fri, 29 Jun 2018 06:32:56 +0000

用ruby写的用于远程自动推送部署工具。官网 github

cap install

自动生成部署文件，结构如下:

├── Capfile
├── config
│   ├── deploy
│   │   ├── production.rb
│   │   └── staging.rb
│   └── deploy.rb
├── lib
│   └── capistrano
│   └── tasks
└── log
└── capistrano.log

production.rb、staging.rb对应不同环境的服务器及配置。

cap production deploy

服务器推送后的目录如下：

├── current -> /tmp/stock/releases/20180102061709
├── releases
│   ├── 20171229041438
│   └── 20180102061709
├── repo
├── revisions.log
└── shared

ubuntu无法开机自启动nginx

Fri, 29 Jun 2018 06:32:56 +0000

阿里云到期了涨价，只好申请了降配续费。阿里自动重启服务器后，发现nginx没有开机自启动。

guoj@iZ2ze8wsk0m120dsi7m0juZ:~$ sudo runlevel
N 5

配好好一切后，重启服务器，奇迹并没有发生，nginx还是没有启动。

guoj@iZ2ze8wsk0m120dsi7m0juZ:~$ sudo cat /etc/init.d/nginx 
#!/bin/sh

### BEGIN INIT INFO
# Provides:       nginx
# Required-Start:    $local_fs $remote_fs $network $syslog $named
# Required-Stop:     $local_fs $remote_fs $network $syslog $named
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: starts the nginx web server
# Description:       starts nginx using start-stop-daemon
### END INIT INFO

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/nginx
NAME=nginx
DESC=nginx

# Include nginx defaults if available
if [ -r /etc/default/nginx ]; then
        . /etc/default/nginx
fi

STOP_SCHEDULE="${STOP_SCHEDULE:-QUIT/5/TERM/5/KILL/5}"

test -x $DAEMON || exit 0

. /lib/init/vars.sh
. /lib/lsb/init-functions

# Try to extract nginx pidfile
PID=$(cat /etc/nginx/nginx.conf | grep -Ev '^\s*#' | awk 'BEGIN { RS="[;{}]" } { if ($1 == "pid") print $2 }' | head -n1)
if [ -z "$PID" ]; then
        PID=/run/nginx.pid
fi

if [ -n "$ULIMIT" ]; then
        # Set ulimit if it is set in /etc/default/nginx
        ulimit $ULIMIT
fi

start_nginx() {
        # Start the daemon/service
        #
        # Returns:
        #   0 if daemon has been started
        #   1 if daemon was already running
        #   2 if daemon could not be started
        start-stop-daemon --start --quiet --pidfile $PID --exec $DAEMON --test &gt; /dev/null \
                || return 1
        start-stop-daemon --start --quiet --pidfile $PID --exec $DAEMON -- \
                $DAEMON_OPTS 2&gt;/dev/null \
                || return 2
}

test_config() {
        # Test the nginx configuration
        $DAEMON -t $DAEMON_OPTS &gt;/dev/null 2&gt;&1
}

stop_nginx() {
        # Stops the daemon/service
        #
        # Return
        #   0 if daemon has been stopped
        #   1 if daemon was already stopped
        #   2 if daemon could not be stopped
        #   other if a failure occurred
        start-stop-daemon --stop --quiet --retry=$STOP_SCHEDULE --pidfile $PID --name $NAME
        RETVAL="$?"
        sleep 1
        return "$RETVAL"
}

reload_nginx() {
        # Function that sends a SIGHUP to the daemon/service
        start-stop-daemon --stop --signal HUP --quiet --pidfile $PID --name $NAME
        return 0
}

rotate_logs() {
        # Rotate log files
        start-stop-daemon --stop --signal USR1 --quiet --pidfile $PID --name $NAME
        return 0
}

upgrade_nginx() {
        # Online upgrade nginx executable
        # http://nginx.org/en/docs/control.html
        #
        # Return
        #   0 if nginx has been successfully upgraded
        #   1 if nginx is not running
        #   2 if the pid files were not created on time
        #   3 if the old master could not be killed
        if start-stop-daemon --stop --signal USR2 --quiet --pidfile $PID --name $NAME; then
                # Wait for both old and new master to write their pid file
                while [ ! -s "${PID}.oldbin" ] || [ ! -s "${PID}" ]; do
                        cnt=`expr $cnt + 1`
                        if [ $cnt -gt 10 ]; then
                                return 2
                        fi
                        sleep 1
                done
                # Everything is ready, gracefully stop the old master
                if start-stop-daemon --stop --signal QUIT --quiet --pidfile "${PID}.oldbin" --name $NAME; then
                        return 0
                else
                        return 3
                fi
        else
                return 1
        fi
}

case "$1" in
        start)
                log_daemon_msg "Starting $DESC" "$NAME"
                start_nginx
                case "$?" in
                        0|1) log_end_msg 0 ;;
                        2)   log_end_msg 1 ;;
                esac
                ;;
        stop)
                log_daemon_msg "Stopping $DESC" "$NAME"
                stop_nginx
                case "$?" in
                        0|1) log_end_msg 0 ;;
                        2)   log_end_msg 1 ;;
                esac
                ;;
        restart)
                log_daemon_msg "Restarting $DESC" "$NAME"

                # Check configuration before stopping nginx
                if ! test_config; then
                        log_end_msg 1 # Configuration error
                        exit $?
                fi

                stop_nginx
                case "$?" in
                        0|1)
                                start_nginx
                                case "$?" in
                                        0) log_end_msg 0 ;;
                                        1) log_end_msg 1 ;; # Old process is still running
                                        *) log_end_msg 1 ;; # Failed to start
                                esac
                                ;;
                        *)
                                # Failed to stop
                                log_end_msg 1
                                ;;
                esac
                ;;
        reload|force-reload)
                log_daemon_msg "Reloading $DESC configuration" "$NAME"

                # Check configuration before stopping nginx
                #
                # This is not entirely correct since the on-disk nginx binary
                # may differ from the in-memory one, but that's not common.
                # We prefer to check the configuration and return an error
                # to the administrator.
                if ! test_config; then
                        log_end_msg 1 # Configuration error
                        exit $?
                fi

                reload_nginx
                log_end_msg $?
                ;;
        configtest|testconfig)
                log_daemon_msg "Testing $DESC configuration"
                test_config
                log_end_msg $?
                ;;
        status)
                status_of_proc -p $PID "$DAEMON" "$NAME" && exit 0 || exit $?
                ;;
        upgrade)
                log_daemon_msg "Upgrading binary" "$NAME"
                upgrade_nginx
                log_end_msg $?
                ;;
        rotate)
                log_daemon_msg "Re-opening $DESC log files" "$NAME"
                rotate_logs
                log_end_msg $?
                ;;
        *)
                echo "Usage: $NAME {start|stop|restart|reload|force-reload|status|configtest|rotate|upgrade}" &gt;&2
                exit 3
                ;;
esac

手动启动/etc/init.d/nginx start也是没起来。systemctl start nginx报错如下：

Cesium简介

Thu, 28 Jun 2018 08:17:09 +0000

基于几种新的HTML5技术构建的，其中最重要的是WebGL。
官网
 github
API文档

支持Google Chrome、Firefox、Internet Explorer 11、Opera。

浏览器打开下面页面，查看是否支持：浏览器测试

install node.js。
下载代码并解压后进到根目录。
运行npm install。
运行npm start。（也可运行node server.js或者通过nginx、apache等web服务器加载当前目录）

cesium应用的基础是viewer，创建viewer并绑定在id=“cesiumContainer"的DIV上即可。

关于Ubuntu系统中mysql的用户debian-sys-maint

Thu, 15 Mar 2018 02:11:03 +0000

最近在Ubuntu16上安装nodejs，发生错误如下：

mysql_upgrade: Got error: 1045: Access denied for user ‘debian-sys-maint’@’localhost’ (using password: YES) while connecting to the MySQL server

Do you want to continue? [Y/n] y
Setting up mysql-server-5.7 (5.7.21-0ubuntu0.16.04.1) ...
mysql_upgrade: Got error: 1045: Access denied for user 'debian-sys-maint'@'localhost' (using password: YES) while connecting to the MySQL server
Upgrade process encountered error and will not continue.
mysql_upgrade failed with exit status 11
dpkg: error processing package mysql-server-5.7 (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-5.7; however:
  Package mysql-server-5.7 is not configured yet.

dpkg: error processing package mysql-server (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 mysql-server-5.7
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

这个mysql用户debian-sys-main是个什么鬼？为什么mysql_upgrade会用这个用户连接，而且为什么又会密码不对？

日志文件总管logrotate

Wed, 14 Mar 2018 06:02:59 +0000

logrotate官网

简介

logrotate是个十分有用的工具，它可以自动对日志进行截断、轮循、压缩以及删除旧的日志文件。配置完后，logrotate的运作完全自动化，不必进行任何人为干预。配置文件通常在/etc/logrotate.conf中，独立配置通常在/etc/logrotate.d/下。

配置

/var/log/mysql.log /var/log/mysql/*log {
        daily
        rotate 7
        missingok
        create 640 mysql adm
        compress
        sharedscripts
        postrotate
                test -x /usr/bin/mysqladmin || exit 0
                MYADMIN="/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf"
                if [ -z "`$MYADMIN ping 2&gt;/dev/null`" ]; then
                  if killall -q -s0 -umysql mysqld; then
                    exit 1
                  fi 
                else
                  $MYADMIN flush-logs
                fi
        endscript
}

手动运行

logroute -f /et/logrotate.conf

定时任务

logrotate需要的cron任务应该在安装时就自动创建了：/etc/cron.daily/logrotate

logstash多个配置文件数据混乱问题

Tue, 13 Mar 2018 07:16:54 +0000

程序自始至终只有一个pipline。要想多个pipline，只能通过启动多个logstash实例。
当指定的目录下的所有配置文件启动时，Logstash会自动把多个文件合并在一个文件中。
可以通过cat **.conf > /tmp/tmp.conf查看多个配置文件合并后的效果，排查问题。
假如有个2配置文件，output又指向同一源时，可以拆成3个文件来处理。

input1.conf

input { ....... .}
  filter { 
    if [type] == "1"{ 
       grok { ...........} 
    } 
}

input2.conf

input { ....... .}
  filter { 
    if [type] == "2"{ 
      grok { ...........} 
    } 
}

output.conf

output { 
  ................ 
}

nginx访问频次限制模块

Thu, 08 Mar 2018 02:47:22 +0000

nginx_http_limit_conn_zone模块

用于限制并发连接数，特别是单个IP地址的连接数量。并非所有连接都被计算在内。只有在服务器处理了请求并且已经读取了整个请求头的情况下才计算连接。官方文档

用法

Syntax:limit_conn zone number;
Default:—
Context:http, server, location

实例

http{
	limit_conn_zone $binary_remote_addr zone=addr:10m;
	limit_conn_zone $binary_remote_addr zone=perip:10m;
	limit_conn_zone $server_name zone=perserver:10m;

	server{
		limit_conn perip 50;
		limit_conn perserver 50;
		limit_conn addr 1;
	}
}

说明

$remote_addr变量的大小可以从7到15个字节不等。存储状态在32位平台上占用32或64字节的内存，在64位平台上总是占用64字节。 $binary_remote_addr对于IPv4地址，变量的大小始终为4个字节，对于IPv6地址则为16个字节。存储状态在32位平台上始终占用32或64个字节，在64位平台上占用64个字节。1M字节的区域可以保持大约32000个32字节的状态或大约16000个64字节的状态。

MySQL对包含NULL字段排序

Wed, 07 Mar 2018 02:54:57 +0000

MySQL5.7文档-order

CREATE TABLE `sorted` (
	`id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT,
	`idx` INT(11) UNSIGNED NULL DEFAULT NULL,
	PRIMARY KEY (`id`)
)

INSERT INTO `sorted` (`id`, `idx`) VALUES (1, 2);
INSERT INTO `sorted` (`id`, `idx`) VALUES (2, NULL);
INSERT INTO `sorted` (`id`, `idx`) VALUES (3, 3);
INSERT INTO `sorted` (`id`, `idx`) VALUES (4, 1);
INSERT INTO `sorted` (`id`, `idx`) VALUES (5, 1);
INSERT INTO `sorted` (`id`, `idx`) VALUES (6, 4);
INSERT INTO `sorted` (`id`, `idx`) VALUES (7, 3);
INSERT INTO `sorted` (`id`, `idx`) VALUES (8, NULL);
INSERT INTO `sorted` (`id`, `idx`) VALUES (9, 0);

NULL被视为低于任何非NULL值。

mysql> select * from sorted;
+----+------+
| id | idx  |
+----+------+
|  1 |    2 |
|  2 | NULL |
|  3 |    3 |
|  4 |    1 |
|  5 |    1 |
|  6 |    4 |
|  7 |    3 |
|  8 | NULL |
|  9 |    0 |
+----+------+
9 rows in set (0.00 sec)

方案一：

mysql> select id, idx from sorted order by -idx desc;
+----+------+
| id | idx  |
+----+------+
|  9 |    0 |
|  4 |    1 |
|  5 |    1 |
|  1 |    2 |
|  3 |    3 |
|  7 |    3 |
|  6 |    4 |
|  2 | NULL |
|  8 | NULL |
+----+------+
9 rows in set (0.00 sec)

方案二：

mysql> select id,idx from sorted order by isnull(idx), idx;
+----+------+
| id | idx  |
+----+------+
|  9 |    0 |
|  4 |    1 |
|  5 |    1 |
|  1 |    2 |
|  3 |    3 |
|  7 |    3 |
|  6 |    4 |
|  2 | NULL |
|  8 | NULL |
+----+------+
9 rows in set (0.00 sec)

方案三：

mysql> select id,idx from sorted order by if(isnull(idx), 0, 1) desc, idx;
+----+------+
| id | idx  |
+----+------+
|  9 |    0 |
|  4 |    1 |
|  5 |    1 |
|  1 |    2 |
|  3 |    3 |
|  7 |    3 |
|  6 |    4 |
|  2 | NULL |
|  8 | NULL |
+----+------+
9 rows in set (0.00 sec)

HTTP ETag

Tue, 23 Jan 2018 02:45:47 +0000

Etag全称EntityTags，HTTP1.1中才加入的，Response Header一个属性，用来帮助服务器控制Web端的缓存验证。由服务器端生成，并且随着文件的改变而改变。HTTP规范从未指定生成ETag的方法。

ETag是一个不透明的标识符，由Web服务器根据URL上的资源的特定版本而指定。如果那个URL上的资源内容改变，一个新的不一样的ETag就会被分配。用这种方法使用ETag即类似于指纹，并且他们能够被快速地被比较，以确定两个版本的资源是否相同。ETag的比较只对同一个URL有意义——不同URL上的资源的ETag值可能相同也可能不同，从他们的ETag的比较中无从推断。

浏览器刷新304(Not Modified)和再次请求200(From Cache)结果对比

Mon, 22 Jan 2018 03:11:23 +0000

在做性能测试时，无意中发现一个事情：在一个图片资源已经本地缓存到浏览器并且未过期的情况下，刷新网页和再次请求返回的状态不一致。
以资源ETag=W/“PSA-aj-5xx_WUsSsC"为例：

再次请求：

repsonse=200，直接从从本地缓存中取资源。

Request URL:http://guoj.top/wp-content/uploads/2018/01/QQ%E6%88%AA%E5%9B%BE20180115140217.png
Request Method:GET
Status Code:200 OK (from cache)
Remote Address:47.93.55.78:80

Response Headers
HTTP/1.1 200 OK
Server: nginx/1.13.7
Content-Type: image/png
Content-Length: 8487
Connection: keep-alive
Accept-Ranges: bytes
X-Original-Content-Length: 24343
ETag: W/"PSA-aj-5xx_WUsSsC"
Date: Tue, 16 Jan 2018 08:32:27 GMT
Expires: Wed, 14 Feb 2018 05:59:18 GMT
Cache-Control: max-age=2496410

Request Headers
GET /wp-content/uploads/2018/01/QQ%E6%88%AA%E5%9B%BE20180115140217.png HTTP/1.1
Host: guoj.top
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.104 Safari/537.36 Core/1.53.4295.400 QQBrowser/9.7.12661.400
Accept: image/webp,image/*,*/*;q=0.8
Referer: http://guoj.top/
Accept-Encoding: gzip, deflate, sdch
Accept-Language: zh-CN,zh;q=0.8
Cookie: Hm_lvt_624adbfe276a5668e7b4779815c5ff38=1513561518; Hm_lvt_7e91fd8ec5e72f05612cc7e567977104=1513561518; wordpress_test_cookie=WP+Cookie+check; wordpress_logged_in_50ac8821fe935de01bdede6b95928a78=dong4stop%7C1516241303%7CRg3hAvZn7NOjg2mST5JurlQ55m4pDmbTzuiMGDygRfn%7Ccb8c3ee4f27ffba3171f763e4df91e2bb1514bfb5167a8af59a20cbc2dac74ec; wp-settings-1=editor%3Dtinymce%26libraryContent%3Dbrowse%26mfold%3Do%26editor_expand%3Don%26hidetb%3D1%26post_dfw%3Doff%26widgets_access%3Doff%26advImgDetails%3Dshow; wp-settings-time-1=1516087140; _GPSLSC=qEFEXaHVp1!Yd4ct0hstK!DAGQ2tgLU_

刷新网页

不同浏览器的效果不一样，又或者做了特别的设置造成。chrome会返回200(From Cache)。qqbrowser会返回304(Not Modified)。
这是因为qqbrowser刷新网页时在Request Header中加入了：
Cache-Control:max-age=0
If-None-Match:W/“PSA-aj-5xx_WUsSsC”;

ansible简介

Thu, 18 Jan 2018 01:25:03 +0000

Ansible 是一个基于 Python 的自动化运维的工具，无需安装服务端和客户端，只需要有ssh即可，而且使用简单。同类的产品Puppet、Chef、SaltStack都是基于服务端+客户端的模式。官方称之为 “Ansible is Simple IT Automation”。

官网 github

安装

sudo apt-get install software-properties-common
sudo apt-add-repository ppa:ansible/ansible
sudo apt-get update
sudo apt-get install ansible

命令应用基础

ansible [-f forks] [-m module_name] [-a args]

-f forks：启动的并发线程数

-m module_name: 要使用的模块

-a args: 模块特有的参数

ansible-doc -l 查看所有模块

ansible-doc -s MODULE_NAME 查看指定模块的详细帮助

nginx模块ngx_pagespeed配置

Tue, 16 Jan 2018 03:04:36 +0000

官方文档性能测试

http{
        # 启用ngx_pagespeed
        pagespeed on;

        pagespeed Statistics on;
        pagespeed StatisticsLogging on;
        pagespeed LogDir /var/log/pagespeed;
        pagespeed FileCachePath /tmp/cache/ngx_pagespeed_cache;
        # 隐藏pagespeed版本信息
        pagespeed XHeaderValue "Powered By ngx_pagespeed";
        # google字体直接写入html 目的是减少浏览器请求和DNS查询 
        pagespeed EnableFilters inline_google_font_css;
        pagespeed RewriteLevel PassThrough;
        # 改善资源的可缓存性
        pagespeed EnableFilters extend_cache;
        # 预解析DNS查询 
        pagespeed EnableFilters insert_dns_prefetch;

        pagespeed EnableFilters local_storage_cache;
        # 删除无用的url前缀 
        pagespeed EnableFilters trim_urls;
        # 合并head
        pagespeed EnableFilters combine_heads;
        # 移除多余html标签
        pagespeed EnableFilters elide_attributes;
        # 移除html空白
        pagespeed EnableFilters collapse_whitespace;
        # 移除html注释
        pagespeed EnableFilters remove_comments;
        # 移除html属性中的不必要的引号
        pagespeed EnableFilters remove_quotes;

        # css
        # 合并css 
        pagespeed EnableFilters combine_css;
        # 压缩css 
        pagespeed EnableFilters rewrite_css;
        # 将css内容移动到script之前，优先于script渲染
        pagespeed EnableFilters move_css_above_scripts;
        pagespeed EnableFilters move_css_to_head;
        # 重写CSS，首先加载渲染页面的CSS规则 
        pagespeed EnableFilters prioritize_critical_css;
        pagespeed EnableFilters flatten_css_imports;
        pagespeed CssFlattenMaxBytes 5120;

        # js
        # 合并js
        pagespeed EnableFilters combine_javascript;
        # 压缩js
        pagespeed EnableFilters rewrite_javascript;
        pagespeed EnableFilters defer_javascript;
        # 将小的js文件已内联方式引入，避免http请求
        pagespeed EnableFilters inline_javascript;


        # image
        # 延时加载客户端看不见的图片
        pagespeed EnableFilters lazyload_images;
        # 压缩图片
        pagespeed EnableFilters rewrite_images;
        # 将小图片的http调用转成内联方式调用
        pagespeed EnableFilters inline_images;
        pagespeed EnableFilters inline_preview_images;
        # 自动将多张背景图片合并成一张图片。
        pagespeed EnableFilters sprite_images;
        pagespeed EnableFilters dedup_inlined_images;
        pagespeed EnableFilters responsive_images_zoom;
        # 移动端图片自适应重置
        pagespeed EnableFilters resize_mobile_images;

        include /etc/nginx/conf.d/*.conf;
        include /etc/nginx/sites-enabled/*;
}

Linux-PAM模块简介

Mon, 15 Jan 2018 07:45:54 +0000

Linux-PAM工程的目的就是分离应用软件和验证机制的开发。通过验证函数库可以实现上述目的，一个应用程序可以使用这些函数库去进行用户的认证。

模块pam_*.so以动态可加载目标文件(使用dloptn(3)函数打开)的形式保存在 /lib/security、 /lib64/security、/lib/x86_64-linux-gnu/security/等。

配置文件：

/etc/pam.conf
/etc/pam.d/
/etc/security/*（其他PAM环境的配置文件）。以/etc/pam.d/sudo配置为例： [table id=3 /]

验证类型	控制标记	模块路径	模块参数
session	required	pam_env.so	readenv=1 envfile=/etc/default/locale user_readenv=0

Capistrano v3 软链接

Fri, 05 Jan 2018 01:48:51 +0000

本地、测试、生产环境的不同，可能需要不同的配置文件。为了避免每次推送版本都修改配置文件，可以事先将配置文件放置在服务器端，推送完版本后通过软链接指向即可。
通过linked_files、linked_dirs可以将文件、目录链接到shared目录下的文件、目录。
例如：

shared的目录结构

shared/
  
├── conf 
│   ├── database.conf 
│   └── global.conf 
├── main.conf
└── resources

配置文件

append :linked_files, "main.conf"
append :linked_dirs, "conf", "resources"

推送版本的目录结构

注意：目录链接会导致原有目录下的文件丢失

├── conf -> /tmp/stock/shared/conf
├── main.conf -> /tmp/stock/shared/main.conf
├── README.md
├── resources -> /tmp/stock/shared/resources
└── REVISION

Capistrano v3修改部署后文件目录权限

Thu, 04 Jan 2018 01:00:59 +0000

在部署完项目后，可能会需要对部署好的项目文件和目录做一些权限上的更改。可以，通过下面两种方式的任务完成。其它，个性要求同理。

注意：capistrano v2中的latest_release，在capistrano v3已变更为release_path

namespace :permission do
    desc "permission update"
    task :update do
        on roles(:app), in: :sequence, wait: 5 do
            execute :echo, "hello"
            execute :chown, "-R www:www #{release_path}"
	    execute :chmod, "-R 755 #{release_path}"
        end
    end
end

namespace :deploy do
    after :finishing, "permission:update"
end

或者

namespace :permission do
    desc "permission update"
    task :update do
        on roles(:all), in: :sequence, wait: 5 do
            execute :echo, "change start"
            within release_path  do
                 execute :chown, "-R www:www *"
				 execute :chmod, "-R 755 #{release_path}"
            end
        end
    end
end

namespace :deploy do
    after :finishing, "permission:update"
end

Capistrano v3推送指定版本

Wed, 03 Jan 2018 01:36:22 +0000

capistrano v3使用属性branch控制版本信息，默认值是:master。实际中，经常需要根据测试、生成环境发布不同的版本。

修改deploy.rb

set :branch, ENV["REVISION"] || ENV["BRANCH_NAME"] || "master"

或者

set :branch, ENV.fetch("REVISION", "master")

推送v1.0版本则运行：

REVISION=v1.0 cap production deploy

推送master则运行：

cap production deploy

gogs后台守护运行

Tue, 02 Jan 2018 01:37:06 +0000

后台脚本在%GOGS_HOME%/scripts目录下，已经包含了各个系统的脚本，只需要稍微修改即可添加到自启动。

root@iZ2ze9hvf7pey4vrxv9r8gZ:/usr/local/gogs# tree scripts/
scripts/
├── autoboot.sh
├── build_freebsd.sh
├── build_linux64.sh
├── build.sh
├── init
│   ├── centos
│   │   └── gogs
│   ├── debian
│   │   └── gogs
│   ├── freebsd
│   │   └── gogs
│   ├── gentoo
│   │   └── gogs
│   ├── openbsd
│   │   └── gogs
│   └── suse
│       └── gogs
├── launchd
│   └── io.gogs.web.plist
├── mysql.sql
├── README
├── supervisor
│   └── gogs
├── systemd
│   └── gogs.service
└── windows
    └── install-as-service.bat

以Ubuntu16、gogs-v0.11.34.1122为例：

复制脚本并赋予执行权限

cp scripts/init/debian/gogs /etc/init.d/
chmod +x /etc/init.d/gogs

cp scripts/systemd/gogs.service /lib/systemd/system/
chmod +x /lib/systemd/system/gogs.service

修改配置

/etc/init.d/gogs /lib/systemd/system/gogs.service

ansible git模块

Wed, 27 Dec 2017 07:02:46 +0000

git模块文档

ansible 127.0.0.1 -m git -a "repo='https://github.com/ansible/ansible.git' dest='/tmp/ansible'"

通过用户名和密码拉取git代码

---
- hosts: all 
  gather_facts: no
  become: yes
  tasks:
    - name: install git package
      apt:
        name: git

    - name: Get updated files from git repository 
      git: 
        repo: "http://{{ githubuser | urlencode }}:{{ githubpassword | urlencode }}@github.com/dong4stop/hello.git"
        dest: /tmp/git
        version: v1.0

若密码中有特殊字符可以加上urlencode，{{ githubpassword | urlencode }}。

ansible-playbook git.yml -e "githubuser=*\*\\*\*"; -e "githubpassword=\*\**";

nginx与php-fpm权限不一致问题

Thu, 14 Dec 2017 05:42:22 +0000

在使用wordpress时，发现一些目录及文件读写权限的问题。
目录已设置为755权限。
检查后，发现是nginx与php-fpm使用的用户和用户组不一致导致的。

PHP-FPM用户和用户组

vi /etc/php/5.6/fpm/pool.d/www.conf

/etc/init.d/php5.6-fpm restart

Nginx用户和用户组

vi /etc/nginx/nginx.conf

nginx -t
nginx -s reload

nginx模块pagespeed安装

Thu, 14 Dec 2017 02:01:21 +0000

下载PageSpeed模块

下载pagespeed和psol：

https://github.com/pagespeed/ngx_pagespeed/archive/v[PageSpeed版本].zip

https://dl.google.com/dl/page-speed/psol/[PageSpeed版本]-x[系统位数].tar.gz

比如PageSpeed版本1.13.35.1-beta，相应的下载地址则为：
https://codeload.github.com/pagespeed/ngx_pagespeed/zip/v1.13.35.1-beta
https://dl.google.com/dl/page-speed/psol/1.13.35.1-x64.tar.gz

wget https://codeload.github.com/pagespeed/ngx_pagespeed/zip/v1.13.35.1-beta -O ngx_pagespeed-v1.13.35.1-beta.zip
unzip ngx_pagespeed-v1.13.35.1-beta.zip
cd ngx_pagespeed-v1.13.35.1-beta/
wget https://dl.google.com/dl/page-speed/psol/1.13.35.1-x64.tar.gz -O psol-1.13.35.1-x64.tar.gz
tar -xzvf psol-1.13.35.1-x64.tar.gz

下载Nginx

wget http://nginx.org/download/nginx-1.13.7.tar.gz
tar -xvzf nginx-1.13.7.tar.gz
cd nginx-1.13.7/

编译安装

./configure --add-module=/root/ngx_pagespeed-1.13.35.1-beta/ \
--with-cc-opt='-g -O2 -fPIE -fstack-protector-strong \
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' \
--with-ld-opt='-Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now' \
--prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf \
--http-log-path=/var/log/nginx/access.log \
--error-log-path=/var/log/nginx/error.log \
--lock-path=/var/lock/nginx.lock \
--pid-path=/run/nginx.pid \
--http-client-body-temp-path=/var/lib/nginx/body \
--http-fastcgi-temp-path=/var/lib/nginx/fastcgi \
--http-proxy-temp-path=/var/lib/nginx/proxy \
--http-scgi-temp-path=/var/lib/nginx/scgi \
--http-uwsgi-temp-path=/var/lib/nginx/uwsgi \
--with-debug \
--with-pcre-jit \
--with-http_ssl_module \
--with-http_stub_status_module \
--with-http_realip_module \
--with-http_auth_request_module \
--with-http_addition_module \
--with-http_dav_module \
--with-http_geoip_module \
--with-http_gunzip_module \
--with-http_gzip_static_module \
--with-http_image_filter_module \
--with-http_v2_module \
--with-http_sub_module \
--with-http_xslt_module \
--with-stream \
--with-stream_ssl_module \
--with-mail \
--with-mail_ssl_module \
--with-threads

make
make install

测试

对Elasticsearch的Text字段分组查询

Wed, 06 Dec 2017 06:58:20 +0000

官方文档

ES默认不支持Text类型字段进行分组查询，将fielddata设置为true。

curl -XPUT '172.16.88.100:9200/capture-2017.06.19/_mapping/capture' -d'
{
  "properties": {
    "host": {
      "type": "text",
      "fielddata": true
    }
  }
}'

一道题说明java初始化顺序

Tue, 05 Dec 2017 06:48:48 +0000

之前，在公司内部给大家做了java培训后，要考一考大家，关于初始化方面，想了一个综合涵盖继承、静态等各个方面的代码。

题目

说出下面程序运行结果：

class Language {

	static {
		System.out.println("language static block");
	}

	{
		System.out.println("language block");
	}

	public Language() {
		System.out.println("language constructor");
	}

	public Language(String name) {
		System.out.println(name);
	}

}

public class Python extends Language {

	private String name;

	public Python(String name) {
		this.name = name;
		System.out.println("python constructor");
		System.out.println(this.name);
	}

	{
		System.out.println("python block");
	}

	static {
		System.out.println("python static block");
	}

	public static void main(String[] args) {
		new Python("hello python");
	}

答案

language static block
python static block
language block
language constructor
python block
python constructor
hello python

grok解析syslog异常_grokparsefailure

Tue, 05 Dec 2017 06:06:30 +0000

logstash的异常信息并不像elastichsearch那样可以打印出详细的java堆栈错误，方便出错后排查问题。

在使用logstash中遇到_grokparsefailure，实在是太难调试，只能一点点去试、去分析。

之前在解析一个标准的syslog日志竟然也出错。用的官方的标准的pattern。

下面这行日志grok解析失败了：

从官方模版中的正则可以看出对于HOSTNAME的解析不支持"_";。

SYSLOGHOST %{IPORHOST}
IPORHOST (?:%{HOSTNAME}|%{IP})
HOSTNAME \b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(\.?|\b)

找到问题，解决就容易了，要么改主机名要么不用官方的pattern。

Logstash简介

Tue, 05 Dec 2017 02:43:59 +0000

官方文档
Logstash是一个接收，处理，转发日志的工具。包含input、filter、output三大组件。分别实现收集->过滤->输出三个功能。
每个组件下面都包含丰富的插件，下图列举一些常见的。

intput

主要负责从数据源接收数据。常见的如：

file：从文件系统中读取一个文件，类似UNIX命令"tail -0a"。
syslog：监听514端口，按照RFC3164标准解析日志数据。
redis：从redis服务器读取数据，支持channel(发布订阅)和list模式。redis一般在Logstash消费集群中作为"broker"角色，保存events队列共Logstash消费。

filter

主要承担对接收的数据解析、过滤。常用的有：

ONLY_FULL_GROUP_BY

Wed, 22 Nov 2017 06:42:11 +0000

单机启动多个MySQL实例

Wed, 22 Nov 2017 06:42:11 +0000

一：利用mysql_install_db生成数据库

mysql_install_db --datadir=/var/db/my3307/data --user=mysql
mysql_install_db --datadir=/var/db/my3308/data --user=mysql

二：配置文件

vi /etc/my_multi.conf

[mysqld_multi]
[mysqld3307] 
server-id = 3307
datadir  = /var/db/my3307/data
socket = /var/db/my3307/mysql.sock
pid-file  = /var/db/my3307/mysqld.pid
log-bin	= /var/db/my3307/logs/mysql-bin.log
log-error = /var/db/my3307/logs/mysqld.log

[mysqld3308]
server-id = 3308
datadir   = /var/db/my3308/data
socket    = /var/db/my3308/mysql.sock
pid-file  = /var/db/my3308/mysqld.pid
log-bin   = /var/db/my3308/logs/mysql-bin.log
log-error = /var/db/my3308/logs/mysqld.log

三：启动

/usr/local/bin/mysqld_multi --defaults-extra-file=/etc/my_multi.cnf stop|start|report

遇到的问题：

FATAL ERROR: Could not find ./bin/my_print_defaults If you compiled from source, you need to run make install to copy the software into the correct location ready for operation. If you are using a binary release, you must either be at the top level of the extracted archive, or pass the basedir option

解决方案：

在/usr/local下执行或者指定basedir。

/usr/local/bin/mysql_install_db
--user=mysql
--basedir=/usr/local
--datadir=/var/db/my3307/data
--defaults-file=/etc/my.cnf

通过nginx去掉codeIgniter框架的URL中的/index.php/

Wed, 22 Nov 2017 02:19:16 +0000

.htaccess为空

不需要再做rewrite处理。

CI配置

application/config/config.php

$config['uri_protocol'] = 'REQUEST_URI';

nginx配置

server {
    listen 80;
    server_name 127.0.0.1;
    root /usr/local/******;
    index index.php index.html index.htm;
    rewrite_log on;

    location / {
        root /usr/local/******;
        index index.php index.html index.htm;
        try_files $uri $uri//index.php?$query_string;
    }

    location~\.php($ | /) {
        fastcgi_pass 127.0.0.1:9000;
        fastcgi_index index.php;
        fastcgi_split_path_info ^ (.+\.php)(.*) $;
        fastcgi_param PATH_INFO $fastcgi_path_info;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }
    
    location~/\.ht {
        deny all;
    }
}