trying to install plume via docker following instructions database cannot connect

root@xxxxxxxxxxxxx:~/plume# docker-compose run --rm plume plm migration run
Creating plume_plume_run ... done
Configuration read from /app/.env
thread 'main' panicked at 'Couldn't connect to the database.: BadConnection("FATAL:  password authentication failed for user \"plume\"\n")', plume-cli/src/main.rs:35:40

Refers to /app/.env but docker exec -it <container> bash reveals no file .env or directory /app

When publishing an article, it gets duplicated in timelines after some time.

It looks like duplication happens every time someone likes or boosts the post (from the same instance, or from another one), but I'm not 100% sure.

• Plume version: 0.4.0
• Operating system: Linux, but not relevant IMO
• Web Browser: Firefox Nightly, but not relevant either

Hi I would like to upgrade without git as mentioned here https://github.com/Plume-org/Plume/blob/master/docs/UPDATE.md.

So I would like to :

1. Backup the important files and folders like .env, etc.
2. Delete the the source folder
3. Download and decompress the fresh sources to the folder.
4. Restore the importation files and folders like .env to the new unpacked sources.

So for this I would like to know what files and folders are needed to be backed up and needs to be restored to the newly unpacked sources, so that the Plume don't break.

When I like or boost a post (on the same instance), it just takes me to a domain.com/posturl/{like,boost} url, which is just a blank page. When I reload the blog's page, the like or boost count still remains at 0, and it seems I haven't affected anything.

Plume version (and/or commit): 61b6ceed92ef838a085da6eb66f87ab1de65a520

During compile on arm64v8 the following error surfaces during the final step (looks like linking). From what I can tell rust-crypto is no longer maintained and won't be receiving a fix (see https://github.com/DaGenix/rust-crypto/issues/383 for reference).

I'm not familiar with the rust toolchain and this seems like Plume or one of it's dependencies has a dependency on the legacy rust-crypto library. Is there a way to track this down and/or update the code to avoid rust-crypto popping up in the dependency graph?

I bring this up because a Raspberry Pi 3, Orange Pi, Scaleway arm VPSs and Amazon arm VPSs are all cheap, easy to obtain and can be used for self hosting yet are all arm64v8 devices/servers.

warning: struct is never constructed: `Write`                                                                                                                                                                                          
  --> src/api/authorization.rs:19:1                                                                                                                                                                                                    
   |                                                                                                                                                                                                                                   
19 | pub struct Write;                                                                                                                                                                                                                 
   | ^^^^^^^^^^^^^^^^^                                                                                                                                                                                                                 
   |                                                                                                                                                                                                                                   
   = note: #[warn(dead_code)] on by default                                                                                                                                                                                            
                                                                                                                                                                                                                                       
error: linking with `cc` failed: exit code: 1                                                                                                                                                                                          
  |                                             
[snip]



  = note: /app/target/debug/deps/libcrypto-0e2d8e020a3b8dff.rlib(crypto-0e2d8e020a3b8dff.crypto.277lu5c6-cgu.12.rcgu.o): In function `crypto::util::fixed_time_eq':
          /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rust-crypto-0.2.36/src/util.rs:52: undefined reference to `rust_crypto_util_fixed_time_eq_asm'
          collect2: error: ld returned 1 exit status
          

error: aborting due to previous error

error: failed to compile `plume v0.2.0 (/app)`, intermediate artifacts can be found at `/app/target`

I'm tying to package plume into Arch Linux with files show below

./etc/plume/config
./usr/share/licenses/plume/LICENSE
./usr/lib/systemd/system/plume.service
./usr/lib/sysusers.d/plume.conf
./usr/lib/plume/
./usr/bin/plume
./usr/bin/plm

Here is the systemd file:

[Unit]
Description=plume

[Service]
Type=simple
User=plume
ExecStart=/usr/bin/plume
EnvironmentFile=/etc/plume/config
WorkingDirectory=/usr/lib/plume
TimeoutSec=30
Restart=always

[Install]
WantedBy=multi-user.target

And here are some of my questions:

