Search Results for "app-release.apk"

The spatie/laravel-activitylog package provides easy-to-use functions to log the activities of the users of your app. It can also automatically log model events. All activity will be stored in the activity_log table. Open source software is used in all projects we deliver. Laravel, Nginx, Ubuntu are just a few of the free pieces of software we use every single day. For this, we are very grateful. When we feel we have solved a problem in a way that can help other developers, we release our code as open source software on GitHub.

...PulseUI.framework (iOS, macOS, watchOS, tvOS) containing all the UI components you’ll see on the screenshots. Document-based Pulse apps (iOS, macOS) to view logs shared from other devices. As a developer, you integrate the frameworks into your app and configure them to capture logs and network traffic. You then add a way to display a Pulse console to view logs right on the device.

Beautiful, fast, and open-source viewer for your app logs. Forget scrolling through raw log files to find the errors or debug logs you're looking for. Forget about SSH'ing onto the production server just to read the logs. Log Viewer helps you quickly and clearly see individual log entries, to search, filter, and make sense of your Laravel logs fast. It is free and easy to install.

swift-log is the official, vendor-neutral logging API for Swift, providing a small, performant core that libraries and applications adopt to avoid logger lock-in. It defines common logging semantics and levels, plus a lightweight façade that backends can implement—so the same application code can run with different logging engines (e.g., OSLog on Apple platforms or custom sinks on servers). The package embraces Swift Package Manager, offers a clean Logger API, and is widely used across the...

DBD2 inserts database records from TCP input. It is a companion project to Syslgod2 and an application in its own right. It ships with a backgrounding client for generic use. The client sends whatever information the user puts on the command-line to the back-end daemon via TCP. Upon successful transmission, the client exits. On failure, it backs off and retries until its life-time timer expires. The back-end daemon accepts data from Syslogd2 or its own client and inserts that data...

...Online (application running and connected to NSLogger) and offline (saved logs) log viewing. Buffer all traces in memory or in a file, send them over to viewer when a connection is acquired. Define a log domain (app, view, model, controller, network…) and an importance level (error, warning, debug, noise…).