luci-app-shadowsocksr - OpenWrt/LEDE LuCI for ShadowsocksR-libev

  •        726

本软件包是 shadowsocksr-libev 的 LuCI 控制界面, 方便用户控制和使用「透明代理」「SOCKS5 代理」「端口转发」功能. 软件包的正常使用需要依赖 iptables 和 ipset. 软件包不显式依赖 shadowsocksr-libev, 会根据用户添加的可执行文件启用相应的功能. GFW-List模式 正常使用需要依赖 dnsmasq-extra, 其中包括DNS防污染和GFW-List 可执行文件可通过安装 openwrt-shadowsocksr 中提供的 shadowsocksr-libev 获得. 只有当文件存在时, 相应的功能才可被使用, 并显示相应的 LuCI 设置界面.

https://github.com/chenhw2/luci-app-shadowsocksr

Tags
Implementation
License
Platform

   




Related Projects

luci-app-shadowsocks - OpenWrt/LEDE LuCI for Shadowsocks-libev

  •    Shell

本软件包是 shadowsocks-libev 的 LuCI 控制界面, 方便用户控制和使用「透明代理」「SOCKS5 代理」「端口转发」功能. 软件包的正常使用需要依赖 iptables 和 ipset. 软件包不显式依赖 shadowsocks-libev, 会根据用户添加的可执行文件启用相应的功能. 可执行文件可通过安装 openwrt-shadowsocks 中提供的 shadowsocks-libev 获得. 只有当文件存在时, 相应的功能才可被使用, 并显示相应的 LuCI 设置界面.

luci - LuCI - OpenWrt Configuration Interface

  •    Lua

This is the OpenWrt "luci"-feed containing LuCI - OpenWrt Configuration Interface. You can browse the generated API documentation directly on Github.

luci

  •    Perl

Luci is an accessibility tool (html parser written in Perl) designed to provide users with a text-only experience of a web site. Inspired by the Betsie project, Luci offers features such as ssl, cookies, frames, 401 authorization (ie. htaccess), etc...

openwrt-dist-luci - LuCI Applications of OpenWrt-dist

  •    C

LuCI Applications of OpenWrt-dist


ssr-backup - ShadowsocksR backups

  •    

ShadowsocksR backups

shadowsocksr

  •    Python

A fast tunnel proxy that helps you bypass firewalls. Check all the options via -h.

open-event-android - Open Event Android App Generator https://github

  •    Java

The Open Event Android project consists of two components. The App Generator is a web application that is hosted on a server and generates an event Android app from a zip with JSON and binary files (examples here) or through an API. The second component we are developing in the project is a generic Android app - the output of the app generator. The mobile app can be installed on any Android device for browsing information about the event. Updates can be made automatically through API endpoint connections from an online source (e.g. server), which needs to defined in the provided event zip with the JSON files. The Android app has a standard configuration file, that sets the details of the app (e.g. color scheme, logo of event, link to JSON app data). A) A standard configuration file, that sets the details of the app (e.g. color scheme, logo of event, link to JSON app data). A sample of the JSON format is maintained in the Open Event Repository.

open-event-droidgen - Open Event Android App Generator https://github

  •    Java

The Open Event Android project consists of two components. The App Generator is a web application that is hosted on a server and generates an event Android app from a zip with JSON and binary files (examples here) or through an API. The second component we are developing in the project is a generic Android app - the output of the app generator. The mobile app can be installed on any Android device for browsing information about the event. Updates can be made automatically through API endpoint connections from an online source (e.g. server), which needs to defined in the provided event zip with the JSON files. The Android app has a standard configuration file, that sets the details of the app (e.g. color scheme, the logo of an event, link to JSON app data). A) A standard configuration file, that sets the details of the app (e.g. color scheme, the logo of an event, link to JSON app data). A sample of the JSON format is maintained in the Open Event Repository.

PixPic - PixPic, a Photo Editing App

  •    Swift

