proxy support #829
Sem revisor
Etiquetas
Nenhum rótulo
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Sem marco
Sem projeto
Sem responsáveis
2 participantes
Notificações
Data limite
Não há data limite definida.
Dependências
Não há dependências definidas.
Referência: Plume/Plume#829
Carregando…
Adicionar tabela
Referência em uma nova issue
Nenhuma descrição fornecida.
Excluir branch "dr-bonez/Plume:feature/proxy"
Apagar um branch é permanente. Ainda que o branch apagado possa continuar a existir por um breve período antes de ser realmente apagado, isso NÃO PODE ser desfeito na maioria dos casos. Continuar?
Adds support for using a proxy for federation.
Motivation is for being able to support homeservers running as Tor hidden services.
Threading config information into plume-common is the only reason this pr isn't very low impact.
Thank you for pull request and sorry for late reply. But we have less time to review, now. Can you wait for a while, please? Thanks.
Sorry for very late reply.
What need proxy config is only
ClientBuilder
. How about to useCONFIG.proxy()
directly inplume-common/src/activity_pub/mod.rs
?I can't. CONFIG comes from plume-models, which has plume-common as a dependency. Pretty sure you can't have 2 crates that depend on each other.
rebased
Okay, I will merge. Thank you for your work!
Okay, I will merge. Thank you for your work!