I have a project to implement an offline support /mode for a learning website which is developed by Laravel. Using a PWA package(ladumor/laravel-pwa) for Laravel, the website is already converted into a PWA as offline access is supported by PWA. Here, the question is if it's a good practice to proceed with Laravel PWA and add more features/courses with resource files for offline mode via the service worker. Or the offline implementation should be done with a frontend framework like Vue JS?
Thank you so much for the answer in advance.
Related
I need to install chatbot with my custom laravel site.
Please let me know the suggestion for this integration.
I have tired this integration format Link but it's able to integrate properly.
Thanks
So, I am going to create an ionic 3 project that use my existing laravel backend. My laravel project is on heroku (for now) and it is already setup with laravel passport and API based in mind, since I already created frontend for laravel with SPA vuejs and already configured cors too.
So I supposed it shouldn't be any problem from my backend to communicated with client side. But I am not very experienced with ionic 3, and the problem is I can't find any one talking straight forward about how to implement basic authentication with laravel passport to ionic 3 and also the basic http request like post, get, delete, and put/patch.
Most of the tutorials are about working with firebase, and me myself is not very familiar with firebase and not willing to invest time to those since all my backend needs are already satisfied with laravel. I also found 1 or 2 site talking about laravel and ionic but i think it is from very different version of ionic since the file structure and the way he working is very different from what I've known (beside those article already 1-2 years old now)
So maybe anyone that have a tutorial about all this thing can share it to me?
I need some suggestion and possibilities...
I have a product whose back-end is on Laravel 5.0 and front-end is built on Angular 2
Due to some SEO issues I am rewriting the front-end in Laravel.
Here I wanted to know that if I am creating new Laravel front-end app THEN how could I communicate/use/request my pre-built back-end APIs without using cURL for best I/O response time.
Our company is about to start a real estate project and have decided to go with the laravel 5.3 framework. The first phase is to write the apis and then these apis will be consumed by the mobile team and the frontend team to build the official mobile app and the web portal respectively.
Now I am confused whether to use laravel's built-in Resource controllers (as instructed in this tutorial http://www.programmableweb.com/news/how-to-build-restful-apis-using-php-and-laravel/how-to/2014/08/13) or use the Dingo Api framework.
Could you please help me which one should I go for and why as per the requirements i mentioned above?
Thanks in advance
Since, Laravel 5.3 comes with Passport (for api authentication), I would suggest you to use Resource controller, which is very simple and easy to work with, and also it create a meaningful end points
Route::resource('post','PostController');
GET /post/{post}
POST /post
EDIT /post/{post}/edit
DELETE /post/{post}
I've used the Codeigniter RESTful framework to make an API for my mobile apps. I would really like to host it on Google's App Engine but there really aren't any tutorials showing how to do this.
Could anybody help in this regard with helping me to get onto app engine?
You can use CodeIgniter modified to run on Google's App Engine (PHP) https://github.com/edwardmp/CodeIgniter-AppEngine
And also follow Tutorial http://blog.programming4design.com/codeigniter-on-google-appengine-for-php/