Guys I have build a website and testing it on localhost using LAMP on ubuntu. Now i want to publish this website on my local network. how do I do it.? Please help. Thanks.
Install a webserver somewhere on your local network (this could be the one you have been using for testing if you don't want to have separate development and live environments … although that usually isn't a good idea).
Publish the site to that webserver (in the same way you are doing for your development server).
Give out the URL to the site
Related
I have my own project hosted on the github. I am using Xampp server on my local machine with necessary database and tables regarding my project.
How can I connect or replica my localhost to GitHub?
This is pretty unclear, but if I understand this correctly, you wish to use github as an hosting service. Short answer is that you can't.
If you want to publish your project, you'll need a server and a domain name.
If your project is a static website, then you can use github pages to host it.
I am in process of making first Drupal 7 website and for that searching for the web hosting. And I found that, several hosting says 1-click Drupal installation. But as I was searching the net for standard practice of site development, many sources explains Develop the site on local environment and then transfer to the web server (which includes, transfer of database, and whole drupal with modules) which is quite convincing that you develop locally and transfer to web so it start working there as it was working on locally.
On the other hand, what is the use of 1 click drupal installation on web server, I believe it will install the fresh core drupal, so from again initially I have to start developing, installing each module so, starting from square 1.
So, which is the BEST practice for making web site live, shall i develop locally first or develop directly on web server?
Simultaneously, what is the best practice about maintaining site, I read that, there should be One live site where visitor will come, Second Test site which is similar to live, One local site, So what is the standard practice for this, and how to maintain?
Very thanks in advance.
In my previous answer in point 2 i outline 4 servers: DEV, STAGE, QA and PROD. this is usually the process on kind of "biggish" company where lots of people might be working in infrastructure, development and qa department. This said, if you are not working in a complex environment, you might just have 2 drupal installations, one for testing , on DEV (e.g dev.mysite.com) and one live (eg.mysite.com). The different url can be arranged from you cpanel or personal panel in case of a shared server.
They might run on the same server, however the dev site is the one you will be working on while creating the site, then you will clone the dev and make it live once the site is ready.
You will keep the dev site as a space to test new features, fix bugs, test updates of module or core files. Once these new features are implemented, or bug fixed, you will replicate the same steps on the live site.
GIT is a version control system: it allow you to keep track of the code you are working on, you might want to create 2 branches: DEV and MASTER.
You will be working on DEV to create the site or update files or fix bugs, and you will merge to LIVE and pull on the live server the code once it's stable. I hope this clarify a bit.
1) one click installation process are usually offered on shared servers, they then might have lower performance and memory limit that your local lamp set up. It is the good to check what is the version of PHP and MySQL that runs on the server, as well as max upload file limit or connection time. I prefer start working locally and then publish on my server, BUT if you install on your server first you will have a good idea of how drupal will perform in the real world, then you can always clone the site and db on your local, and also you will avoid the ugly surprise of trying to move your site from local to your server and find out bugs or migration issues.
2) in enterprise dev environment you might have 3/4 steps, DEV ("wild west") STAGE (release candidate) QA (quality assurance server) PROD (live site). You usually sync (eg with GIT) your local to DEV or STAGE , than you push to QA, then if it's all good to PROD
wondering if you can help me with the following.
I have a new server in my office, with Windows Server 2008 R2, i have 2 developers working here now, i have just installed WAMP on the server and running, i would like that each of the devs to have their own instance in the wamp, i mean if within www i have N quantity of Projects.
Programmer A gets access to some projects only, also the Databases.
At this point i know how to setup the wamp to be accessed in the LAN using Vhosts, but i have no clue how to setup specific privileges.
Could not find anything on the web on that issue.
Can I suggest another method.
As WAMPServer is intended as a developers tool anyway, you install WAMPServer on each developers PC. You make sure the config on all PC's is the same as the Server version.
For an existing project i.e maintenance/upgrade you give them the source and a database backup. They develop this locally and when its ready you take the source and a database backup to your WAMPServer on the Server.
For a new project, they develop it locally and then when its ready you move the project to the Server.
This would be much simpler and would leave the Server version for UAT or LIVE, whatever you are using it for.
Of course there are better solutions involving source management etc, but as a fairly simple and low maintenance solution, this would work.
I am currently setting up a development machine at my company and I would like to be able to set up a few local sites on this one machine for testing. In order to do so, I am running the following software:
ColdFusion Server 10 (Developer's Edition)
IIS
Everything is installed and I am able to run the default site (from localhost) but I can't figure out, nor can I find how I can set up other sites on this system. I have the files for each site on the local machine. Ideally, I would like to be able to call up each site using a subdomain, such as (http://site1.domain.com, http://site2.domain.com, http://site3.domain.com) where each one points to a separate file base on the local machine.
Can anyone point me in the right direction?
Create the sites in IIS for each site, pointing to its respective web root. Then run the web server configuration tool to hook up the connectors for the sites.
You can find that under {ColdFusion root}/cfusion/runtime/bin/wsconfig.exe (on windows - not sure of the file extension on non-windows machines)
From there you can run the connector for each individual site or you can set it to run the connector for every site.
what configurations can make differ between a local host server like phpMyadmin and a web hosting server
is it possible or convenient if a laptop [instead a desktop computer] is converted into a serverHost
is there a php script provided for an automatic backup or sync of files
in a web-based application, which is better? running the codes first in the localhost or directly upload the codes in the webhost ??
waaa .. .i need some response to this
Default configurations on localhost servers are almost the same as the configurations hosting-companies offer.
Ofcourse!
Just google, back-up is always possible.. hosting-companies gives 90% of the time a tool in the controlpanel to backup your website.
Always test on localhost then apply on the webserver and watch the results.