NodeJS is a platform, I can't think of a reason why would you want to minify that code. NodeJS does not have anything to do with front end development. Minifying and concatenating scripts and styles is mainly a process for the front end.
Nothing here yet.
Nothing here yet.
No blogs yet.
NodeJS is a platform, I can't think of a reason why would you want to minify that code. NodeJS does not have anything to do with front end development. Minifying and concatenating scripts and styles is mainly a process for the front end.
That's great that you can go to a cloud service and set up a project quickly but some companies use their own custom production server(s). Docker is good for these situations, where you set your server manually and don't need to pay for services that give you servers to use (DigitalOcean / AWS etc). The power of Docker is that the exact same environment can be used for local development, staging and production.
It really depends on the project and the architecture of the project you are working on. Some projects are bigger and a simple CRUD generator would probably be useless when you have millions of classes handling every single thing in the application. Generators are useful for small to medium projects, where you can quickly prototype a web application. I personally don't use them at all.
Think of an idea for a web application or choose one from Upwork. Start building it and as you build it and get stuck, ask questions, look for answers, learn the skill of figuring stuff out, you'll need it in this profession. Watch tutorials, although they cover the basics most of the time, but you can even watch people code live on Livecoding.tv Deploy your project and celebrate!
Query scopes are usually defined in the model classes so you can use them anywhere when using the model as a dependency or the facade. The AuthController is not special, it's just like any other controller but the problem you might have is with the call of the scope itself. Post some code here so we can see what do you work with and what might be wrong.
I build them in parallel, feature by feature. Sometimes I might spend a little bit more time on the front end but since I am not really a designer, I just set up the template for a start and build a prototype application. Later on, I just change stuff and refactor code if needed. I do this because I know that things will change and better ideas will come up later on. You can't possibly know what's coming up next, or how it will look based on the first ideas and the initial spec. Sometimes I just add features to a list by myself just to improve the User Experience and talk about the ideas with the client if they will be implemented or not.
Laracasts should be your best friend. This is one of the websites that changed my way of thinking and the way of programming. I believe that this is the best website for PHP and Laravel (if you plan on using it after you are done with plain PHP, few projects) The PHP For Beginners series is still in progress but it gets updated every week. There's a lot of modern PHP development on this website, including some JavaScript too! The Laracasts Forum should be your home for all PHP questions while learning. There are a few other websites that teach PHP and/or other PHP frameworks (save them for later, don't start with a framework!!!!) The ones I checked out were: Code Course KNP University Pluralsight - Has a few courses on PHP but it has a lot of valuable content for JavaScript, HTML and CSS and other stuff. Whatever you choose, make sure to spend a few good months or a year with PHP and Object Oriented Programming PHP only without using any framework to understand the language and what's happening. Make sure to ask questions, people will help you. Oh, and most importantly, think of a few cool projects that might be useful to you, just so you have something to build and practice your newly learned skills. Remember to revisit things that you already know so you can understand things better every time you learn the same thing. You will find out why it is used and how it is used in real life. That's how I learned Object Oriented Programming.