08-25-2016, 04:10 PM
Hi,
I'm wondering, what is the best/recommended structure or design for a project based on/including UserSpice. Our project will offer several web services. So, starting at the root folder I have e.g. a folder for service1, another for service2 etc. Now, I like the idea to have one UserSpice system, i.e. the users and usersc folders, e.g. located in the root folder. I'm not sure, but I think that in this case I would need a lot of additional files, e.g. an extra header.php for each service, an extra navigation.php for each service, extra custom_login_script.php. Additionally I think I would need a lot of additional logic to check where I am and then which files to choose etc. Hopefully, I'm wrong and there is a much better solution/way.
Another possibility, which came to my mind is to have an UserSpice system (the folders users and usersc) in each of the service subfolders. In this case I could clearly separate all stuff and I could have different header.php, navigation.php and all the custum stuff in the separate usersc folders. All UserSpice systems could of course access the same data base, so, for the user it looks like one system. But I'm scared about maintaining all UserSpice systems regarding patches or other changes or changes by myself.
So, would be happy to hear some good advice.
Thanks,
Sebastian
I'm wondering, what is the best/recommended structure or design for a project based on/including UserSpice. Our project will offer several web services. So, starting at the root folder I have e.g. a folder for service1, another for service2 etc. Now, I like the idea to have one UserSpice system, i.e. the users and usersc folders, e.g. located in the root folder. I'm not sure, but I think that in this case I would need a lot of additional files, e.g. an extra header.php for each service, an extra navigation.php for each service, extra custom_login_script.php. Additionally I think I would need a lot of additional logic to check where I am and then which files to choose etc. Hopefully, I'm wrong and there is a much better solution/way.
Another possibility, which came to my mind is to have an UserSpice system (the folders users and usersc) in each of the service subfolders. In this case I could clearly separate all stuff and I could have different header.php, navigation.php and all the custum stuff in the separate usersc folders. All UserSpice systems could of course access the same data base, so, for the user it looks like one system. But I'm scared about maintaining all UserSpice systems regarding patches or other changes or changes by myself.
So, would be happy to hear some good advice.
Thanks,
Sebastian