What's the best way to teach interns how to write an iOS app? Just let them do it! This app is the result of our interns’ collaboration. This app was created for educational purposes and we used all our common practices just like we do when creating commercial apps. Read more about AGILE on our blog. We followed gitflow approach and merge requests in order to check the code. This approach let our senior developers share their valuable expertise with interns. Delivering builds for testing was automated through Continuous Integration Server. One of our mentors pretended to be a customer who came to us with an idea for an app. While we were working on the app, he regularly received new builds - in time and after each sprint. Guys went the whole way from an idea and basic design concept to generating provisioning profiles and certificates and deploying the final build to iTunes Connect. Here’s where you can check out the app itself.

in-app-purchase - A Node.js module for in-App-Purchase for iOS, Android, Amazon and Windows.

  •    Javascript

A node.js module for in-app purchase (in-app billing) and subscription for Apple, Google Play, Amazon Store, Roku, and Windows. NOTE Unity receipt supports the following: Apple, Google Play, and Amazon.

dokku-letsencrypt - BETA: Automatic Let's Encrypt TLS Certificate installation for dokku

  •    Shell

dokku-letsencrypt is the official plugin for dokku that gives the ability to automatically retrieve and install TLS certificates from letsencrypt.org. During ACME validation, your app will stay available at any time.Note: Your app must already be deployed and accessible in the browser in order to add letsencrypt to your app. Your app just being created is not enough. If you need to, add a temporary certificate to your app prior to adding letsencrypt by running dokku certs:generate <app> DOMAIN to make your app accessible.

create-dmg - Create a good-looking DMG for your macOS app in seconds

  •    Javascript

Imagine you have finished a macOS app, exported it from Xcode, and now want to distribute it to users. The most common way of distributing an app outside the Mac App Store is by putting it in a .dmg file. These are hard to create, especially good-looking ones. You can either pay for a GUI app where you have to customize an existing design or you can run some homebrewed Bash script and you still have to design it. This tool does everything for you, so you can play with your 🐈 instead.Discuss it on Product Hunt and Twitter.

InAppSettingsKit - This iOS framework allows settings to be in-app in addition to or instead of being in the Settings app

  •    Objective-C

InAppSettingsKit (IASK) is an open source solution to easily add in-app settings to your iPhone apps. Normally iOS apps use the Settings.bundle resource to make app's settings to be present in "Settings" app. InAppSettingsKit takes advantage of the same bundle and allows you to present the same settings screen within your app. So the user has the choice where to change the settings. More details about the history of this development on the FutureTap Blog and the Edovia Blog. To support traditional Settings.app panes, the app must include a Settings.bundle with at least a Root.plist to specify the connection of settings UI elements with NSUserDefaults keys. InAppSettingsKit basically just uses the same Settings.bundle to do its work. This means there's no additional work when you want to include a new settings parameter. It just has to be added to the Settings.bundle and it will appear both in-app and in Settings.app. All settings types like text fields, sliders, toggle elements, child views etc. are supported.

InjectionIII - Re-write of Injection for Xcode in (mostly) Swift4

  •    Objective-C

This start-over implementation on Injection for Xcode has been built into an app: InjectionIII.app included in the repo which runs in the status bar. Code injection allows you to update the implementation of methods of a class incrementally in the iOS simulator without having to rebuild or restart your application saving developer time. You can avoid the complications of code signing by using the pre-built binary which is available to download here. For some reason you may need to take the app out of qurantine manually or it will report it as damaged when you run it: xattr -d com.apple.quarantine ~/Downloads/InjectionIII.app. To use, copy/link it to /Applications and run the app. Injection also expects to find your current Xcode at path /Appplications/Xcode.app. Injection no longer requires you to change your project as for iOS is always available if you use the "Start Injection" menu (or type control-=) each time you start your app. Once injection is connected, a file watcher is started in the InjectionIII app and whenever you save a Swift or Objective-C source the target app is messaged to update the implementation. The file watcher can be disabled & enabled while the app is running using the status bar menu. If you inject a subclass of XCTest it will try running that individual test inside your application. When you run your application without rebuilding (^⌘R), recent injections will be re-applied.