Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You could have a separate application folder for the admin and front-end:</p> <ul> <li>application <ul> <li>classes <ul> <li>controller</li> <li>model</li> </ul></li> <li>views </li> </ul></li> <li>admin_application <ul> <li>classes <ul> <li>controller</li> <li>model </li> </ul></li> <li>views</li> </ul></li> </ul> <p>This approach would allow you to customise each bootstrap environment individually, and separates the various files nicely. However, due to this separation you will need to structure shared code as modules, to allow the functionality to be shared across the two apps. You could just duplicate the code of course, but that would wrong now, wouldn't it! ;)</p> <p>Another approach would be to have admin subfolders within each folder of a single application:</p> <ul> <li>application <ul> <li>classes <ul> <li>controller <ul> <li>admin</li> </ul></li> <li>model <ul> <li>admin</li> </ul></li> </ul></li> <li>views <ul> <li>admin</li> </ul></li> </ul></li> </ul> <p>This approach leaves files a little more intermixed, and might make things harder to maintain (depending on your perspective), but it's certainly easier to implement. One advantage of this approach is that you can create a /public_html/admin folder and protect it using .htaccess (you'll need to add a copy of the normal index.php file too). Then whenever any <a href="http://yourdomain.com/admin" rel="nofollow noreferrer">http://yourdomain.com/admin</a> requests are made, the .htaccess file will kick-in and protect your admin application at the webserver level. Plus, the request will automatically route to the /admin subfolders within the various folders, so you've also got less work to do when it comes to routing.</p> <p>Both situations would use Kohana's (awesome) routing mechanisms to handle which requests went where, and each is as secure as the other from an application access point of view. I've assumed you're using KO3 by the way...</p> <p><strong>EDIT</strong><br> Actually, you are able to .htaccess protect the admin app if you use the first method too. You'd just need to adapt the /admin/index.php file to point to the admin app.</p>
    singulars
    1. This table or related slice is empty.
    1. POkohana project structure
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMathew
    1. USMathew
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POkohana project structure
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for your clear answer MatW. I will check out the second approach. Approach 1 looks great, but I'm not too sure how modules work at this moment. Thanks a ton!
      singulars
      1. PO
      1. USberto77
    2. COHi MatW, I decided to stop being a wimp and try out the first folder structure. I have everything set up. But now, do I create a separate bootstrap.php file in 'admin_application'? and how can I tell my application to use this bootstrap when it goes to http://mydomain.com/admin or http://admin.mydomain.com? Thanks a lot
      singulars
      1. PO
      1. USberto77
    3. COok, I think I will make two 'index.php' files. 1.site.php and 2.admin.php...put both of those in document root. also create another bootstrap.php file and place in 'admin_application'. then use .htaccess to route to the correct application (admin_application or application)...not sure, but I'll try. Help appreciated.
      singulars
      1. PO
      1. USberto77
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload