docs issueshttps://git.pleroma.social/pleroma/docs/-/issues2023-11-09T13:54:24Zhttps://git.pleroma.social/pleroma/docs/-/issues/11Dependency Dashboard2023-11-09T13:54:24Zrenovate-botDependency DashboardThis issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
This repository currently has no open or pending branches.
## Detect...This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
This repository currently has no open or pending branches.
## Detected dependencies
<details><summary>gitlabci</summary>
<blockquote>
<details><summary>.gitlab-ci.yml</summary>
</details>
</blockquote>
</details>
<details><summary>pipenv</summary>
<blockquote>
<details><summary>Pipfile</summary>
</details>
</blockquote>
</details>https://git.pleroma.social/pleroma/docs/-/issues/10robots.txt generation doesn't work2023-11-09T09:01:21ZAltarof Patatoesrobots.txt generation doesn't workHi, on a recently installed instance (OTP on Debian), I wanted to disable search engines indexing, I followed the procedure here : https://docs-develop.pleroma.social/backend/administration/CLI_tasks/robots_txt/ but it doesn't work:
```
...Hi, on a recently installed instance (OTP on Debian), I wanted to disable search engines indexing, I followed the procedure here : https://docs-develop.pleroma.social/backend/administration/CLI_tasks/robots_txt/ but it doesn't work:
```
# su pleroma -s $SHELL -lc "./bin/pleroma_ctl robots_txt disallow_all"
The task robots_txt does not exist
```
I discovered that the actual command seems to be instead:
`su pleroma -s $SHELL -lc "./bin/pleroma_ctl robotstxt disallow_all"`
I would have proposed a patch to the doc directly, but I couldn't figure how to do that, being not that familiar with git/gitlab.https://git.pleroma.social/pleroma/docs/-/issues/9Consider using Renovate bot?2023-01-23T21:52:07ZSean KingConsider using Renovate bot?From the looks of it, Renovate bot does support Python package managers, including `pipenv`: https://docs.renovatebot.com/python/From the looks of it, Renovate bot does support Python package managers, including `pipenv`: https://docs.renovatebot.com/python/https://git.pleroma.social/pleroma/docs/-/issues/8Add a reply/interact feature for replying from other instances.2023-11-09T09:01:46ZGwynneAdd a reply/interact feature for replying from other instances.Like the follow button, it asks for your username and redirects you to your own instance. please add this feature so users can easily reply without copying the link and then commenting in their instance.
I was trying to add this feature...Like the follow button, it asks for your username and redirects you to your own instance. please add this feature so users can easily reply without copying the link and then commenting in their instance.
I was trying to add this feature in where you can add comments in your static website with just a mastodon [source link](https://carlschwan.eu/2020/12/29/adding-comments-to-your-static-blog-with-mastodon/), I was trying to use pleroma for this. which obviously it wouldn't work without altering the code, but pleroma as no "interact" feature so that makes this impossible to do.https://git.pleroma.social/pleroma/docs/-/issues/7Instructions about pre-generating keys manually / automated deploys2020-07-23T13:01:50ZRaphael LullisInstructions about pre-generating keys manually / automated deploysI am working on an ansible role for deploying pleroma and it would be great to be able to separate the task of installing packages from the configuration ("instance gen") procedures.
I know that I can generate the vapid keys by myself (...I am working on an ansible role for deploying pleroma and it would be great to be able to separate the task of installing packages from the configuration ("instance gen") procedures.
I know that I can generate the vapid keys by myself (at least I used the js web-push package), and of course things like database password are easy to be defined by the admins. The things that were not clear were regarding how the secret key / signing salt are generated. Are they just independent random strings, or is there something else?
Similar question goes to the "joken" signer_key. How is it generated?https://git.pleroma.social/pleroma/docs/-/issues/6Add a document about Pleroma.Upload.Filter.Mogrifun filter2020-05-24T09:31:23ZKaede FujisakiAdd a document about Pleroma.Upload.Filter.Mogrifun filterI found that there is a `Mogrifun` filter in [here](https://git.pleroma.social/pleroma/pleroma/-/blob/develop/lib/pleroma/upload/filter/mogrifun.ex), but I can't the docs about this filter in the [document](https://docs-develop.pleroma.s...I found that there is a `Mogrifun` filter in [here](https://git.pleroma.social/pleroma/pleroma/-/blob/develop/lib/pleroma/upload/filter/mogrifun.ex), but I can't the docs about this filter in the [document](https://docs-develop.pleroma.social/backend/configuration/cheatsheet/#upload-filters) yet.https://git.pleroma.social/pleroma/docs/-/issues/5Add HOWTO for setting up panel and tos2020-03-11T14:25:40ZMartinAdd HOWTO for setting up panel and tos~~~gherkin
Feature: Pleroma FE personalize TOS and Panel text
As an administrator of a Pleroma instance
I'd like to change the texts of the side panel and the terms of services
to add specific instance information or a data privacy state...~~~gherkin
Feature: Pleroma FE personalize TOS and Panel text
As an administrator of a Pleroma instance
I'd like to change the texts of the side panel and the terms of services
to add specific instance information or a data privacy statement
~~~
## Implementation
Add the following text somewhere to the documentation:
## Adapt Sidepanel text and Terms of Service
First make shure, that your static dir is set right
- If you are running the database driven config, adapt it in the Admin Pannel -> Settings -> Instance -> Static dir, e.g. set it to `/var/lib/pleroma/static`.
- If you are running the file based config, set this to your `/etc/pleroma/config.exs`:
~~~elixir
config :pleroma, :instance, static_dir: "/var/lib/pleroma/static"
~~~
Check, that this directory exists and has the needed subdirectories:
~~~sh
mkdir -p /var/lib/pleroma/static/instance
mkdir -p /var/lib/pleroma/static/static
~~~
Now add html stubs to both files, the panel text and to the terms of service. Here is an example text, with adapted margin. You should later adapt both text files to your needs, first the side panel, which should be the smaller one of both texts and will only show up, if you have the site specific panel switched on in the configuration settings.
Edit /var/lib/pleroma/static/instance/panel.html and add:
~~~html
<div style="margin:12px;">
<h1>Hello</h1>
<p>This is my Pleroma instance. I do not provide commercial services. See here for <a href="/about">data privacy statement</a>.</p>
</div>
~~~
After this edit /var/lib/pleroma/static/static/terms-of-service.html and add:
~~~html
<div style="margin:12px;">
<h1>Terms of Service</h1>
<p>Here you find my terms of service and below my data privacy statement</p>
<p>yes, you will have to write it. :-)</p>
</div>
~~~
This and other information will be shown, if you call your `/about` page of your site.
Now set the right permissions for all files and directories:
~~~sh
chown -R pleroma:pleroma /var/lib/pleroma/static
~~~
Finally you are ready to load your Pleroma Frontend in your Browser. **Attention**: If you don't see the change immediately when pressing F5, the browser may have cached the files, so you need to flush your browser cahe in the browser settings and reload again.https://git.pleroma.social/pleroma/docs/-/issues/4Provide a link to the main site2020-03-08T14:04:32ZHaelwennProvide a link to the main siteLooking at the nav bar I'm not so sure where this link should be as IMO it should either be at the right or at the left of it.
Maybe the link to the repository could be moved to the pages themselves? I think it should make more sense si...Looking at the nav bar I'm not so sure where this link should be as IMO it should either be at the right or at the left of it.
Maybe the link to the repository could be moved to the pages themselves? I think it should make more sense since it changes depending on where you are.https://git.pleroma.social/pleroma/docs/-/issues/3broken link in frontend docs2020-03-08T14:02:21Zjellypotatobroken link in frontend docsThe first hyperlink in https://docs-develop.pleroma.social/frontend/CONFIGURATION#where-configuration-is-stored points to a 404 page: https://docs-develop.pleroma.social/config.html#frontend_configurationsThe first hyperlink in https://docs-develop.pleroma.social/frontend/CONFIGURATION#where-configuration-is-stored points to a 404 page: https://docs-develop.pleroma.social/config.html#frontend_configurationshttps://git.pleroma.social/pleroma/docs/-/issues/2TOC: Add uncollapse/collapse all buttons2019-11-20T19:23:17Zrinpatchrin+pleroma@patch.cxTOC: Add uncollapse/collapse all buttonsSome users are complaining about having to click through too many buttons to get to the file they need, but uncollapsing everything isn't a good idea either because most users will get overwhelmed with the amount of files. Thus we need a...Some users are complaining about having to click through too many buttons to get to the file they need, but uncollapsing everything isn't a good idea either because most users will get overwhelmed with the amount of files. Thus we need an uncollapse all button as a compromisehttps://git.pleroma.social/pleroma/docs/-/issues/1Version toggle2020-03-10T18:22:34Zrinpatchrin+pleroma@patch.cxVersion toggleThis would require some modifications to mkdocs because it doesn't support them natievlyThis would require some modifications to mkdocs because it doesn't support them natievly2.1