jamesmp Posted July 9, 2014 Share Posted July 9, 2014 (edited) Hi guys Been a while since I've been on here, completely lost my login details for my old account which is a shame because it was a well established one but hey ho that's life. Anyhow, I've starting a project as of tomorrow and I was wondering if I could get some advice on the best methods/routes to take. The Brief + 3 full websites + no single admin + one main admin The Plan Once all 3 websites are complete none of them will have the standard admin panel that the average website has. All 3 websites (this number is going to grow in time too) will have one central admin held of a separate and isolated server which in essence will *remotely* administrate the websites I connect to it. The Question I have never done a project with multiple websites that run from a central admin. My questions are if anyone could shine some light.... Should I make the admin panel audit the website selected by sending commands through api, crud, rest or simply by direct db access? What is the most secure way of doing this central admin (bare in mind the admin panel will have a minimum of 10 different admin levels/permission sets)? How should I have the database layout/hierarchy for this (3 completely separate site - again this will grow + a central admin site)? Last question (that I can think of) - how much of a mammoth task really is this? Any help would be greatly appreciated! Thanks guys James Edited July 9, 2014 by jamesmp Quote Link to comment https://forums.phpfreaks.com/topic/289643-some-advice-for-a-large-project/ Share on other sites More sharing options...
trq Posted July 9, 2014 Share Posted July 9, 2014 The first question I have is, these "websites", are they all going to be hosted on a single machine? If so, why is the admin panel going to be hosted separately? I would be possible to create a CMS that could handle multiple websites which is essentially what you're asking. Not a simple task, but its very doable given the right timeframe and resources. Should I make the admin panel audit the website selected by sending commands through api, crud, rest or simply by direct db access? Rest is a "type" of api, while crud is basically an interface to the database. I would be tempted to go down the api route but it would be a lot more work than creating a cms allowing crud. What is the most secure way of doing this central admin (bare in mind the admin panel will have a minimum of 10 different admin levels/permission sets)? Really? I'm not sure that is a question that can be answered in a simple post. How should I have the database layout/hierarchy for this (3 completely separate site - again this will grow + a central admin site)? A single database will suffice. Last question (that I can think of) - how much of a mammoth task really is this? Completely depends on your skillset and the tools that you are comfortable using. I just finished a project where I created a completely custom, fairly feature rich CMS for a client in around 5 weeks from scratch. With the right tools, anything is possible. Quote Link to comment https://forums.phpfreaks.com/topic/289643-some-advice-for-a-large-project/#findComment-1484452 Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.