Pasta is a (yet another) opinionated pastebin pastabin, written using Laravel.
It's a personal project, which began as a fun way to relax without staying away from code for too long.
New features, improvements, and fixes will (or won't) come as I implement them.
- Get a server running PHP 8.1, Node.js 17, and MySQL 8. Older (not much older, though) versions should work. Other databases also should work.
- Clone the repo or download a zip.
- Install dependencies -
composer installfor PHP,npm installfor JS. - Copy
.env.exampleto.envand fill in values to match your setup. At the moment the important ones areAPP_ENV(should be set toproductionon production),APP_DEBUG(should befalsein production), andDB_*(should match your DB). - Generate an encryption key with
php artisan key:generate. Important - it isn't used to encrypt pastas. Pasta encryption keys are derived from user-provided passwords. Laravel uses it for some internal stuff. - Run migrations -
php artisan migrate. This will set up the database structure for you. - Build styles and scripts for production with
npm run production.npm run devwill build for development andnpm run watchwill watch for changes while you're developing. - Serve with
php artisan servefor development. Serve frompublic/with Apache, Caddy, Nginx or whatever you prefer.
See Laravel 9.x docs for more information on possibilities. This isn't an advanced app. A basic LEMP stack or shared hosting with PHP/MySQL should work.
- Top right is where all the settings live.
- Language means syntax highlighting mode. Most of what CodeMirror supports is there. Some entries are duplicated for clarity.
- Anonymous is the default author name. This will change when user features are implemented. You can enter your name here and it will display with your pasta.
- Password (optional) is the (optional) password, from which an encryption key is derived. If you're okay with your pasta being sent and stored in plaintext, leave it alone. If not, provide an 8+ chars password. It WILL be sent to the server, but it won't be stored. At least if nobody modified the code (I didn't. This repo should be ok. Unless one of a couple dozen things that can happen will happen, so... review the code before using it.)
- Finish up the repo.
Readme, examples, wiki, dotfiles. - Client-side encryption
- Web frontend using Alpine.js
- Clean up initial Laravel files
- User login/registration
- Figure out what to do next. Something will inevitably come up :)
Any contributions are welcome, but you really should consider helping other FLOSS projects first. They need it more.
Pasta is open-source software licensed under the MIT license. TLDR: Do (almost) anything you want with it, don't blame me if it doesn't work the way you thought it will.