I would choose Electron or NW.js.
they are based on Nodejs, let the development process easy as long as you have some knowledge of HTML/CSS/JavaScript.
However they don't support all of the native system features.
We (in China) use VPN software everyday to get access to most of the website (FB/Google/Twitter/IG/Slack, etc).
It's illegal to sell VPN service without government permission, but no one will catch you if you are a user.
Almost all the Chinese business accept mobile payments, if you do care about privacy, you should prepare enough RMBs.
Nginx has widely used modules, business logic can be run in the same worker process with proxy. And it is easy to find enough developers to develop a relatively complex business support system based on nginx module system.
Haproxy itself is efficient as a proxy, however, developing a business system requires a lot of interaction between proxy and the business control processes.
Hi guys,
Make end users evaluate the product as early as possible, that's the methodology.
Maybe what you have seen today is an pre-alpha version of the github recommendation product, they will gather your comments and decide what to create.
- The feed design is poor, I don't like the alway black bold font for every repo name, but they keep blue font for branch name.
In my experience, website monitoring can be started from these several aspects:
- network transfer layer. Monitor each other from difference IDCs - for clouds, I mean geo-regions.
- api. Introduce some monitoring providers, ensure basic api work correct and performance at acceptable level.
- client side, real use measurement(RUM). Monitor the most importance elements of the page, with some javascripts to measure and collect performance metrics.
For example, for the front-page of a site, do:
1. ping the domain/ip from several host at different regions.
2. api status check from 3rd party.
3. on page javascript, measure 'onload' time, and send to your monitor backend.
If you have anything more, can touch me via twitter