New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Selfhosted version improvements #89
Conversation
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
…testing Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Gitlab Migration: Adding test stage See merge request tckb-public/plausible!1
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Added Dockerfile and cleaned up configurations See merge request tckb-public/plausible!2
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Adding overlay scripts for Db migration on release artifacts See merge request tckb-public/plausible!3
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
Resolve "Cosmetic changes to self-hosted version" Closes plausible#20 See merge request tckb-public/plausible!25
- added ability for disabling - authentication completely - registration - landing page - formatting cleanups
Improvements to selfhosting setup See merge request tckb-public/plausible!26
- added ability for disabling - authentication completely - registration - landing page - formatting cleanups
added test cases See merge request tckb-public/plausible!27
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Thanks for the huge work 💚 💙 💜 💛 ❤️
The only change I'd like to see is to remove the DISABLE_LANDING_PAGE
variable. Some context: the /
route is never hit in the cloud version of Plausible. We started out with it as the landing page but now we're running a static site in front of the app server with a reverse proxy. The static site shadows the /
route to serve the landing page.
This means the /
route is not even relevant to our cloud deployment. In a self-hosted scenario, its should probably:
- Redirect to
/login
if the user is not logged in - Redirect to
/sites
if the user is logged in
Seems like that's what the DISABLE_LANDING_PAGE
already does so you could just remove the env variable do it unconditionally.
I thought about that, but since it being a opensource, I do not want to rule out a possibility that someone with a fork want to customize the landing page and would still want have a landing page. we can set this variable to true by default. I would probably would want to customize it somehow -- What do you think ? |
I still don't see much reason to keep it tbh. If someone has a fork and they're adding code for a landing page, it shouldn't be a big ask to also change the Instead of referencing an old landing page we don't use anymore, it would be better to reference the code for our live landing page. The main reason I want to remove it is because our CSS is compiled based on the classes used in the actual HTML templates. By removing the landing page we remove some of Tailwind's CSS classes from being included in the final build. This would make the whole app lighter. |
Okay, I agree on the size part. So removing the templates at https://github.com/plausible/analytics/tree/master/lib/plausible_web/templates/page would suffice right? |
Yeah, and changing the controller to redirect based on the login state here: |
This is already handled by auto_auth_plug. I will remove unnecessary assets and templates to needed for self-hosting |
Cool 👍 I will merge once those are removed |
One more thing, let's make the landing page disabled by default. |
If I remove the template, then there wouldn't be any landing page :P I am not sure if I understand this correctly |
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
…ter' Resolve "Remove landing page and unsed templates" Closes plausible#21 See merge request tckb-public/plausible!28
Signed-off-by: Chandra Tungathurthi <tckb@tgrthi.me>
…ter' More fixes and addressing PR comments Closes plausible#21 See merge request tckb-public/plausible!29
This PR will address some of the concerns raised during the self-hosted versions:
closes #26, closes #85, closes #86, closes #88, closes #133
Joken
dependenc