Fraise

Map of planned industrial and infrastructure projects, clusters, airports, and harbors across 140+ countries. Explore $70T+ CapEx and logistics opportunities on Fluidify. The Fluidify Map is the 2D industrial and infrastructure map. Use it to explore planned projects, industrial clusters, airports, and harbors across 140+ countries. Machine-readable copies: /home.md · /map.md · /about.md · /llms.txt

Software has never been easier to start — or easier to turn into a mess. A simple application becomes a pile of frameworks, dependencies, services, and infrastructure, and AI just makes the pile grow faster. View on GitHub Edit on Replit Free, source included, nothing to sign up for. Most software starts from a blank project. Features get added, dependencies accumulate, architecture evolves, and workarounds become permanent — until changing one thing means worrying about five others. Scalar starts from the opposite premise: a deliberately simple foundation — Python on the server, server-rendered HTML, SQLite, and minimal JavaScript. A working application you can read from top to bottom, understand, and change.

Open-source, self-hosted database sync with real-time CDC — PostgreSQL, MySQL, SQLite, MongoDB and Redis, any engine to any other. One command to install. Syncle connects to PostgreSQL, MySQL, SQLite, MongoDB and Redis. You pick a table on one of them and where it should go on another. Syncle copies the rows across, then keeps copying as the source changes. Docker with Compose v2 is all you need. Runs on your own machine, MIT licensed. PostgreSQL Syncle MySQL MongoDB Redis One Postgres table feeding three other databases at the same time. A bridge connects one source to one or more destinations. Any engine can sit on either side, so a Postgres table can go to MongoDB, to Redis, or to another Postgres. A destination can also be an HTTP endpoint, if you are feeding a service instead of a database. If the destination table does not exist yet, Syncle creates it and works out the column types for that engine. Writes are upserts, so running a sync twice will not leave you with two copies of a row. A job that dies partway through restarts from the last row it recorded, not from the beginning.