So, you have your shining, ticketing, tomato-shaped timer on your desk and you are a proud practitioner of the Pomodoro Technique®. I've got bad news and good news. The bad news is the Pomodoro Technique® can seriously damage your team's productivity. The good news is that it's very likely that you are not practicing the…

GOfax.IP - T.38 / Fax Over IP backend for HylaFAX using FreeSWITCH - gonicus/gofaxip

MultiBootUSB

This small structure it’s a backyard cottage that measures 420 square feet. Even though it’s small, it’s been very cleverly designed with a layout that allows it to house a living room, a kitchen, a dining area, a bathroom and a loft. - Page 2

This blogpost provides a summary of different ways to share a git repository. Depending on your needs you can opt for different solutions. RepositoryProConControlling AccessCreate Repositories File shareNo network access requiredNot internet friendlyUsing filepermissionsNeeds preparation per project on the share Git daemonFast git protocolNot internet friendly portno good permission control. Read by default, Write can be enabled , but only anonymousper project needs to be blessed Plain SSH serverAllows good securityNot internet friendly port, requires account creation per user on server Uses filepermissionsper project inited SSH server git-shellEnhancement of Plain SSH Server scenarioNot internet friendly port, requires account creation per user on serverUses filepermissionsper project inited GitosisAdds good remote management of users and repositories, only requires one system accountNot internet friendly portUses gitosis-config fileNo server initalisation, only config is needed Apache httpFalls back to standard apache config, only requires one system account, internet friendlySlightly overheadUses htpasswdper project inited Apache http + gitwebFalls back to standard apache config, only requires one system account, internet friendly, adds nice view of repository Slightly overhead, read-only accessUses htpasswdper project inited githubInternet accessible, easy to use webinterfaceHosted externallyManaging sshkeysWeb interface http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#setting-up-a-public-repository Preparation:Git enable a simple project-X Let's say you have project called project-X that you have been working on, on your local machine. It contains one file called README. To enable git on this project you can: $ cd $HOME/project-X # git init enables the git repository $ git init # You add the readme file to the repository $ git add README # You commit your changed to your local repository $ git commit -a -m 'Added README'

Version 2 is live! Wordlists sorted by probability originally created for password generation and testing - make sure your passwords aren't popular! - berzerk0/Probable-Wordlists

Now, next, and beyond: Tracking need-to-know trends at the intersection of business and technology

An elegant and modern git repository viewer. Contribute to klaussilveira/gitlist development by creating an account on GitHub.

Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.

Don't worry, it's totally legal

While it's pretty painless to convert from commercial office software to an open source version, if you'd like to replace commercial security products

Wood Tools - деревообработка

When adding packages with Bower, should I need to manually update the main.less or should it happen automatically? For instance, I ran bower install --save font-awesome But nothing was added to main.less in the aut…

ansible_netbox_dns. GitHub Gist: instantly share code, notes, and snippets.

A most foundational practice.

Are you still doing Windows PC deployments the same way you’ve done it for the last ten years (or longer)? My blog wants to help you to address this.

Package gorilla/mux is a powerful HTTP router and URL matcher for building Go web servers with 🦍 - gorilla/mux

A timeline recording only some of the many disasters happening in crypto, decentralized finance, NFTs, and other blockchain-based projects.

This Design World website educates engineers designing moving machinery with linear axes and actuators for automation in industrial and end-user builds. It details specification and integration of linear guides and slides, drives (such as screws and motors), linear feedback, linear actuators, stages, and gantries.

Hi, I want to simulate incoming calls on Asterisk server. The way I’m doing that is, I just connect an outgoing call from Asterisk to an incoming number. Here is what I’m currently doing now to simulate a single connec…

