Go to file
Daniel Legt 7982d564e8 * 2022-06-07 02:25:31 +03:00
dist + Build Script 2022-05-21 16:45:56 +03:00
lib * 2022-06-07 02:25:31 +03:00
static . 2022-06-07 02:04:21 +03:00
templates * Restyled the Pad title 2022-06-07 00:27:51 +03:00
.env.example Working on the admin interface 2022-06-02 23:53:32 +03:00
.gitignore + Build Script 2022-05-21 16:45:56 +03:00
Changelog.md * Version Bumb 2022-06-01 18:29:24 +03:00
Dockerfile * Replaced alpine with Scratch 2022-06-01 21:28:57 +03:00
LICENSE * Updated the license 2022-05-22 19:42:49 +03:00
README.md * Readme visual changes 2022-05-21 17:45:34 +03:00
build.sh Updated visuals 2022-05-21 17:41:43 +03:00
docker-compose.example.yaml * Docker Compose example updated 2022-06-01 18:43:35 +03:00
go.mod Real time WebSocket pasting 2022-06-07 00:02:31 +03:00
go.sum Real time WebSocket pasting 2022-06-07 00:02:31 +03:00
main.go WebSockets Work started 2022-06-04 16:32:53 +03:00

README.md

Gopher

Quickly create "pads" and share with others

Docker Ko-Fi Go

demo

FreePad

Gopher

FreePad is a simple Go project to help you juggle temporary notes that you might wanna pass from one device to another, or from a person to another with memorable and easy to communicate online "Pads".

The project is absolutely free to use, you can extend the code and even contribute, I am more than happy to be corrected in my horrible beginner code.

The current maintainer and creator is Kato Twofold

Gopher

Before getting started there are a couple things you should configure before proceeding, such as the database storage type and a couple limits, now if you really want to you can skip these but it's better to know what you're running as to not wake up with a not-so-nice surprise.

Gopher

The .env file contains all of the available options and you should use it to change those said variables, these are really important to customizing and self hosting this experience for yourself.

If you need any help with any setting you can always open an issue over on github and get help from me.

If you are barely getting started with hosting your own services, or even Sys admin stuff in general or writing code my suggestion is to just copy .env and leave it as is until you get it running with the defaults running fine, afterwards you can play with it a little and who knows, maybe even get to learn something!

Gopher

# Get into a directory to run this
mkdir ~/freepad && cd freepad

# Copy the latest .env and docker-compose.example.yaml files
wget -O docker-compose.yaml https://raw.githubusercontent.com/JustKato/FreePad/master/docker-compose.example.yaml
wget -O .env https://raw.githubusercontent.com/JustKato/FreePad/master/.env.example

# Edit your docker-compose.yaml and change the DOMAIN_BASE environment variable
vim docker-compose.yaml

# Edit your .env file and change the variables to your liking
vim .env

# Run the container
docker-compose up
# Run the container in the background
docker-compose up -d

Distribution

Downloads here

# Get into a directory to run this
mkdir ~/freepad && cd freepad

# Get the latest distribution from https://github.com/JustKato/FreePad/releases
wget -O release.zip https://github.com/JustKato/FreePad/releases/download/main/...

# Unzip the release
unzip release.zip

# Edit the .env file
vim ./.env

# Run the program
./freepad

Building

# Clone th erepo
git clone https://github.com/JustKato/FreePad.git ~/freepad

# Get into the directory
cd ~/freepad

# Build using the script
./build.sh

# Copy the environment variable
cp .env dist/

# Go into the program's directory
cd dist

# Run the program
./freepad