A focused writing and publishing space. https://write.with.parts
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Matt Baer a850fa14cd Move instance page editing to dedicated section 6 years ago
.github Automatically assign "bug?" label to bug reports 6 years ago
author Fix IsValidUsername check when PagesParentDir isn't current dir 6 years ago
cmd/writefreely Fix spacing around copyright notices 6 years ago
config Merge pull request #68 from writeas/user-invites 6 years ago
keys Move key generation to app from keys.sh 6 years ago
less Standardize admin navigation 6 years ago
migrations Set up migrations table on initial setup 6 years ago
page Fix spacing around copyright notices 6 years ago
pages Support user invites 6 years ago
parse Describe package parse 6 years ago
static Merge pull request #78 from mrvdb/apple-icons 6 years ago
templates Move instance page editing to dedicated section 6 years ago
.dockerignore added .git to make builds cache more effectively and run faster 6 years ago
.gitignore Fix go-bindata error in Travis build 6 years ago
.travis.yml Fix go-bindata error in Travis build 6 years ago
AUTHORS.md Add @nkoehring to AUTHORS 6 years ago
CONTRIBUTING.md Explain where to post questions, feedback, bugs 6 years ago
Dockerfile Deploy the app in the proper dir for dependency management 6 years ago
LICENSE Use AGPL 6 years ago
Makefile Do Travis builds without sqlite 6 years ago
README.md Merge branch 'readme-downloads' 6 years ago
account.go Support user invites 6 years ago
activitypub.go Fix AP follower INSERT with SQLite 6 years ago
admin.go Move instance page editing to dedicated section 6 years ago
app.go Move instance page editing to dedicated section 6 years ago
auth.go Fix spacing around copyright notices 6 years ago
cache.go Fix spacing around copyright notices 6 years ago
collections.go Add numeric avatars 6 years ago
config.ini.example Improved the Docker dev workflow slightly. 6 years ago
database-no-sqlite.go Support building without SQLite support 6 years ago
database-sqlite.go Fix tagged posts SQLite query 6 years ago
database.go Move instance page editing to dedicated section 6 years ago
docker-compose.yml Improved the Docker dev workflow slightly. 6 years ago
docker-setup.sh Improved the Docker dev workflow slightly. 6 years ago
errors.go Fix spacing around copyright notices 6 years ago
export.go Fix spacing around copyright notices 6 years ago
feed.go Fix hashes in code blocks rendered as hashtags 6 years ago
go.mod Support Go modules 6 years ago
go.sum Support Go modules 6 years ago
handle.go Send correct status on 410/500 in handleHTTPError 6 years ago
hostmeta.go Fix spacing around copyright notices 6 years ago
instance.go Fix spacing around copyright notices 6 years ago
invites.go Support user invites 6 years ago
keys.go Generate encryption keys in configured directory 6 years ago
nodeinfo.go Set PublicReader value in nodeinfo 6 years ago
pad.go Fix spacing around copyright notices 6 years ago
pages.go Move instance page editing to dedicated section 6 years ago
postrender.go Fix hashes in code blocks rendered as hashtags 6 years ago
posts.go Don't federate scheduled posts upon claiming 6 years ago
read.go Fix hashes in code blocks rendered as hashtags 6 years ago
request.go Fix spacing around copyright notices 6 years ago
routes.go Move instance page editing to dedicated section 6 years ago
schema.sql Set up migrations table on initial setup 6 years ago
session.go Fix spacing around copyright notices 6 years ago
sitemap.go Fix spacing around copyright notices 6 years ago
sqlite.sql Set up migrations table on initial setup 6 years ago
templates.go Support configuring resource directories 6 years ago
unregisteredusers.go Support user invites 6 years ago
users.go Support user invites 6 years ago
webfinger.go Fix spacing around copyright notices 6 years ago

README.md

 

Write Freely


Latest release Go Report Card Build status

 

