These are chat archives for COCOPi/cockpit

29th
Jan 2015
Adam Paterson
@adam-paterson
Jan 29 2015 12:57
Love the look of this, playing around with it this morning and I’m impressed
Artur
@aheinze
Jan 29 2015 12:58
@adam-paterson thanks! :-)
Adam Paterson
@adam-paterson
Jan 29 2015 12:58
I’ll be issueing a couple of PR this weekend, just some code smell things
Artur
@aheinze
Jan 29 2015 12:59
sure, any contribution is welcome
Adam Paterson
@adam-paterson
Jan 29 2015 13:02
Thought about spliting the project dependancies out? Making Lime it’s own depends for example?
Artur
@aheinze
Jan 29 2015 13:06
Lime and all vendor libs are already independent projects … or do you mean managing the vendor files via composer?
Adam Paterson
@adam-paterson
Jan 29 2015 13:09
Yeah
Artur
@aheinze
Jan 29 2015 13:24
I know this question would come up some day…I have a personal opinion about that for cockpit. I want to keep the repo small and simple + a „clean“ vendor folder without docs/tests etc. I understand that for large projects, composer is a must, but Cockpit has very few dependencies which are easy to update before a release. You should be able to download cockpit from github and start right away without any further step. so for now composer integration is not planned.
Julien Tant
@JulienTant
Jan 29 2015 13:28
index.php is the entry point of all routes ?
i'm thinking about, how to use this inside of a framework
i guess i need to expose the index.php file, and update some path in this file
Artur
@aheinze
Jan 29 2015 13:33
you have a „custom“ folder in within cockpit just add a config.php and bootstrap.php to adjust paths or integrate custom code…please have a closer look at bootstrap.php
index.php is also only for for the backend