Common Code & Config Files 🔒 Runs locally in your browser — nothing is uploaded.

phpinfo.php, .htaccess, Dockerfile, nginx.conf and more — copy or download.

Server

phpinfo.php Upload to a server to print its full PHP configuration. Delete afterwards — it leaks server details. .htaccess Apache: force HTTPS, SPA fallback to index.html, gzip and long-cache static assets. .htpasswd Apache basic-auth users file. The example password is "secret" (bcrypt). Generate real hashes with htpasswd -B. nginx.conf Reverse proxy to an app on :3000 with SPA fallback and gzip. php.ini Common PHP settings for uploads, memory and error display in development. app.service systemd unit to run a Node/Python app as a service that restarts on failure. crontab Cron schedule examples — backups, cache clearing, health pings.

Docker

Dockerfile Multi-stage Node.js image — small final layer, production deps only. Dockerfile (Python) Slim Python image with cached pip layer. docker-compose.yml Web app + PostgreSQL with a named volume and healthcheck. .dockerignore Keep node_modules, git history and secrets out of the Docker build context.

CI / Deploy

.github/workflows/ci.yml GitHub Actions: install, lint, test and build on every push and pull request. .gitlab-ci.yml GitLab CI pipeline with test and build stages using a Node image. Procfile Heroku / Railway process types — how to start your web and worker dynos. vercel.json Vercel config: SPA rewrites and a security header. netlify.toml Netlify build settings and an SPA redirect.

Web

index.html Minimal "It works!" page to confirm a web server serves static files. robots.txt Allow all crawlers and point them at your sitemap. sitemap.xml Minimal XML sitemap listing two URLs with last-modified dates. manifest.webmanifest Web app manifest so a site can be installed as a PWA. sw.js Bare-bones service worker: precache the shell and serve cache-first. .well-known/security.txt Tells security researchers how to report vulnerabilities (RFC 9116). humans.txt Credits the people behind the site — a small web tradition. 404.html A simple custom 404 page.

Config & tooling

.env.example Template of environment variables — commit this, never the real .env. .editorconfig Consistent whitespace across editors and languages. .gitattributes Normalize line endings and mark binary files so diffs stay clean. .prettierrc A sensible Prettier baseline. eslint.config.js Flat ESLint config for modern JavaScript with recommended rules. tsconfig.json Strict modern TypeScript starting config. .npmrc Reproducible, quieter npm installs. .nvmrc Pin the Node.js version for nvm and CI. Makefile Common task shortcuts. Remember: recipes are indented with TABS.

Language manifests

requirements.txt Pinned Python dependencies for a typical web app. pyproject.toml Modern Python project metadata and tool config. composer.json PHP Composer manifest with PSR-4 autoloading. package.json A minimal Node.js package manifest with common scripts. go.mod A Go module file declaring the module path and Go version.

About this tool

Every developer keeps re-typing the same handful of files: the phpinfo.php you drop on a server to check its config, the .htaccess that forces HTTPS, the Dockerfile, the docker-compose with a database, the nginx reverse proxy. Here they are, ready to view, copy or download with the correct filename.

Treat them as starting points, not production configs — read each one and adjust it to your setup. Everything is served as static text; nothing runs on a server here.

Frequently asked questions

What license are these code samples under?

They're free to use, copy, and modify for any purpose — personal projects, tests, teaching, or as a starting boilerplate. No attribution is required.

Are these production-ready, or just examples?

They're minimal, working boilerplate meant as a starting point or a test fixture — review and harden them (error handling, security, config) before shipping to production.

What are these files useful for beyond just reading the code?

They're handy as real test fixtures: use them to check file-upload validators, syntax highlighters, linters, or file-type detection across many languages and formats without writing sample files yourself.

Is anything about what I download tracked or uploaded?

No. These are static file downloads — nothing about which files you pick or download is sent anywhere or logged.

What categories and languages are covered?

Files are grouped by category — server, Docker, CI, web, config, and language — spanning many popular languages and toolchains, so you can grab a realistic sample file for almost any file type.