WriteFreely is a beautifully pared-down blogging platform that's simple on the surface, yet powerful underneath.

It's designed to be flexible and share your writing widely, so it's built around plain text and can publish to the fediverse via ActivityPub. It's easy to install and light enough to run on a Raspberry Pi.

Try the editor

Find an instance

Features

  • Start a blog for yourself, or host a community of writers
  • Form larger federated networks, and interact over modern protocols like ActivityPub
  • Write on a fast, dead-simple, and distraction-free editor
  • Format text with Markdown
  • Organize posts with hashtags
  • Create static pages
  • Publish drafts and let others proofread them by sharing a private link
  • Create multiple lightweight blogs under a single account
  • Export all data in plain text files
  • Read a stream of other posts in your writing community
  • Build more advanced apps and extensions with the well-documented API
  • Designed around user privacy and consent

Hosting

We offer two kinds of hosting services that make WriteFreely deployment painless: Write.as for individuals, and WriteFreely.host for communities. Besides saving you time, as a customer you directly help fund WriteFreely development.

Write.as

Start a personal blog on Write.as, our flagship instance. Built to eliminate setup friction and preserve your privacy, Write.as helps you start a blog in seconds. It supports custom domains (with SSL) and multiple blogs / pen names per account. Read more here.

WriteFreely.host

WriteFreely.host makes it easy to start a close-knit community — to share knowledge, complement your Mastodon instance, or publish updates in your organization. We take care of the hosting, upgrades, backups, and maintenance so you can focus on writing.

Quick start

WriteFreely has minimal requirements to get up and running — you only need to be able to run an executable.

Note this is currently alpha software. We're quickly moving out of this v0.x stage, but while we're in it, there are no guarantees that this is ready for production use.

First, download the latest release for your OS. It includes everything you need to start your blog.

Now extract the files from the archive, change into the directory, and do the following steps:

# 1) Configure your blog
./writefreely --config

# 2) (if you chose MySQL in the previous step) Log into MySQL and run:
# CREATE DATABASE writefreely;

# 3) (if you chose Multi-user setup) Import the schema with:
./writefreely --init-db

# 4) Generate data encryption keys
./writefreely --gen-keys

# 5) Run
./writefreely

# 6) Check out your site at the URL you specified in the setup process
# 7) There is no Step 7, you're done!

For running in production, see our guide.

Packages

WriteFreely is available in these package repositories:

Development

Ready to hack on your site? Here's a quick overview.

Prerequisites

Setting up

go get -d github.com/writeas/writefreely/cmd/writefreely

Configure your site, create your database, and import the schema as shown above. Then generate the remaining files you'll need:

make install # Generates encryption keys; installs LESS compiler
make ui      # Generates CSS (run this whenever you update your styles)
make run     # Runs the application

Docker

Using Docker for Development

If you'd like to use Docker as a base for working on a site's styles and such, you can run the following from a Bash shell.

Note: This process is intended only for working on site styling. If you'd like to run Write Freely in production as a Docker service, it'll require a little more work.

The docker-setup.sh script will present you with a few questions to set up your dev instance. You can hit enter for most of them, except for "Admin username" and "Admin password." You'll probably have to wait a few seconds after running docker-compose up -d for the Docker services to come up before running the bash script.

docker-compose up -d
./docker-setup.sh

Now you should be able to navigate to http://localhost:8080 and start working!

When you're completely done working, you can run docker-compose down to destroy your virtual environment, including your database data. Otherwise, docker-compose stop will shut down your environment without destroying your data.

Using Docker for Production

Write Freely doesn't yet provide an official Docker pathway to production. We're working on it, though!

Contributing

We gladly welcome contributions to WriteFreely, whether in the form of code, bug reports, feature requests, translations, or documentation improvements.

Before contributing anything, please read our Contributing Guide. It describes the correct channels for submitting contributions and any potential requirements.

License

Licensed under the AGPL.