I'm a noob to the VPS game. How do you do your website development with a VPS. Do you develop the website on your local PC then FTP the files to the VPS, or do you install the user GUI on the VPS, install VNC then develop on the VPS itself using the GUI via VNC?
Developing a website on a VPS
- Thread starter clay973
- Start date
Whether you develop a website on virtual/VPS/semi/dedicated web hosting does not matter,and the process can be the same (i.e. preference). There is no ONE WAY every one does it.
Some prefer to develop a website locally on their PC, and then upload it once completed. Others prefer to do development on the server, and upload or modify on the server. So they do their coding and what not as they go along with a live website. Some will leave up the index page, and work on it from a folder or renamed file.
What type of web hosting you have does not make a difference in regards to website development.
/2cts
Some prefer to develop a website locally on their PC, and then upload it once completed. Others prefer to do development on the server, and upload or modify on the server. So they do their coding and what not as they go along with a live website. Some will leave up the index page, and work on it from a folder or renamed file.
What type of web hosting you have does not make a difference in regards to website development.
/2cts
^^This
The only thing that really changes from shared hosting to a VPS/Dedicated are the folders. Sometimes the folder you use is htdocs, somtimes it's public_html, and sometimes it's www.
Aside from that, it's really the same once you get it running.
Depending on the needs of the domain, I could develop via xampp on my local machine and then port it over to the live site. Usually I just work on it on a live site to begin with because it's faster and noone is going to see it anyway for a couple days even if I got indexed.
Same here.
I do the basic shit locally. But once I have a workable site or it's around half way done, I put it on the server and do the rest there.
A lot of times, I will even launch the site before completed. Assuming people can sign up, get content, payment processor integrated etc.. Most people do not care if the site is not complete, and you might as well get some money rolling in while you work. Unless you are doing some major ad campaign or media blitz where you want a completed site.
pro tip: if you keep 2 copies of your site, make sure you always know which one you are working on. Otherwise you could be trying for hours to get something to work before you realize the site in your browser is not the one you are actually working on.
I understand you can do it both ways, I guess I was just wondering about best practice. Are you best to keep your VPS to a bare minimum (ie do everything via the console without installing the GUI) or is it standard to have the GUI accessed via VNC.
Does the GUI/VNC effect server performance?
Does the GUI/VNC effect server performance?
Displaying a graphical representation of anything requires more resources. The personal computer is a perfect example. It use to have a Kilobyte of RAM. When a nice GUI was introduced, it had 128 KB of RAM. Notice the significant difference?
You'll probably be using 100+MB of your RAM just to run the GUI on your server depending on the setup. It's not a major notice until you start running more and more sites.