This gist lists challenges you run into when building offline-first applications based on IndexedDB, including open-source libraries like Firebase, pouchdb and AWS amplify (more).
Note that some of the following issues affect only Safari. Out of the major browsers, Chrome's IndexedDB implementation is the best.
When this bug occurs, every time you use the indexeddb, the WAL file grows. Garbage collection doesn't seem to be working, so after a while, you end up with gigabytes of data.
So you want to write a sync system for a web app with offline and realtime support? Good luck. You might find the following resources useful.
Database in a browser, a spec (Stepan Parunashvili)
What problem are we trying to solve with a sync system?
The web of tomorrow (Nikita Prokopov)
| # Parallelly download all aws-lambda functions | |
| # Assumes you have ran `aws configure` and have output-mode as "text" | |
| # Works with "aws-cli/1.16.72 Python/3.6.7 Linux/4.15.0-42-generic botocore/1.12.62" | |
| download_code () { | |
| local OUTPUT=$1 | |
| aws lambda get-function --function-name $OUTPUT --query 'Code.Location' | xargs wget -O ./lambda_functions/$OUTPUT.zip | |
| } | |
| mkdir -p lambda_functions |
| #################################### | |
| # 创建者：v2rayse.com | |
| # 客户端：Clash.Meta | |
| # 创建时间：2023-10-16 11:18:43 | |
| # 使用模版：V2RaySE 默认模版 | |
| # 节点数量：1 | |
| # Stash修改版 | |
| #################################### | |
| # !!当前配置文件请使用基于 Clash.Meta 内核程序 | |
| mixed-port: 7890 |
| try | |
| { | |
| await using var sqlDataReader = await sqlCommand.ExecuteReaderAsync(cancellationToken); | |
| await using var streamWriter = new StreamWriter($"{reportName}_{startDate:dd-MM-yyyy}-{endDate:dd-MM-yyyy}.csv"); | |
| await using var csvWriter = new CsvWriter(streamWriter, _csvConfiguration); | |
| var columnSchema = sqlDataReader.GetColumnSchema(); | |
| var columnCount = columnSchema.Count; | |
| // write headers to CSV: |
| /* | |
| Solar system objects | |
| Adapted from: http://en.wikipedia.org/wiki/List_of_Solar_System_objects_by_size | |
| Collected by: https://www.khanacademy.org/profile/patrick809/programs | |
| */ | |
| CREATE TABLE solar_system_objects( | |
| body TEXT | |
| , mean_radius NUMERIC /* km */ | |
| , mean_radius_rel NUMERIC /* relative to earth */ | |
| , volume NUMERIC /* 10^9 km^3 */ |
| # CLI | |
| sudo apt update -y | |
| sudo apt install -y \ | |
| git curl btop \ | |
| docker.io docker-buildx \ | |
| build-essential pkg-config autoconf bison rustc cargo clang \ | |
| libssl-dev libreadline-dev zlib1g-dev libyaml-dev libreadline-dev libncurses5-dev libffi-dev libgdbm-dev libjemalloc2 \ | |
| libvips imagemagick libmagickwand-dev mupdf mupdf-tools \ | |
| redis-tools sqlite3 libsqlite3-0 libmysqlclient-dev \ | |
| rbenv apache2-utils |
| #!/bin/sh -e | |
| #git-cache-meta -- simple file meta data caching and applying. | |
| #Simpler than etckeeper, metastore, setgitperms, etc. | |
| #from http://www.kerneltrap.org/mailarchive/git/2009/1/9/4654694 | |
| #modified by n1k | |
| # - save all files metadata not only from other users | |
| # - save numeric uid and gid | |
| # 2012-03-05 - added filetime, andris9 |
Organizing your Go (Golang) project's folder structure can help improve code readability, maintainability, and scalability. While there is no one-size-fits-all structure, here's a common folder structure for a Go project:
project-root/
├── cmd/
│ ├── your-app-name/
│ │ ├── main.go # Application entry point
│ │ └── ... # Other application-specific files