I have the following problem: If I have one website and the server drops, I can configure an backup website? Example: www.exemplesite.com goes offline because of techinical issues, so www.exemplesite2.com goes online, so my users don't have to wait until the first site goes online?
I want something like If> the site 1 goes down Then> the site 2 goes online until site 1 is down When the site 1 comes back to work, I put site 2 down again If I'm not being clear, I'm sorry, my english is very poor
Buy another domain and put the exact same code in ? and then make it private and if it goes down you can unprivate it ?
Related
I'm currently trying to upload a html+css page to my hosting service (1&1 internet).
Unfortunately, I have very little experience in that; and would like to ask this question:
How is it possible to update the existing homepage on a site that already has been uploaded to the web?
I'm using WebspaceExplorer. Now, when I enter it, (Hosting section) there are a lot of folders and files with a few options like download, delete and so on.
I can't seem to find out how to make the program understand which one should be the homepage. This is because I see that the page I uploaded is online and accessible, but is not the first page the user sees! How can I change it?
It may be confusing because of the poor description so here is the url of both:
velten-berlin.org (current Homepage)
velten-berlin.org/Upload (desired homepage)
I am hoping somebody can help me because I am on the verge of frustration tears.
The company I work for has a site hosted on godaddy and has to remain up until I complete the rebuild on hostgator, using the Wordpress theme, Grand Restaurant http://themes.themegoods2.com/?theme=GrandRestaurant
To get around the domain name issue since I cannot change nameservers yet, I had to use the Google Chrome plugin, Virtual Hosts, which has me input the IP and domain, to force access to the site.
Everything was working fine until I needed to use the "content builder." If you look at the Grand Restaurant theme, you can click on Menu. I need to use the "Menu Grid" option in the content builder but it does not work. Whenever I try to add the menu grid, it appears that it is trying to load (showing the gif loading image) yet in never actually loads. I have spent several days and hours going back and forth with host gator and the theme developer.
The theme developer says that the content builder does not work because:
"The WordPress URL and Site URL are set to the domain name. When you are logged in, you are being redirected to the IP, so the browser sees 2 different sites and some functionality ex. AJAX call doesn't allow you to get data from different URLs.
Your WordPress URL and Site URL settings are different from your actual site. You have to change your Domain Name URL and Site URL settings to the IP number."
I did what he said earlier today and it completely broke the site. Spent nearly 2 hours with host gator's tech support to get it back up. All tech support will tell me in regards to the content builder not working is that I need to change the AJAX file to allow the site URL and wordpress URL to be different. I have no idea how to do that!
Any wisdom you all could provide would be greatly appreciated. I have 1700 bakery items that I need upload by the end of July and I do not know what I am going to do if I cannot get the content builder working.
In order for this to work properly you should be using a method of back up and restore. By migrating from one hosting provider to another you could simply deploy the new Wordpress on host gator as a new site and import the Wordpress backup to the host gator with the many different plugins available through Wordpress. The way your trying to complete this is impossible and usually will only work with images and back ups being managed on virtual machines, and VPS. It won't hurt anything on the original up and running site. You mentioned that host gator was able to get the site back up? You shouldn't have to rebuild this if you use a back up and restore method. Everything should fall right into place, you can also test these methods through virtual box, and VMware virtualization products which offer trial versions. Try using a migration method and see if the conflicts still persist with the content builder.
Heres is what I would do if you cannot change the domain over but still use the domain for the dev environment.
Modify your hosts file and use hostgators IP and the company domain as the entry.
Install wordpress to the current company domain by simply entering the domain (Should go to hostgators server since you've added that entry in your hosts file)
With the hosts file modification, you should be able to view the wordpress site thats hosted with hostgator using the live domain name.
This way, when you're launching, theres no need to do any modification on wordpress. Simply change the DNS over, revert your hosts file and the site will swap over seamlessly.
I have this issue where I cant decide what's for what and what is the best. Hope someone could provide me with some explanations to clear up my confusion.
So here it is, I have a site which is quite large. Currently running on Yii Framework which I am in the process of migrating it to L5 Framework. This website has several sub sites structure like below example:
1) www.example.com
2) www.example.com/{username}
3) explore.example.com
4) explore.example.com/{organization}
5) connect.example.com
6) coin.example.com
7) m.example.com
8) e3.example.com
So the current hosting method is using 1 project to host everything. Here comes the problem, should one of the sub sites were to be disabled for whatever reason, the whole website would need to be put to a stop, code to disable the site and the deploy the entire site again.
Back to L5 Framework, I noticed that I can do the same in laravel aslo to host everything in one project using the following routing methods in routes.php:
Route::group(['domain' => '{account}.myapp.com'], function()
{
Route::get('user/{id}', function($account, $id)
{
//
});
});
Again the same question rises, if there is a sub site to be disabled, I would need to code the disable site and redeploy the whole site again. So I was thinking if it is practical to host each sub sites in a new project as a module such that if any changes to that sub site, it will only affect that particular module while the others maintain running.
Additionally I would also like to ask, if I host it as a separate project, my website requires the user to login before they can navigate to any of the pages or application. So how do I tell the other modules where the user has been logged in and everything can be proceed as usual?
Finally of course if anyone have any other suggestions or approaches feel free to enlighten me too. My main motives are to achieve:
1) Maximum development flexibility
2) Fail tolerance
3) Sub sites can share the same login with the main website
(You are only require to login at the main page and you will be authorized
to use the rest of the web application)
Thank you.
I guess, the answer will be too late. Nevertheless, it might help someone else.
Today I faced a similar dilemma myself - should I use subsites or separate applications for public site and admin site of my application.
At first it seemed that I should have separate apps to avoid bringing down bith sites if I wish to upgrade just one of them. But I did not want to duplicate all the Laravel boilerplate code all over again in my repository.
Then it came to me that actually I can implement everything as subsites, but I can deploy the Laravel app to multiple subdomains. Thus there will be single app in the repository, but I'll have a different copy for each subdomain.
Drawback - the code of controllers, views (and some site specific models) will be duplicated for each deployed site. That's not an issue for a small site - just a bunch of unused files. But if I wanted a clean solution, I could implement some modular structure and bring in site-specific MVC stuff during deployment. That's another topic, I guess. There are some 3rd party solutions for modular Laravel apps. Of course, modular solution adds to the complexity and maintenance, therefore I have nothing against file duplication on server, if that's not an issue for you.
Regarding authentication - I haven't tried it with Laravel, but I have experience with implementing cookies for top level domain in pure PHP application. Essentially, you can configure your session cookie to be effective for all subdomains, and then users will have to log-in just once in any of your sites. Here seems to be a working solution for Laravel:
Persisting sessions across subdomains in Laravel 5
Just set the top level domain to .example.com and theoretically you should be good to go. For development purposes, I'd store this value in .env, though.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I hope someone here can help. I’ve spent days looking through forums and google results to no avail :(
Basically I have a friend that was having a magento site developed for them, but the company doing the developing have been giving them the run around for over a year. Because of this, my friend has asked if I could move this onto my shared host to continue developing, and then once complete, to move onto their own VPS.
Below is a list of things I have done:
Moved all files to shared host
imported .sql file into a new database
altered .xml to new database name and password etc
altered the database to point to the relevent IP address for
developing instead of the previous development url (friend doesn’t
own the url previously used)
deleted all cache and other temp
files as per online instructions to moving magento.
reindexed cache and index management.
After doing this, the site loads fine, until I want to navigate into a category or product page etc, then I get a full screen 404, not magento’s 404.
If I manually add index.php into the middle of the url, the page will load. If I disable the SEO rewrite then obviously everything works fine (other than any links that have been manually created into images etc of course). This lead me to believe it was a problem with rewrites, so I altered the rewrite url in .htaccess to point to google, and when I click on a category etc, that then indeed directs me to google. So I know the problem isn’t rewrites not working.
I then found a site suggesting it could be a problem importing the database that replaced 0’s with 1’s in certain database locations, however I checked this and all is just as it should be.
I know everything was working fine before the move, as I was developing the site for my friend whilst it was on the original server (long story, people who were being payed to do things weren’t, so I was doing it, however they refused to give ftp access to be able to change faults in the skin)
Version of the magento concerned is 1.501
Also, I already have one magento install working successfully on my shared host, so I know the host is compatible with magento.
One further thing that I believe proves apache rewrites are working (I've been told a lot that they can't be!, I've even checked with the hosting company just to make ultra sure):
If I amend the .htaccess from index.php to http://ip.ip.ip.ip/~example/index.php then the categories start to work!!
However this isn’t a fix, because no matter what I cannot get other links to work, e.g: On a few pages I redirected the category to land at a “landing page” then there was a description and an image to then click to take you to the product page. These links now do NOT work!!!
If anyone can give me any ideas where I need to be looking I would greatly appreciate it.
Many thanks for reading.
Oh, and nothing comes up in the error log either.
Thanks for the suggestion, however I've found the solution.
Magento obviously didn't like being run from the ip address followed by a folder.
I've since assigned it a temporary domain name and everything is working 100%
I've a magento installation with 3 websites whit 3 storeview each. Everything works fine a part google analitycs. I want to have a different account associated to each website to have separate statistics. The main site works perfectly but the other 2 no. I don't see any traffics, visit piratically nothing.
Thanks for your support,
bye
Enrico
Goto Admin -> Config -> Google Api
Then change the "Current Configuration Scope" for the other 2 websites and enter each GA Account Number.
View source on each domain to check if the GA Code is there and correct.
You may also want to take a look #
GA Tracking Multiple Domains