remove reference to backend

This commit is contained in:
FloatingGhost 2022-07-14 16:52:09 +01:00
parent a6c4caf965
commit 2bd4541757
23 changed files with 43 additions and 43 deletions

View File

@ -1,6 +1,6 @@
# Transfering the config to/from the database
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
## Transfer config from file to DB.

View File

@ -1,6 +1,6 @@
# Database maintenance tasks
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
!!! danger
These mix tasks can take a long time to complete. Many of them were written to address specific database issues that happened because of bugs in migrations or other specific scenarios. Do not run these tasks "just in case" if everything is fine your instance.

View File

@ -1,6 +1,6 @@
# Managing digest emails
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
## Send digest email since given date (user registration date by default) ignoring user activity status.

View File

@ -1,6 +1,6 @@
# EMail administration tasks
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
## Send test email (instance email by default)

View File

@ -1,6 +1,6 @@
# Managing emoji packs
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
## Lists emoji packs and metadata specified in the manifest

View File

@ -1,6 +1,6 @@
# Managing instance configuration
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
## Generate a new configuration file
=== "OTP"

View File

@ -1,6 +1,6 @@
# Creating trusted OAuth App
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
## Create trusted OAuth App.

View File

@ -1,6 +1,6 @@
# Managing relays
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
## Follow a relay

View File

@ -1,6 +1,6 @@
# Managing robots.txt
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
## Generate a new robots.txt file and add it to the static directory

View File

@ -1,6 +1,6 @@
# Managing uploads
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
## Migrate uploads from local to remote storage
=== "OTP"

View File

@ -1,6 +1,6 @@
# Managing users
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
## Create a user

View File

@ -1,6 +1,6 @@
# Configuring search
{! backend/administration/CLI_tasks/general_cli_task_info.include !}
{! administration/CLI_tasks/general_cli_task_info.include !}
## Built-in search

View File

@ -1,6 +1,6 @@
# Installing on Alpine Linux
{! backend/installation/otp_vs_from_source_source.include !}
{! installation/otp_vs_from_source_source.include !}
## Installation
@ -10,7 +10,7 @@ As of Alpine Linux v3.16, `doas` is the preferred way of running privileged comm
If you are running an earlier version, replace `doas` with `sudo` (and use `sudo -Hu akkoma` instead of `doas -u akkoma`).
If you want to run this guide with root, ignore the `doas` at the beginning of the lines, unless it calls a user like `doas -u akkoma`; in this case, use `su -l <username> -s $SHELL -c 'command'` instead.
{! backend/installation/generic_dependencies.include !}
{! installation/generic_dependencies.include !}
### Prepare the system
@ -223,6 +223,6 @@ doas -u akkoma env MIX_ENV=prod mix pleroma.user new <username> <your@emailaddre
#### Further reading
{! backend/installation/further_reading.include !}
{! installation/further_reading.include !}
{! backend/support.include !}
{! support.include !}

View File

@ -1,6 +1,6 @@
# Installing on Arch Linux
{! backend/installation/otp_vs_from_source_source.include !}
{! installation/otp_vs_from_source_source.include !}
## Installation
@ -214,6 +214,6 @@ sudo -Hu akkoma MIX_ENV=prod mix pleroma.user new <username> <your@emailaddress>
#### Further reading
{! backend/installation/further_reading.include !}
{! installation/further_reading.include !}
{! backend/support.include !}
{! support.include !}

View File

