frp

0x01 简介 为什么需要内网穿透? 很多时候从公网访问自己内网的设备是困难的，毕竟自己没有一个独立的IP地址。 Frp 服务器进行内网穿透，速度快还十分简单。可以实现很多功能，包括不限于远程桌面，文件共享等。 什么是内网穿透 使内网的服务器，或者防火墙内的机器，对外提供服务。 原理图，来自参考文章 0x02 环境及安装 centos7 (本地) 192.168.30.100 kali 服务器端（自己的vps）192.168.30.128 本机 ubuntu 18.10 2.0 下载 下载程序arch 如果输出是x86_64 则下载linux_amd64那个压缩包 本文是x86_64(绝大多数人都是这个)。 mkdir frp &cd frp wget https://github.com/fatedier/frp/releases/download/v0.29.0/frp_0.29.0_linux_amd64.tar.gz tar -zxvf frp_0.29.0_linux_amd64.tar.gz # 更改下文件名 mv frp_0.29.0_linux_amd64 frp cd frp # 确保frp具有可执行权限 chmod +x frps 运行 ./frps --help 没问题即可开始配置服务端 若提示-bash: ./frps: cannot execute

I'm just starting to look into the world of Functional Reactive Programming in Haskell, and I would like to experiment with GUI programming (with gtk, because of substantial binding) in a reactional setting. Now, I've been looking a bit at Grapefruit, Reactive-Banana and Buster, and I would like any testament to the joy/horror of using any one or other package. All I have is these preliminary oppinions: I don't mind doing some of the binding of the FRP package to gtk myself, as I have an ambivalet feeling about the abstracted backend idea (that Grapefruit has).. While I find type theory

I'm using ReactiveCocoa signals to represent calls to RESTful backend in our system. Each RESTful invocation should receive a token as one of the parameters. The token itself is received from authentication API call. All works fine and we're now introduced token expiration, so the backend access class may need to reauthorize itself if the API call fails with HTTP code 403. I want to make this operation completely transparent for the callers, this is the best I came up with: - (RACSignal *)apiCallWithSession:(Session *)session base:(NSString *)base params:(NSDictionary *)params get:(BOOL)get {

I tried the following without success. The equivalent using -subscribeNext: works as expected. // A [[_viewModel.loginCommand.executionSignals flatten] subscribeCompleted:^{ NSLog(@"A"); }]; My only working implementation is as follows: // B [_viewModel.loginCommand.executionSignals subscribeNext:^(RACSignal *loginSignal) { [loginSignal subscribeCompleted:^{ NSLog(@"B"); }]; }]; Why doesn't -flatten work in "A", and how I can I rewrite "B" to not use a nested subscription? The -flatten operator returns a signal that completes only when all of the inner signals have completed, which requires

I'm learning Haskell, and trying to write some event-driven programs. The following code is from the tutorial: http://www.haskell.org/haskellwiki/OpenGLTutorial2 main = do (progname,_) <- getArgsAndInitialize initialDisplayMode $= [DoubleBuffered] createWindow "Hello World" reshapeCallback $= Just reshape angle <- newIORef (0.0::GLfloat) -- 1 delta <- newIORef (0.1::GLfloat) -- 2 position <- newIORef (0.0::GLfloat, 0.0) -- 3 keyboardMouseCallback $= Just (keyboardMouse delta position) idleCallback $= Just (idle angle delta) displayCallback $= (display angle position) mainLoop The states are

I have been experimenting with RxJS for two weeks now, and although I love it in principle I just cannot seem to find and implement the correct pattern for managing state. All articles and questions appear to agree: Subject should be avoided where possible in favor of just pushing state through via transformations; .getValue() should be deprecated entirely; and .do should perhaps be avoided except for DOM manipulation? The problem with all such suggestions is that none of the literature appears to directly say what you should be using instead, besides "you'll learn the Rx way and stop using

　只有信用卡大小的它，同时也是一台功能完备的电脑(树莓派),把内网能玩的功能都玩了个遍，自然就有了外网访问这台树莓派的需求。一样也是查阅了无数文章，研究了无数个方案，最终试验成功用FRP实现了内网穿透，实现在外网访问家里的这台raspbian系统。 下载 接下来到GitHub上下载frp的发行版本（https://github.com/fatedier/frp/releases）。下载时看好对应的平台。ECS对应的是linux_amd64，树莓派对应的是linux_arm（最好别下arm64位的……）。 然后解压： 来源： https://www.cnblogs.com/lwlq/p/11546668.html

In recent implementations of Classic FRP, for instance reactive-banana, there are event streams and signals, which are step functions (reactive-banana calls them behaviours but they are nevertheless step functions). I've noticed that Elm only uses signals, and doesn't differentiate between signals and event streams. Also, reactive-banana allows to go from event streams to signals (edited: and it's sort of possible to act on behaviours using reactimate' although it not considered good practice), which kind of means that in theory we could apply all the event stream combinators on signals

I've been hearing a lot about functional reactive programming, and decided to check out what the big deal is. Going through the bacon.js documentation, it seems that the main difference is that instead of setting an event listener on a component, I create an event stream on it, and pass the event handler into the stream instead. In other words, all I really did was move the event handler from the component to the event stream. Is that it? If so, what's the big advantage of doing this? Bergi Is that it? No. It's about having event streams. You still will attach listener to them in the end to