I had long been aware of the [effort of cznic](https://gitlab.com/cznic/sqlite) to automatically translate the C source of SQLite to Go while avoiding the complexity CGo would introduce. SQLite was always meant to be a database you embed into your application, and I was curious what tradeoffs that meant, if any, and just generally how it differed from the usual suspects (PostgreSQL, etc.). To explore these trade-offs and differences, I decided to dive deeper into the usage of this library. SQLite is a single-writer multiple-reader database. Using just a single instance of database/sql.DB will not work well with this, because it will make it hard to avoid receiving SQLITE_BUSY errors when multiple writers try to run at the same time (because sql.DB is a connection pool). So we will need to separate readers from writers by making two instances of database/sql.DB and limiting the writer to a single [MaxOpenConn](https://pkg.go.dev/database/sql#DB.SetMaxOpenConns) and the reader to as many as you require. So far, SQLite is behaving remarkably like other databases apart from the single-writer gotcha; we still have connections and per-connection settings. The usual way to pass these settings is usually in the DSN you pass to [sql.Open](https://pkg.go.dev/database/sql#Open) and this is [definitely possible](https://pkg.go.dev/modernc.org/sqlite#Driver.Open), but I find that it would be more straightforward if I could just run my custom SQL when a new connection is made[1]. We can do that with [sqlite.RegisterConnectionHook](https://pkg.go.dev/modernc.org/sqlite#RegisterConnectionHook). Now the question is what settings to use, because [there are quite a few of them](https://www.sqlite.org/pragma.html). These are the ones I am using personally: - `PRAGMA journal_mode = WAL;` Use write-ahead-logging. Better concurrency, but with an edge-case: with heavy writers, the wal can grow idefinitely ([see for more](https://www.sqlite.org/cgi/src/doc/wal2/doc/wal2.md)). I don't expect this will happen in my use-case. For a good description on the various jornal modes, [see this blogpost](https://www.mycelial.com/learn/sqlite-journal-mode-options). - `PRAGMA synchronous = NORMAL;` Since with the WAL journal mode, this is safe, there is no reason to use FULL. - `PRAGMA temp_store = MEMORY;` Let's store temporary indices, tables, etc. in memory, my use-case is not very resource-constrained to require using the filesystem (also, [this is a fun read](https://www.sqlite.org/fasterthanfs.html) if we are talking about additional syscalls to the kernel) - `PRAGMA mmap_size = 30000000000; -- 30GB` Just making sure, access to my database is always done with memory-mapped I/O. - `PRAGMA busy_timeout = 5000;` How much time to wait in milliseconds after which SQLITE_BUSY is returned when waiting for the db to unlock. - `PRAGMA automatic_index = true;` Make sure [automatic indexing](https://www.sqlite.org/optoverview.html#autoindex) is enabled, it can only help, and is a great way to get warnings about indexes that should be created. - `PRAGMA foreign_keys = ON;` Make sure foreign key enforcement is enabled. - `PRAGMA analysis_limit = 1000;` Make sure [ANALYZE](https://www.sqlite.org/lang_analyze.html#approx) returns quickly in case the DB gets large. - `PRAGMA trusted_schema = OFF;` No idea what security audited functions are, but this setting makes sure only those can be run. The manual page tells me to turn it off anyway, so let's do that. Not all of these settings are per-connection settings, but it doesn't hurt to always run all of these on every connection, and having a single "Init SQL" makes things simpler. Let's deal with explicit transactions next. The default transaction mode is DEFERRED, meaning that it depends on the next statement what type of transaction is started (if a SELECT statement comes first, a read transaction is started, with the possibility of upgrading it to a write transaction depending on the statements that follow). With our setup, there should never be multiple writers concurrently, so making all transactions write transactions from the get-go (with BEGIN IMMEDIATE) can only help us show if this invariant is violated. Putting this all together, this is the code we arrive at: ```go package main import ( "bytes" "context" "crypto/sha1" "database/sql" "database/sql/driver" "encoding/hex" "fmt" "time" "modernc.org/sqlite" ) type DB struct { dbPath string Read *sql.DB Write *sql.DB } const initSQL = ` PRAGMA journal_mode = WAL; PRAGMA synchronous = NORMAL; PRAGMA temp_store = MEMORY; PRAGMA mmap_size = 30000000000; -- 30GB PRAGMA busy_timeout = 5000; PRAGMA automatic_index = true; PRAGMA foreign_keys = ON; PRAGMA analysis_limit = 1000; PRAGMA trusted_schema = OFF; ` func New(ctx context.Context, dbPath string) (db *DB, err error) { db = &DB{ dbPath: dbPath, } // make sure every opened connection has the settings we expect sqlite.RegisterConnectionHook(func(conn sqlite.ExecQuerierContext, _ string) error { _, err = conn.ExecContext(ctx, initSQL, nil) return err }) write, err := sql.Open("sqlite", "file:"+db.dbPath) if err != nil { return } // only a single writer ever, no concurrency write.SetMaxOpenConns(1) write.SetConnMaxIdleTime(time.Minute) if err != nil { return } read, err := sql.Open("sqlite", "file:"+db.dbPath) if err != nil { return } // readers can be concurrent read.SetMaxOpenConns(100) read.SetConnMaxIdleTime(time.Minute) db.Read = read db.Write = write return } func (db *DB) InTransaction(ctx context.Context, tx func(context.Context, *sql.Conn) error) (err error) { // cancel anything that takes longer than 5 seconds var cancel func() ctx, cancel = context.WithTimeout(ctx, time.Duration(5*time.Second)) defer cancel() // separate conn thats just for us // so that the transactions queries are executed together conn, err := db.Write.Conn(ctx) if err != nil { return } defer conn.Close() _, err = conn.ExecContext(ctx, "BEGIN IMMEDIATE TRANSACTION") if err != nil { return } defer func() { if r := recover(); r != nil || err != nil { if _, err = conn.ExecContext(ctx, "ROLLBACK"); err != nil { return } } }() err = tx(ctx, conn) if err != nil { return } _, err = conn.ExecContext(ctx, "COMMIT") return } ``` Just as a small added bonus, it's also very easy to register our own go functions that we can then call from SQL. In this example, we define the sha1 function, receiving and returning a single argument, and always returning the same output for the same input (thus the deterministic). For more information, [see the docs](https://www.sqlite.org/appfunc.html) ```go func registerFuncs() { // lets add our own sha1 hash function usable from SQL sqlite.MustRegisterDeterministicScalarFunction( "sha1", 1, func(ctx *sqlite.FunctionContext, args []driver.Value) (driver.Value, error) { var arg *bytes.Buffer switch argTyped := args[0].(type) { case string: arg = bytes.NewBuffer([]byte(argTyped)) case []byte: arg = bytes.NewBuffer(argTyped) default: return nil, fmt.Errorf("expected argument to be a string, got: %T", argTyped) } h := sha1.Sum(arg.Bytes()) return hex.EncodeToString(h), nil }, ) } ``` In conclusion, this solution works perfectly well for most of the usage scenarios out there where immense scaling is neither expected nor needed. There are faster ways to use SQLite with Go (see the [excellent cvilsmeier benchmarks](https://github.com/cvilsmeier/go-sqlite-bench)), but its still plenty-fast enough, and avoiding CGo makes it very convenient also. [1]: This is another thing that database/sql.DB being a connection pool makes harder.

Simple Linux router implementation for Debian + Netfilter/IPtables - noahbailey/ansible-router

Telecom and IT Knowledgebase Articles from the Telecom Experts at sandman.com. Learn how to fix the unfixable.

Recipients request specific items they need or want. They do this by working with a Connecting Organization. Once the Request Form is filled out, the Connecting Organization submits it to HYH for approval. Once approved, the requests are posted on the website.

ADSB Exchange is the world's largest co-op of unfiltered flight data.

Contribute to PrometheanInfoSec/Lockdown development by creating an account on GitHub.

Random stories from the IT world

Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.

In this blog post, we explore how to generate device configurations with NetBox using NetBox 3.5's new built in Jinja2 templating features.

neurospicy toaster writing random code. fnr1r has 23 repositories available. Follow their code on GitHub.

Hacker Public Radio is a podcast that releases shows every weekday Monday through Friday. Our shows are produced by the community (you) and can be on any topic that is of interest to hackers and hobbyists.

A command-line tool for Logseq to quickly create and edit journal entries. - jrswab/lsq

Slim Framework is a very light PHP framework that’s great for building web applications and REST APIs. The Slim Hello World example, found right on the homepage, will get you up and running in a matter of minutes. Once you’ve … Continue reading →

This Design World website educates engineers designing moving machinery with linear axes and actuators for automation in industrial and end-user builds. It details specification and integration of linear guides and slides, drives (such as screws and motors), linear feedback, linear actuators, stages, and gantries.

Timothy Leary — ‘Admit it. You aren’t like them. You’re not even close. You may occasionally dress yourself up as one of them, watch the same mindless te...

Contribute to taigaio/taiga-back development by creating an account on GitHub.

Pihole Speedtest Mod. Contribute to arevindh/pihole-speedtest development by creating an account on GitHub.

Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.

An in-depth analysis of how Drupal's development was sponsored between July 1, 2020 and June 30, 2021.