|
C
|
Chris Whitehead 4/1/2025 |
|
I've used that method previously in 10.91, then I had a play about with the JWT keys which works well. I actually like this better as it makes the dev a bit faster. I wanted to break a large project down for speed and make it easier to develop rather than build a larger project each time. I found that using the shared JWT in security -> session control The linking to the other application pages in each of the menus, the users can swap between the apps/sections without knowing they actually are. I understand this makes it a little harder sometimes as you're dealing with 2 codebases rather than one, like adding a field into the shared table, you have to update both, you'd still have to update both even if it was one application |
|
|
C
|
Chris Whitehead 4/1/2025 |
|
I must add, If I can see any issues, this would be with dynamic permissions so that might be worth keeping an eye out for names which are the same and updating groups, I've not got that far yet. |
|
|
Sergey Kornilov admin 4/1/2025 |
|
Saving a project as a template and adding it to another project is a viable option. And yes, it probably makes sense to turn off the security in the second project before saving it as a template. |
|
|
francesco author 4/3/2025 |
|
Thank you very much for your helpful answers! |
|