Please check out fastbin-rewritten:
https://github.com/jozsefsallai/fastbin-rewritten
Painless, self-hosted, modern alternative to Hastebin.
Just paste your code or text, click save, and you're ready to go! You can also select a programming language from the dropdown. You can click on the "Raw" button to view only the contents, without any UI stuff.
fastbin uses Monaco as its editor, which is the editor used by Visual Studio Code. This offers great functionality and syntax highlighting support.
You can also clone a document using the Clone button.
When viewing documents, the syntax highlighter works based on the ending of the URL. For example, if I have a JavaScript file with the key "foobar", I can append ".js" to the end of the URL and it will highlight it as JavaScript. Appending .js to the raw URL will obviously not work, it expects only the key to be provided.
fastbin now has its own command line client. It's available for Linux, Mac OS, Windows, and OpenBSD and you can download it here.
fastbin was designed to be compatible with most Hastebin clients. If your client support specifying a custom server, you can specify your self-hosted fastbin URL and it should work just fine.
Currently, files are stored for an indefinite amout of time. This might change in the future (possibly as a custom config option).
Please do NOT post any of your secret keys or passwords to a fastbin server. Every URL is unlisted, but again, available for the public. Snippets are NOT encrypted (i.e. they're plaintext). If there's popular demand for snippet encryption, I'll make sure to include that.
1. Clone the repository
git clone git@github.com:jozsefsallai/fastbin.git
cd fastbin
2. Install the dependencies
npm install
3. Configure your fastbin server
cp config.development.json config.production.json
nano config.production.json
4. Build for production
npm run prod
Note: you need at least 1 GB of usable RAM in order to initiate a production build. If you have less than that, you can rely on swap memory. Don't worry if the build takes a long time (more than 1-2 minutes, as this is normal), especially if you're building for the first time.
5. Start the server
node index.js
For production environments, I recommend that you use a tool such as PM2 to keep your fastbin server running 24/7.
If you want to password-protect your fastbin instance, you can do so by generating a key using the following command:
node bin/generateKey
Once you have that key, you have to use it to be able to log in and post snippets. If you're using the API, you have to provide the key as a bearer auth token in your request's auth headers. Please note that snippets made using this method are still going to be publicly available.
At the moment, fastbin can store snippets using three different strategies: FileStorageStrategy,
S3StorageStrategy, FirebaseStorageStrategy. You can specify which one you want to use by
changing the value of the storageStrategy property inside of config.[environment].json
from FileStorageStrategy to any of the ones mentioned earlier.
Some storage strategies require additional configuration.
You can specify the location of the stored snippets using the fileStorage.location config
option. This path is relative to the root of the project.
You need to specify the auth credentials, as well as the endpoint and the S3 bucket name
inside the aws.s3 object of the configuration file.
You need to specify the name of the Firebase Storage bucket* inside of the firebase.bucket
property of the config. You should also include your Firebase credentials certificate in
the root of the project and call it firebase.json (this step is crucial). If you don't
have a credentials JSON file yet, you can generate one in the settings of your Firebase
projects.
*Make sure you only specify the bucket's name, WITHOUT ".appspot.com".
Contribution is more than welcome and appreciated! If you want to contribute, you can file a bug report or submit a pull request.
MIT.