What do you mean by authentication - the ability for Web users to create usernames/passwords etc? Bootstrap is a front-end frame work ( in browser Gui) you'll need a back end such as wordpress, etc
Bootstrap is the presentation portion of a website, a CSS framework that works with JQuery to make HTML look pretty on a page.
For authentication you need logic written in code using a language like PHP and some way of storing your users information such as MySQL.
Therefore you need to learn how to program and how to style with Bootstrap to create an application that presents Bootstrap pages and does things like authentication.
It's best to use a PHP Framework once you learn these things. I suggest Laravel - but before learning Laravel you must understand Object Oriented Programming principles.
laravel is nice but it's a fucking pain to set up before you get a feel for it. Lots of dependencies and using composer/homestead isn't always so easy.
The hardest part is setting up the environment. I spent the better part of a day getting it to load correctly the first time.
I don't care what anyone says, it's finicky and I'm not a moron.
Once you get it down it's really nice, you just need to stick it out.
If you are making run of the mill sites stick with a common CMS, i.e. Wordpress.
If you need to go completely custom and build something unique I would use laravel.
laravel is nice but it's a fucking pain to set up before you get a feel for it. Lots of dependencies and using composer/homestead isn't always so easy.
The hardest part is setting up the environment. I spent the better part of a day getting it to load correctly the first time.
I don't care what anyone says, it's finicky and I'm not a moron.
Once you get it down it's really nice, you just need to stick it out.
As with anything, there is a learning curve.
Laravel is no more difficult than any other Framework. Frameworks use lots of dependencies.
The thing that sets Laravel apart from many other frameworks is it's extensive scaffolding capabilities, like in my example above to scaffold basic auth into an application.
However you do need a fair amount of knowledge to develop your app. I guess as a minimum you would need to know.
PHP
MySQL
Laravel
Git
Then for deployment you'd need to understand how to set up a web server and possibly a mail server. While it's possible to deploy a Laravel App to shared hosting I wouldn't recommend it. You need a custom Document Root for starters and then you really want to be able to lock down the server for the best security.
laravel is nice but it's a fucking pain to set up before you get a feel for it. Lots of dependencies and using composer/homestead isn't always so easy.
The hardest part is setting up the environment. I spent the better part of a day getting it to load correctly the first time.
I don't care what anyone says, it's finicky and I'm not a moron.
Once you get it down it's really nice, you just need to stick it out.
If you are making run of the mill sites stick with a common CMS, i.e. Wordpress.
If you need to go completely custom and build something unique I would use laravel.
thanks.
i custom code everything from scratch., very rarely i use wp.
but if it needs to put some time in it., then i am good with old fashioned php coding.
thanks.
i custom code everything from scratch., very rarely i use wp.
but if it needs to put some time in it., then i am good with old fashioned php coding.
Don't take 'old fashioned PHP' to Laravel - you need to use modern coding standards and OOP to get the most from it.
Laravel is great but you'll find there's a fair bit of new stuff to learn, like Blade (templating language) and Eloquent ORM (a simplified ActiveRecord implementation).
Once you learn Laravel you'll be able to do more things in less time than you have ever done with PHP.
thanks.
i custom code everything from scratch., very rarely i use wp.
but if it needs to put some time in it., then i am good with old fashioned php coding.
Over the last 10 years I went from procedural to OOP to CodeIgniter to Laravel and now I am back to building my own custom OOP apps. As nice as Laravel sounds it is much quicker and easier to just pull in a few packages from packagist using composer and go from there rather than fuck with Laravel. This hipster movement bullshit towards that framework confuses me, they all love making more work for themselves. Stick to what you are doing.
Over the last 10 years I went from procedural to OOP to CodeIgniter to Laravel and now I am back to building my own custom OOP apps. As nice as Laravel sounds it is much quicker and easier to just pull in a few packages from packagist using composer and go from there rather than fuck with Laravel. This hipster movement bullshit towards that framework confuses me, they all love making more work for themselves. Stick to what you are doing.
i tried codeigniter once and it was Pain in the Ass, last time i checked codeigniter stopped updating.
i tried codeigniter once and it was Pain in the Ass, last time i checked codeigniter stopped updating.
i still do procedural., and its fun.
It was purchased by a university in British Columbia I believe who update it all the time. The next version is being completely redone to use more modern techniques.
I liked CodeIgniter because I could upload it and you're done with the setup. Extremely easy to use and when quick to get the job done. It may not be the "proper" way to do things in this skewed 2016 programmer mindset but when time is money in business then your boss or client loves seeing quick progress.
Comment