|f0x 47e961abb2 remove broken html||5 months ago|
|.github/ISSUE_TEMPLATE||6 months ago|
|author||7 months ago|
|cmd/writefreely||6 months ago|
|config||5 months ago|
|keys||6 months ago|
|less||6 months ago|
|page||6 months ago|
|pages||5 months ago|
|parse||7 months ago|
|static||5 months ago|
|templates||5 months ago|
|.dockerignore||6 months ago|
|.gitignore||6 months ago|
|.travis.yml||7 months ago|
|AUTHORS.md||6 months ago|
|CONTRIBUTING.md||6 months ago|
|Dockerfile||5 months ago|
|LICENSE||6 months ago|
|Makefile||6 months ago|
|README.md||5 months ago|
|account.go||6 months ago|
|activitypub.go||5 months ago|
|admin.go||5 months ago|
|app.go||5 months ago|
|auth.go||6 months ago|
|cache.go||6 months ago|
|collections.go||6 months ago|
|config.ini.example||6 months ago|
|database.go||6 months ago|
|docker-compose.yml||6 months ago|
|docker-setup.sh||6 months ago|
|errors.go||6 months ago|
|export.go||6 months ago|
|feed.go||6 months ago|
|handle.go||6 months ago|
|hostmeta.go||6 months ago|
|instance.go||6 months ago|
|keys.go||6 months ago|
|nodeinfo.go||5 months ago|
|pad.go||5 months ago|
|pages.go||6 months ago|
|postrender.go||6 months ago|
|posts.go||5 months ago|
|request.go||6 months ago|
|routes.go||5 months ago|
|schema.sql||6 months ago|
|session.go||6 months ago|
|sitemap.go||6 months ago|
|templates.go||6 months ago|
|unregisteredusers.go||6 months ago|
|users.go||6 months ago|
|webfinger.go||6 months ago|
This is a fork from https://github.com/writeas/writefreely/ to fix some things, and make some things better.
Changes so far:
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.
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) Log into MySQL and run: # CREATE DATABASE writefreely; # # 2) Configure your blog ./writefreely --config # 3) 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.
WriteFreely is available in these package repositories:
Ready to hack on your site? Here’s a quick overview.
go get 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
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.
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
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,
will shut down your environment without destroying your data.
Write Freely doesn’t yet provide an official Docker pathway to production. We’re working on it, though!
Before contributing anything, please read our Contributing Guide. It describes the correct channels for submitting contributions and any potential requirements.
Licensed under the AGPL.