@ -1,12 +1,12 @@
# Installing on Debian Based Distributions
{! backend/installation/otp_vs_from_source_source.include !}
{! installation/otp_vs_from_source_source.include !}
## Installation
This guide will assume you are on Debian 11 (“bullseye”) or later. This guide should also work with Ubuntu 18.04 (“Bionic Beaver”) and later. It also assumes that you have administrative rights, either as root or a user with [sudo permissions](https://www.digitalocean.com/community/tutorials/how-to-add-delete-and-grant-sudo-privileges-to-users-on-a-debian-vps). If you want to run this guide with root, ignore the `sudo` at the beginning of the lines, unless it calls a user like `sudo -Hu akkoma`; in this case, use `su <username> -s $SHELL -c 'command'` instead.
{! backend/installation/generic_dependencies.include !}
{! installation/generic_dependencies.include !}
### Prepare the system
@ -177,6 +177,6 @@ sudo -Hu akkoma MIX_ENV=prod mix pleroma.user new <username> <your@emailaddress>
#### Further reading
{! backend/installation/further_reading.include !}
{! installation/further_reading.include !}
{! backend/support.include !}
{! support.include !}

View File

@ -185,4 +185,4 @@ sudo -Hu akkoma MIX_ENV=prod mix pleroma.user new <username> <your@emailaddress>
#### その他の設定とカスタマイズ
{! backend/installation/further_reading.include !}
{! installation/further_reading.include !}

View File

@ -2,7 +2,7 @@
This document was written for FreeBSD 12.1, but should be work on future releases.
{! backend/installation/generic_dependencies.include !}
{! installation/generic_dependencies.include !}
## Installing software used in this guide
@ -213,4 +213,4 @@ Restart nginx with `# service nginx restart` and you should be up and running.
Make sure your time is in sync, or other instances will receive your posts with
incorrect timestamps. You should have ntpd running.
{! backend/support.include !}
{! support.include !}

View File

@ -1,12 +1,12 @@
# Installing on Gentoo GNU/Linux
{! backend/installation/otp_vs_from_source_source.include !}
{! installation/otp_vs_from_source_source.include !}
## Installation
This guide will assume that you have administrative rights, either as root or a user with [sudo permissions](https://wiki.gentoo.org/wiki/Sudo). Lines that begin with `#` indicate that they should be run as the superuser. Lines using `$` should be run as the indicated user, e.g. `akkoma$` should be run as the `akkoma` user.
{! backend/installation/generic_dependencies.include !}
{! installation/generic_dependencies.include !}
### Your make.conf, package.use, and USE flags
@ -295,6 +295,6 @@ If you opted to allow sudo for the `akkoma` user but would like to remove the ab
#### Further reading
{! backend/installation/further_reading.include !}
{! installation/further_reading.include !}
{! backend/support.include !}
{! support.include !}

View File

@ -1,6 +1,6 @@
# Switching a from-source install to OTP releases
{! backend/installation/otp_vs_from_source.include !}
{! installation/otp_vs_from_source.include !}
In this guide we cover how you can migrate from a from source installation to one using OTP releases.
@ -142,4 +142,4 @@ Refer to [Running mix tasks](otp_en.md#running-mix-tasks) section from OTP relea
## Updating
Refer to [Updating](otp_en.md#updating) section from OTP release installation guide.
{! backend/support.include !}
{! support.include !}

View File

@ -1,6 +1,6 @@
# Installing on NetBSD
{! backend/installation/generic_dependencies.include !}
{! installation/generic_dependencies.include !}
## Installing software used in this guide
@ -204,6 +204,6 @@ incorrect timestamps. You should have ntpd running.
#### Further reading
{! backend/installation/further_reading.include !}
{! installation/further_reading.include !}
{! backend/support.include !}
{! support.include !}

View File

@ -4,7 +4,7 @@ This guide describes the installation and configuration of akkoma (and the requi
For any additional information regarding commands and configuration files mentioned here, check the man pages [online](https://man.openbsd.org/) or directly on your server with the man command.
{! backend/installation/generic_dependencies.include !}
{! installation/generic_dependencies.include !}
### Preparing the system
#### Required software
@ -252,6 +252,6 @@ LC_ALL=en_US.UTF-8 MIX_ENV=prod mix pleroma.user new <username> <your@emailaddre
#### Further reading
{! backend/installation/further_reading.include !}
{! installation/further_reading.include !}
{! backend/support.include !}
{! support.include !}

View File

@ -1,6 +1,6 @@
# Installing on Linux using OTP releases
{! backend/installation/otp_vs_from_source.include !}
{! installation/otp_vs_from_source.include !}
This guide covers a installation using an OTP release. To install Akkoma from source, please check out the corresponding guide for your distro.
@ -235,7 +235,7 @@ At this point if you open your (sub)domain in a browser you should see a 502 err
If everything worked, you should see Akkoma-FE when visiting your domain. If that didn't happen, try reviewing the installation steps, starting Akkoma in the foreground and seeing if there are any errrors.
{! backend/support.include !}
{! support.include !}
## Post installation
@ -300,6 +300,6 @@ This will create an account withe the username of 'joeuser' with the email addre
## Further reading
{! backend/installation/further_reading.include !}
{! installation/further_reading.include !}
{! backend/support.include !}
{! support.include !}

View File

@ -1,3 +1,3 @@
{! backend/installation/otp_vs_from_source.include !}
{! installation/otp_vs_from_source.include !}
This guide covers a from-source installation. To install using OTP releases, please check out [the OTP guide](./otp_en.md).