Centralize configuration and add some new config #494

Merge aplicado
Plume_migration_agent aplicou merge dos 6 commits de config em master 5 anos atrás
Proprietário

Ideally, if someone could review the idea in this comment, I'd like to add the implementation to this pr too

Ideally, if someone could review the idea in [this comment](https://github.com/Plume-org/Plume/issues/273#issuecomment-474982184), I'd like to add the implementation to this pr too
codecov[bot] comentou 5 anos atrás (Migrado de github.com)

Codecov Report

Merging #494 into master will increase coverage by 0.05%.
The diff coverage is 31.74%.

@@            Coverage Diff             @@
##           master     #494      +/-   ##
==========================================
+ Coverage   26.67%   26.72%   +0.05%     
==========================================
  Files          64       65       +1     
  Lines        8713     8741      +28     
==========================================
+ Hits         2324     2336      +12     
- Misses       6389     6405      +16
# [Codecov](https://codecov.io/gh/Plume-org/Plume/pull/494?src=pr&el=h1) Report > Merging [#494](https://codecov.io/gh/Plume-org/Plume/pull/494?src=pr&el=desc) into [master](https://codecov.io/gh/Plume-org/Plume/commit/b945d1f602aba50d2cfdc77eba0742f6e707632b?src=pr&el=desc) will **increase** coverage by `0.05%`. > The diff coverage is `31.74%`. ```diff @@ Coverage Diff @@ ## master #494 +/- ## ========================================== + Coverage 26.67% 26.72% +0.05% ========================================== Files 64 65 +1 Lines 8713 8741 +28 ========================================== + Hits 2324 2336 +12 - Misses 6389 6405 +16 ```
elegaanz (Migrado de github.com) revisou 5 anos atrás
elegaanz (Migrado de github.com) comentou 5 anos atrás

Not really related, but I'm thinking about it because I'm seeing it: shouldn't we drop this setting and force people to set up HTTPS? I introduced it to make it easier to develop locally, but now this requires HTTPS too because of CSRF.

Not really related, but I'm thinking about it because I'm seeing it: shouldn't we drop this setting and force people to set up HTTPS? I introduced it to make it easier to develop locally, but now this requires HTTPS too because of CSRF.
@ -115,38 +127,14 @@ Then try to restart Plume.
})
elegaanz (Migrado de github.com) comentou 5 anos atrás

Isn't there a way to use the Config struct from rocket directly in our config module instead of RocketConfig?

Isn't there a way to use the `Config` struct from rocket directly in our `config` module instead of `RocketConfig`?
trinity-1686a revisou 5 anos atrás
@ -115,38 +127,14 @@ Then try to restart Plume.
})
Autor
Proprietário

RocketConfig could become a Result<rocket::Config> (Result to denote when there was an error creating the Config, or when there is no secret key). I through of it at some point, but did not remember what I wanted to do when I was about to commit

`RocketConfig` could become a `Result<rocket::Config>` (Result to denote when there was an error creating the Config, or when there is no secret key). I through of it at some point, but did not remember what I wanted to do when I was about to commit
trinity-1686a revisou 5 anos atrás
Autor
Proprietário

We should probably, http does not work well anyway

We should probably, http does not work well anyway
trinity-1686a revisou 5 anos atrás
Autor
Proprietário

As someone on Matrix said they were using Plume on a Tor Hidden Service, I tried to see if this won't cause any CSRF issues, and apparently Tor Browser consider hidden service to be secure even without https, that's nice

As someone on Matrix said they were using Plume on a Tor Hidden Service, I tried to see if this won't cause any CSRF issues, and apparently Tor Browser consider hidden service to be secure even without https, that's nice
elegaanz (Migrado de github.com) aprovou estas alterações 5 anos atrás
elegaanz (Migrado de github.com) deixou um comentário

Looks good. Thanks. 😊

Looks good. Thanks. :blush:
Autor
Proprietário

It was incomplete >_<

It was incomplete >_<
elegaanz comentou 5 anos atrás (Migrado de github.com)

Sorry… I didn't saw you added the "Incomplete" label… 🤦‍♀️

Sorry… I didn't saw you added the "Incomplete" label… :woman_facepalming:
Autor
Proprietário

No worries, I made another pr with what I wanted to add

No worries, I made another pr with what I wanted to add
khimaros (Migrado de github.com) revisou 5 anos atrás
khimaros (Migrado de github.com) deixou um comentário

Would be rad if 'plm' honored this config as well. Fortunately, easy to workaround with command line flag.

Would be rad if 'plm' honored this config as well. Fortunately, easy to workaround with command line flag.
Autor
Proprietário

@khimaros you can open an issue with what you think would be a better comportment 😉

@khimaros you can open an issue with what you think would be a better comportment :wink:

Revisores

O pull request teve merge aplicado como 65bb50e88f.
Você também pode ver as instruções para a linha de comandos.

Passo 1:

No repositório do seu projeto, crie um novo branch e teste as alterações.
git checkout -b config master
git pull origin config

Passo 2:

Faça merge das alterações e atualize no Forgejo.
git checkout master
git merge --no-ff config
git push origin master
Acesse para participar desta conversação.
Sem revisor
Sem marco
Sem responsável
2 participante(s)
Notificações
Data limite
A data limite é inválida ou está fora do intervalo. Por favor, use o formato 'dd/mm/aaaa'.

Data limite não informada.

Dependências

Nenhuma dependência definida.

Referência: Plume/Plume#494
Carregando…
Ainda não há conteúdo.