I have developed a Laravel application that is currently being used by my clients. I am in the midst of developing a simple WordPress website to advertise my services and basically showcase what I do.
I'm unsure on what the best way is to link the two.
My domain is www.themacrocoach.co.uk
I'm thinking the best way to do this would be if the client logs in from: www.themacrocoach.co.uk/login
Which then automatically redirects to:
www.themacrocoach.co.uk/dashboard
Upon logging out, the user is redirected back the WordPress website:
www.themacrocoach.co.uk
The dilemma I have is how to set all this up? Currently my server only has the Laravel application residing on it.
Do I keep everything on one server or split them across two?
Related
I have a SAAS in production and I want to give the customer the option of having a custom domain.
The application is in PHP without any javascript framework.
I would like to know the best ways to set up so that it is practical in terms of scale and implementation.
The operation should be as follows:
MAIN APPLICATION
myapp.com/company/product/clothes
The client will be able to navigate through the page through his domain as well, but everything being consumed from the main application without code duplication.
Customer domain example
companyapp.com/product/clothes
I currently use a shared hosting that contains WHM/CPANEL.
I manage a website. Let's name it Website A. Website A is written in PHP, procedural-style, with a few different and out-dated frameworks in it. No surprise, it is a mess to maintain and to upgrade. I want to create Website B with a clean framework (Symfony2) and using OOP. Slowly I will refactor Website A into Website B. Any new features will also be done in Website B.
The catch? I want content from Website A to appear in the layout of Website B. I can't simply include the files of Website A in Website B as the configuration of it messes with the framework of Website B. What's the best way to achieve it? Using an iframe? Using Curl? Or using another method?
When I tried using AJAX, the integration went smoothly. Since they're on the same domain the cookies are shared, so even if the user logs in on Website B, Website A is aware of it. It was, however, slow to output and I had problems with the responsive design (even though I know responsive iframe can be done).
When using Curl, it was much faster to output and no responsive problems. However, since it's PHP that connects to Website A, I need to find a way to pass the authentication from one Website to another.
Both methods need some work in order to function properly. I lean toward the curl method, but is there a "best practice" in my case?
Both websites has personalized content, it's not simply a firewall-type authentification.
I'm not sure whether you're authentication involves personalised content, which would be harder, or just firewalled content. This would make a difference. The best approach I've seen to this problem was to use nginx as a reverse proxy.
I am still new to magento. I have successfully installed magento ce on my local wamp server. I choose magento because I heard that it has multi site feature. My client have three separate website that are running on three domain name(www.sample1.com, www.sample2.com, www.sample3.com). I am planning to control them on one admin.
I would like to know how can I manage to create multi site on my local and how can I upload it on live server.
Also, can someone explain to me in simple the architecture of multi site of magento. If I'm not mistaken, I understood it this way.
admin -> my backend maybe running soon www.sample1.com that handles all my website.
website -> This is where I will give separate domain. for example website one is running on www.sample1.com. website two is running on www.sample2.com. and finally website three is running on www.sample3.com
store -> I don't have clear understanding of it.
store view -> this is the presentation layer. the most fron-end of the website where products, themes are displayed.
This is kind of stupid but i'm still new to magento.
Thanks!
I have a wordpress site, foo.com. For various reasons, mainly caching, I need to move the wp-admin area to a subdomain admin.foo.com which is hosted on a separate server.
What's the best way to approach this, would a straight .htaccess rewirte work? I've seen that you can set WP_ADMIN_URL in wp-config.php but how do you separate the site in such a way that the amin sits on a different server than the rest of the site.
You can make use of two different installation of wordpress but the database will be same. One for staging and another for live
There isn't a way to separate the frontend and admin area of a Wordpress site onto two different servers. Wordpress is a web application. You get the whole thing as a package.
If you've seen something like this before, the site owner is doing one of two things:
They are running Wordpress on the admin site only, then using a plugin or some other technique to generate static HTML snapshots of the pages that form the public website.
They are using a staging site plus live site type architecture. Many of the new WP-specific hosting services include a staging site and a simple synchronization option.
I have developed a website application that includes a custom built CMS and PayPal payments etc...
My client already has hosting for his main website via the developer of that site.
I wish to host the new application under a subdomain such as:
application.website.com
I have reservations about storing my complete source code on the other web designers server.
Is there a way that the code can remain on my server but with the required subdomain or somehow password protect the folder?
Thanks for the help.
You might be able to store your source code on your server and use the PHP include function to get the pages on your client's website to use the code on your server. I've not tried this so it may not be possible for PHP to communicate between two servers like this, but give it a go and see what happens.