Read the latest posts from Fedi.dev.

from Gytis Repečka

Today WriteFreely v.0.10 was released with two little commits by me: Lithuanian translation and lessc installation fix for CentOS – so proud to be listed among contributors 😊 To celebrate it I'm posting quick guide how to update WriteFreely instance when building binary from source.

1. Backup

As always, use mysqldump to backup your database and preferably entire home directory of user running WriteFreely.

2. Stop system service

systemctl stop writefreely

At this point Nginx will start returning Bad gateway error to visitors.

3. Pull sources

Because I use my forked repository, I retrieve sources by using this command:

go get -d -u -v code.gyt.is/writefreely

Updated sources will be available in your user's home GOPATH, run below command to know:

echo $GOPATH

In my case it is ~/go/src.

After sources are retrieved change directory to ~/go/src/src/code.gyt.is/writefreely.

4. Build

Don't forget to ensure Go modules are enabled otherwise build will fail on sitemap.go as described in issue #93. So before building run:

export GO111MODULE=on

And initiate build process:

make build   # Compile the application

5. Run database migration

Might not be always necessary (check release notes) but better run database migration:

./cmd/writefreely/writefreely  --migrate

6. Initiate installation

make install

7. Build interface

To build templates and CSS, run:

make ui # Generates CSS (run this whenever you update your styles)

Note – lessc runs fine with CentOS starting v.0.10 (my pull request there 😊).

8. Run binary

Run binary with”

make run

This will copy writefreely binary to to your GOBIN path.

9. Start system service

systemctl start writefreely

At this point you should have #writefreely running fine and #nginx reverse-proxying to it successfully.

Note – it's always a good idea to ensure your WriteFreely service runs on dedicated system user.

Read more #server tips on my blog and don't forget to toot me @gytis@mastodon.lt!

Happy lightweight federated blogging 😎


from Gytis Repečka

WordPress content management system can successfully federate – there is a nice ActivityPub plugin. However, when running WordPress on Nginx server (as HTTP server, not only reverse proxy) there might be an issue – after setting up ActivityPub on auto.coffee I couldn't find @gytis@auto.coffee from my Mastodon instance.

After doing some digging I found out ActivityPub standard requires webfinger end-point under .well-known folder which by proposed default WordPress configuration for Nginx is forbidden.

First I tried to allow access to .well-known but even though JSON API started working, trying to access specific user end-point it kept throwing following error:

  "code": "rest_missing_callback_param",
  "message": "Missing parameter(s): resource",
  "data": {
    "status": 400,
    "params": [

While following example of successfully federating WordPress instance it was expected to return something like this:

  "subject": "acct:gytis@blog.gyt.is",
  "aliases": [
  "links": [
      "rel": "self",
      "type": "application/activity+json",
      "href": "https://blog.gyt.is/author/gytis/"
      "rel": "http://webfinger.net/rel/profile-page",
      "type": "text/html",
      "href": "https://blog.gyt.is/author/gytis/"

Actually problem was that URL was not passed to WordPress' index.php – workaround was provided in issue #8 of ActivityPub plugin. Solution is easy as adding extra location directive in Nginx configuration:

location ~* /.well-known {
    try_files $uri $uri/ /index.php?$args;

And there it goes – Auto.Coffee is ready to federate :)

Read more #server and #nginx #configuration tips.


from Inretio, MB

“Inretio”, MB registered in Lithuania, see below details:

Data Value
Company code 305174082
Established 2019-05-28
Official name “Inretio”, MB
Legal form Small Partnership

Information about company is stored at State Enterprise Centre of Registers, Lithuania.