Self-hosted front page

[michel.c...@gmail.com]

Hi there,

Is there a way to set the login page as default front page instead of the discovery page. 

I did switch to false publicRegisterEnabled in ~/taiga-front-dist/dist/conf.json and PUBLIC_REGISTER_ENABLED in ~/taiga-back/settings/local.py and visitors now can't register them self but it's still the discover page that appear first when I'd rather have the login page appear first and stick there until login.  

So if user isn't connected, redirect every request to login page!

Thanks.

[Alejandro Alonso]

Hello Michel,

I'm sorry but there is no way to disable discover page, public projects will always appear on that section. Probably you could tweak your nginx configuration so users get redirected to /login when accessing to /discover but it will be a bit strange for logged in users when they access to /discover.

Regards,

--
Please help us keep the Taiga.io Community open and inclusive, follow our Code of Conduct:
https://github.com/taigaio/code-of-conduct/blob/master/CODE_OF_CONDUCT.md
---
You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/4f153bd8-bbf4-406d-a129-32382ccd9ec9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alejandro Alonso Fernández CIO & Co-founder alejandr...@kaleidos.net  | Tel: (+34) 627263808 | (+34) 913562995 www.kaleidos.net/FC8EAC/

[Michel Chouinard]

Hello Alejandro,

I'm sorry to read this...  I believe that on a self-hosted setup we should be able to decide who have access to our service.  My Taiga setup is for my team, clients and me...  Most projects will be private, client A doesn't have to know the progress on client's B projects and vice versa...  But some projects could be public to all my clients, team and me once connected to the site...  Right now, if a project is public it's readable even by any visitors that stumble on my Taiga...

For now I'll keep that in mind and set all projects private but invite whom it concern...  More management...

[Alejandro Alonso]

Hello Michel,

 

I'm sorry to read this...  I believe that on a self-hosted setup we should be able to decide who have access to our service.  My Taiga setup is for my team, clients and me...  Most projects will be private, client A doesn't have to know the progress on client's B projects and vice versa...  But some projects could be public to all my clients, team and me once connected to the site...  Right now, if a project is public it's readable even by any visitors that stumble on my Taiga...

For now I'll keep that in mind and set all projects private but invite whom it concern...  More management...

Yes, right now it's the only way, if you don't want any external user can access to any project all of them must be private.

Regards, 

[nictra...@gmail.com]

Hello,

Sorry to Necro, but its very important that this gets fixed. I actually can't use this in my company due to legal concerns because we have no way to disable discover. Please consider adding a flag to disable this behavior.

[David Barragán]

Hi all,

The important thing is not to disable "discover". If you want that nobody can see the data of a project, it must be private. Even if you can't access to the discover page, you can still see the project data, through the project homepage in the browser or directly with the Taiga API.

You can control which user can create public projects in the superadmin panel and set the dafault number to 0 in settings/local.py (https://github.com/taigaio/taiga-back/blob/master/settings/local.py.example#L120) 

Regards

--

Please help us keep the Taiga.io Community open and inclusive, follow our Code of Conduct:
https://github.com/taigaio/code-of-conduct/blob/master/CODE_OF_CONDUCT.md
---
You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/856c3387-6fa9-471c-b58d-9500e94d0bbe%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

David Barragán Merino   Engineer david.b...@kaleidos.net  | Tel: (+34) 913562995 www.kaleidos.net/FFF8E7

[nictra...@gmail.com]

Thank you for expanding on the issues, but knowing about them does not fix them.

Hear me out here - even if I disable the ability for people to create public projects, a member of my board (who are not super technical) will go to taiga, see this "discover" thing and start questioning me on the security of the platform. When I tell them that I've disabled the ability to create public projects, they're going to ask me "But why did you use an application that is insecure by default? I don't think we can trust developers who treat principle of least privilege with such disregard."

I'd rather not fight that battle - so if you could add in a simple config option, it would save the ass of many an IT guy.

[Stefan Mueller]

Hello,

I'm right that this problem still exists?

stefan

[Alex Hermida]

Hello Stefan!

Yes. However, Its something we'll include in incoming changes in the next or following minor release.

Best.

To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/ac2c715a-eb0c-4351-a11a-2f8cbb36e219%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Alex Hermida
https://alexhermida.dev/

[Joseph Harrietha]

Yes :(

Regards,

Joseph Harrietha

You received this message because you are subscribed to a topic in the Google Groups "taigaio" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/taigaio/A4R61mhJQPg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to taigaio+u...@googlegroups.com.

To post to this group, send email to tai...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/ac2c715a-eb0c-4351-a11a-2f8cbb36e219%40googlegroups.com.