my first (an hopefully not the last) post here :)if i missed out the forum, please feel free to redirect me.
OK, here are few questions:
I need to create a corporate "application" for internal use only (is that OK regarding FuelPHP license)?
that "application" will store (and process) records about build status of our software components (various shared objects,exes,jars,etc.) which are results of regular build procedure (we are using SCons + jenkins for build process). When i think of it, I see a website hosted on some HTTP server (like apache or ngnix), based on PHP and enriched with few web services. build results with history and logs will be displayed, so that developers can analyze build status of their components. so what are your thoughts - is Fuel PHP suited for this or I'm completely missed out the point?
(in general) shall i use REST or SOAP services? most probably, service clients will be python scripts (calling some service methods: when build of components start/finishes)
I'm PHP rookie, and total stranger in web development, but i think that FuelPHP might help me to dive in? Am i right?
3. REST is a 1000 times simpler then SOAP, so don't do SOAP unless you absolutely have to. Fuel comes with a Controller_Rest base controller to quickly create RESTful services. It does both XML and JSON out of the box.
4. To be honest, I don't think Fuel is for the absolute beginner. If you are a developer, and have a sound concept of OO development (C++, Java), then you're used to reading documentation and learn from existing code, and PHP will be yet another language to learn.
If these are your first steps in development land, you might struggle a bit in the beginning, as we don't gear towards the absolute beginner, the documentation doesn't contain any howto's for example. If that is the case, get a good book (PHP 5.3+), keep php.net handy for reference, and try.
If you have questions, you can always ask them here, or pop into our IRC channel #fuelphp on Freenode, there are always people online to help you.
I don't have to use SOAP, so will go with REST. we are currently improving build procedures, so i thought it would be nice to have a fresh language experience (I have almost 10 years c++ experience, so can be considered as an old fart :) )
Donate