1. Is it possible to build a plume with 2 database backend including pg and sqlite, I found with enable all features, plume-cli will refuse to compile
2. What should be packaged into a working dir in /usr/lib/plume? After I run plume with systemd, I failed to run database migration with `Unable to find migrations directory in this directory or any parent directories.

• Plume version: 0.3.0-alpha-2
• Operating system: Arch Linux
• Web Browser: Firefox Here is the pkgbuild

We now have a type that routes an activity through the registered handlers until one of them matches.

Each Actor/Activity/Object combination is represented by an implementation of AsObject

These combinations are then registered on the Inbox type, which will try to deserialize the incoming activity in the requested types.

Advantages:

• nicer syntax: the final API is clearer and more idiomatic
• more generic: only two traits (AsActor and AsObject) instead of one for each kind of activity
• we always try to dereference unknown objects
• it is easier to see which activities we handle and which one we don't

(sorry for the big diff once again :confused:)

What is happening

In the docs provided, it says to create a .env file in the place where you built Plume. From following the instructions, I think that this location is /home/plume/Plume/.env but am unsure. With all my variables in this file, when I run any command, i.e. plm migration run it says that the database cannot be connected to. So, when I add the DATABASE_URL in front of these commands, it works just fine.

What I need help with

Where, exactly, given that I am running Plume with a dedicated user named "plume" and have compiled from source for Ubuntu 16.04, do I put my .env file so that Rust? Plume? app can read these variables without me having to put them all in an extremely long argument to launch and run Plume?

My system

Arguments used to install Plume

# Install Rust first...
curl https://sh.rustup.rs -sSf | sh

# Git latest version
git clone https://github.com/Plume-org/Plume.git
cd Plume

# Next Build the front-end
cargo install cargo-web&&cargo web deploy -p plume-front

# Build the back-end, replacing DATABASE either with postgres or sqlite
cargo install --no-default-features --features postgres --force&&cargo install --no-default-features --features postgres --path plume-cli --force

Other items

1. Ubuntu 16.04
2. PostgresSQL

Good to knows

My instance actually works, I just want to be able to use the "configuration" file the way it was meant to be used. I am using custom logo, that works, email server, that works, and would like to use custom port (not 7878). Thanks for all your help and for creating Plume!

There are many cases in which (at least in Persian language) a tag may include space(s). Currently, Plume removes space from tags. Look at the following screenshots to see what is entered as tag and how it is damaged in output;

• Plume version: 0.4.0

• Custom CSS for blogs
• Custom themes for instance
• New dark theme
• UI for admin to upload new theme (or delete them)
• UI to choose your theme

Instance level themes are just CSS files, stored in static/css (see Instance::list_themes).

TODO:

• [x] Federate blog themes
• [x] Escape url()/import
• [x] Add a way to avoid conflicts between blog and instance themes
• [x] UI to disable blog CSS (the option is already in the database, just need to add a checkbox in the settings)
• [x] SQlite migrations
• [x] Documentation

Fixes #354, #403

So far:

• Ligther colors
• No more border radius
• Buttons are now always colored
• Fix weird margin with CWed images
• Add a border to quotes
• Start to redesign the post page (according to the Figma mockups)
  • Full-size cover image, with a gradient and the title/subtitle/authors/date over it
  • Like/boost are now between tags and author info
  • Author info has a difference background color to make a difference between the different sections
  • Tags and license are now side-by-side

As I started it, this redesign is not perfectly following what was done on Figma (for instance lighter colors were not planned), but I'm open to discussion if you think Figma mockups should be better respected.

It is available at https://pr-553.joinplu.me/ if you want to see how it looks like. You can login with admin/admin123 to see all the pages.

error[E0107]: this trait takes 0 generic arguments but 1 generic argument was supplied
   --> plume-common/src/activity_pub/mod.rs:412:6
    |
412 | impl Extends<HashtagType> for Hashtag {
    |      ^^^^^^^------------- help: remove these generics
    |      |
    |      expected 0 generic arguments
    |
note: trait defined here, with 0 generic parameters
   --> /home/plume/.cargo/registry/src/github.com-1ecc6299db9ec823/activitystreams-0.7.0-alpha.22/src/base.rs:41:11
    |
41  | pub trait Extends: Sized {
    |           ^^^^^^^

For more information about this error, try `rustc --explain E0107`.
error: could not compile `plume-common` due to previous error
warning: build failed, waiting for other jobs to finish...
error: failed to compile `plume-cli v0.7.2 (/home/plume/Plume/plume-cli)`, intermediate artifacts can be found at `/home/plume/Plume/target`

Locking activitystreams version can fix this, for example, activitystreams = "=0.7.0-alpha.20" (the version in Cargo.lock

NOTE: Plume's Gitea instance does not seem to send emails so it is impossible to activate my account, even via github's account linking process.

After having banned my first user, Plume fails to start. Plume fails to start with the following message:

sept. 16 17:36:36 web-01 plume[715590]: Configuration read from /var/www/plumeblog/.env
sept. 16 17:36:38 web-01 plume[715590]: thread 'main' panicked at 'Failed to cache local instance user: Blocklisted(false, "")', plume-models/src/instance.rs:115:18
sept. 16 17:36:38 web-01 plume[715590]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I checked the database and I don't see anything weird

With backtrace:

# RUST_BACKTRACE=1 plume
Configuration read from /var/www/plumeblog/.env
thread 'main' panicked at 'Failed to cache local instance user: Blocklisted(false, "")', plume-models/src/instance.rs:115:18
stack backtrace:
   0: rust_begin_unwind
             at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panicking.rs:577:5
   1: core::panicking::panic_fmt
             at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/core/src/panicking.rs:135:14
   2: core::result::unwrap_failed
             at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/core/src/result.rs:1737:5
   3: once_cell::imp::OnceCell<T>::initialize::{{closure}}
   4: once_cell::imp::initialize_or_wait
   5: once_cell::imp::OnceCell<T>::initialize
   6: plume_models::instance::Instance::cache_local_instance_user
   7: plume::init_rocket
   8: plume::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

With full backtrace:

# RUST_BACKTRACE=full plume
Configuration read from /var/www/plumeblog/.env
thread 'main' panicked at 'Failed to cache local instance user: Blocklisted(false, "")', plume-models/src/instance.rs:115:18
stack backtrace:
   0:     0x555c0275509c - std::backtrace_rs::backtrace::libunwind::trace::h9c95184963fef745
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:     0x555c0275509c - std::backtrace_rs::backtrace::trace_unsynchronized::h5d21f8fdfc262588
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x555c0275509c - std::sys_common::backtrace::_print_fmt::h6ce732896d3b7bc2
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/sys_common/backtrace.rs:67:5
   3:     0x555c0275509c - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h56a1b948079bb60c
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/sys_common/backtrace.rs:46:22
   4:     0x555c0277d35c - core::fmt::write::ha787ab3b9068d913
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/core/src/fmt/mod.rs:1168:17
   5:     0x555c0274cbe3 - std::io::Write::write_fmt::h4913c71f24efdd75
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/io/mod.rs:1653:15
   6:     0x555c02757a62 - std::sys_common::backtrace::_print::h8ba799ac9853e240
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/sys_common/backtrace.rs:49:5
   7:     0x555c02757a62 - std::sys_common::backtrace::print::hc1060288e0e5dcfe
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/sys_common/backtrace.rs:36:9
   8:     0x555c02757a62 - std::panicking::default_hook::{{closure}}::h5623b336a8b38b2c
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panicking.rs:290:50
   9:     0x555c02757645 - std::panicking::default_hook::h7f9b0932f349911f
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panicking.rs:307:9
  10:     0x555c02758114 - std::panicking::rust_panic_with_hook::h87cab73890184b28
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panicking.rs:691:17
  11:     0x555c02757df7 - std::panicking::begin_panic_handler::{{closure}}::h541a05bf9df15ade
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panicking.rs:581:13
  12:     0x555c02755544 - std::sys_common::backtrace::__rust_end_short_backtrace::h18b7b64c8e3dc986
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/sys_common/backtrace.rs:139:18
  13:     0x555c02757b09 - rust_begin_unwind
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panicking.rs:577:5
  14:     0x555c018f85c3 - core::panicking::panic_fmt::h1720bda5e8269e46
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/core/src/panicking.rs:135:14
  15:     0x555c018f86b3 - core::result::unwrap_failed::hf939f97f1c5ed232
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/core/src/result.rs:1737:5
  16:     0x555c01c70ffc - once_cell::imp::OnceCell<T>::initialize::{{closure}}::ha04c87d9b0aab204
  17:     0x555c027211d3 - once_cell::imp::initialize_or_wait::hdecf96bf5a9a1e0d
  18:     0x555c018bb382 - once_cell::imp::OnceCell<T>::initialize::he036ea8628b8ab4f
  19:     0x555c01da3943 - plume_models::instance::Instance::cache_local_instance_user::h4e82f81de694932e
  20:     0x555c01a8f103 - plume::init_rocket::hf7a3a1c15d8aeb08
  21:     0x555c01a97b47 - plume::main::h60ab4c229ca636c9
  22:     0x555c01a32893 - std::sys_common::backtrace::__rust_begin_short_backtrace::hb0706cfb5e0d1bbe
  23:     0x555c01b884f9 - std::rt::lang_start::{{closure}}::h91ffb41cf926ee9a
  24:     0x555c02754757 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::hce9a5e26b1a2c58c
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/core/src/ops/function.rs:259:13
  25:     0x555c02754757 - std::panicking::try::do_call::h6c2996a203e8e883
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panicking.rs:485:40
  26:     0x555c02754757 - std::panicking::try::hb55cfc029aa1d1ae
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panicking.rs:449:19
  27:     0x555c02754757 - std::panic::catch_unwind::h9d5a29e8020cfa03
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panic.rs:136:14
  28:     0x555c02754757 - std::rt::lang_start_internal::{{closure}}::h3aef114df9bcaef3
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/rt.rs:128:48
  29:     0x555c02754757 - std::panicking::try::do_call::ha59134c701ee03a3
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panicking.rs:485:40
  30:     0x555c02754757 - std::panicking::try::h5a79ced7a6a77bd0
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panicking.rs:449:19
  31:     0x555c02754757 - std::panic::catch_unwind::h580b9b0c2eacfaaf
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/panic.rs:136:14
  32:     0x555c02754757 - std::rt::lang_start_internal::ha11525fb3cb33455
                               at /rustc/6abb6385b2cb7249f67b9b3ce7522527767dd907/library/std/src/rt.rs:128:20
  33:     0x555c01aaed12 - main
  34:     0x7fbbb7b6dd0a - __libc_start_main
  35:     0x555c018f8d9a - _start
  36:                0x0 - <unknown>

My .env file:

# cat /var/www/plumeblog/.env 
# The address of the database
# (replace USER, PASSWORD, PORT and DATABASE_NAME with your values)
#
# If you are using SQlite, use the full path of the database file (`plume.db` for instance)
# Windows user's paths are backslashes, change them to forward slashes
#DATABASE_URL=/etc/path/to/Plume/plume.db
DATABASE_URL=postgres://(myuser):(mypasswd)[email protected]:5432/plumeliberta

# For PostgreSQL: migrations/postgres
# For SQlite: migrations/sqlite
MIGRATION_DIRECTORY=migrations/postgres

# The domain on which your instance will be available
BASE_URL=blog.liberta.vip

# Secret key used for private cookies and CSRF protection
# You can generate one with `openssl rand -base64 32`
ROCKET_SECRET_KEY=(mykey)

# Mail settings
# If you don't want to setup a mail server and/or address for plume
# and don't plan to use the "password reset" feature,
# you can comment these lines.
MAIL_SERVER=mail.gandi.net
MAIL_USER=(myemail)
MAIL_PASSWORD=(mypass)
MAIL_HELO_NAME=mail.gandi.net
MAIL_ADDRESS=(myemail)

• Plume version: Latest dev version and latest release both have the same behaviour
• Operating system: Debian 11 (bullseye)
• Web Browser: Firefox (Debian 11)

Some articles with titles containing certain symbols such as "/" or "[]" might return error.

For example: https://plume.pullopen.xyz/~/Inspirations-T%C3%A4uschungen/%E5%9B%A0%E7%82%BA%E4%B8%80%E5%88%87%E5%BF%AB%E6%A8%82%E8%A6%81%E6%B1%82%E6%B0%B8%E6%81%86%20%5B%E2%85%A0%5D with a "[" and "]" in it.

and: https://plume.pullopen.xyz/~/%E5%A4%A7%E6%B5%B7%E8%B4%BC%E5%92%8C%E4%BB%96%E4%BB%AC%E7%9A%84%E5%B4%BD%E5%B4%BD/%E3%80%90%E6%B5%B7%E8%B4%BC%E7%8E%8B%2F%E4%BA%B2%E5%AD%90%E5%90%91%E3%80%91%E6%88%90%E9%95%BF%E7%97%9B with a "/" in it.

• Plume version: 0.7.3 - dev
• Operating system: windows
• Web Browser: firefox

Is your feature request related to a problem? Please describe. I notice that after a while, the search_index and database file grows bigger and bigger, filled with remote article that we usually do not need or understand, and taking too much disk space.

Describe the solution you'd like I would like to have a plm order to purge remote content as well as the related search index.

Describe alternatives you've considered Or would you please give me some instruction?

Is your feature request related to a problem? Please describe. the site can't be searched by google

Describe the solution you'd like update sitemap.xml hourly or daily

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

1. Other replies my plume article from mastodon.
2. I can see the reply under my article, but it doesn't show in notification.
3. When someone replies as plume user, I can see the notification in plume.

Would you be able to figure it out?

• Plume version: 0.7.3-dev
• Operating system: Windows
• Web Browser: Firefox