called controller page of shopping_admin into ecommerce codeigniter application - php

i have created one codeigniter application named as ecommerce. In this application i have created another codeigniter application called as shopping_admin into the application folder of ecommerce. so how can i called controller page of shopping_admin? how to configure shopping_admin?

What do you want?
Why you did not make single application and use the ACL (user Access Control List) between admin and user.
But if you still insist make 2 application on one directory, maybe you can use CURL.
Example here
sory for my bad english

Related

Persistent the authenticate user on main and the subdomains in the Laravel | Session | subdomains

Yes, I know it looks like an old question but still unclear.
I have two different Laravel applications and both have their separate tables. On my local system, I put both of them as subdomain domain(virtual host). Both of them are working fine.
What I want is that whenever a user logged in to either of the subdomains then the user should automatically be authenticated to another subdomain. So I don't need to login into my subdomain separately or again and again.
Some people suggest the following solution.
use the identical setup for app key, session.php, database, and use the database as a driver for the session.
use a third domain as the main domain(or subdomain like auth.example.com) and implement SSO with Laravel.
use passport and create the main domain for the oAuth server to provide tokens.
use Redis or Memcached as a session driver to persistent user authentication.
prefix the table(for second app) with some specific string(i.e app_2) and use single database(i.e database merge)
Real use case:-
One Laravel application handle all banking related feature so the subdomain will be banking.example.com
One Laravel application handle all accounting related feature so the subdomain will be accounting.example.com
I am a little bit confused now. Currently, both application is built using blade template engine for now but in future, the frontend may be in React or Angular. As of now, I can go with the Laravel Blade template engine.
Can someone help me with how can I achieve a single login system and persistent user login and also sync user information across main and subdomains in Laravel fashion?

Protect laravel routes with amember

I am using laravel for my web application. I have integrated amember within my larvel site inside /publi/amember. Now i want to protect my routes using amember. Anyone knows how to do it. I am using L5 Moduler structure for my larvel site.
The best approach is use Am_Lite API to do it.
http://www.amember.com/docs/API/Lite
So you need to include this file
amember/library/Am/Lite.php
within your application (before any output done) and then use the following call to check access:
Am_Lite::getInstance()->checkAccess(Am_Lite::PAID);
In event of user has necessary access then this call do nothing otherwise redirect user to login form.

PHP - One application installation for multiple subdomain

I want to archive this username.mydomain.com for each new user register with application and each user has its own database.
Its actually inventory application developed in codeigniter, so user registration will be only done by admin.
One application installation for all sub domain(usersname) should points to same server directory, later application will select database according to subdomain so how can i archive this.
In order to achieve what you want, is to follow the following steps:
DNS Configuration
Apache Configuration
Testing out your server configuration
Setting up CodeIgniter
Creating controllers & Views
Extending created controllers
All of the steps are nicely detailed in Atchyut Sekhar's article on tutsplus.com # https://code.tutsplus.com/tutorials/basecamp-style-subdomains-with-codeigniter--net-16330
Hope that helps!
Best,
-Rush

Custom Domain mapping in cloud based application

I am creating a cloud based application in laravel/php.
I have a functionality where user can have their website at user.myapp.com and it works (with subdomain and model binding).
I now want to go one step further, and allow users to add their own custom domain names. So their website will be reachable at user-domain.com rather than (or as well as) user.myapp.com.
I want to understand how to do this. I'm using Laravel framework which is based on php and apache.
What kind of server do I need? Can I use shared hosting?
What configs do I need to do in order for this to work?
What DNS record the user must create to put things together?
You can do this with any kind of server. You can make a route that is caught by any domain and in the controller of this route, you can query the database to know what website should be displayed for that domain.
You can get the domain name of the current request using app('request')->root();

How to make web installer for my Laravel application?

I know of #RachidLaasri/LaravelInstaller but it is rather a kind of different thing I want.
I want to do something like, go to a URL like localhost::8000/installer. Then, it will display a page for super admin registration, i.e., email, password, and username. Note: I want to eliminate the ability of making my superadmin app user going to the UsersTableSeeder to configure anything.
Then, when I click on install, it migrate my seeded classes. I currently watched the command line app but still can't really figure out how to go about this.
Any advice / tip will be appreciated.
Laravel Installer
add 2 router in your project.
http :
routes.php
routes2.php
---
view
application/
installation/
in first route you should take db name and more information you need from user. Save db name to .evn file.
After then you might create database using php codes, How to make db Pdo
and run \Artisan::call('migrate') in your Controller.
Rename route to installation-route using php rename method file. And rename route2 to route.
Have you tried this PHP Application Installer
This library can be used for PHP appplication configuration(database, admin credentials etc) using user interface.

Categories