Hi Trent,
First question is what is in your heart? Is the path you are following
where you want to go? Do not read anything into my question. It is all
about you, and what you want to do.
I would suggest Bluehost and get as many months as you may need. I know
they have a discount for new customers and I think you have to buy a
year or more to get the discount - worth investigating. I think they
use cPanel, which may or may not be of use to you.
Make sure you have shell access to your shared hosting server.
I would stay away from GoDaddy for the only reason of price. I would
encourage you look at them and see how they stack up.
I used to buy my domains at GoDaddy until the price kept increasing.
Now I am with NameSilo.
If you are not going to keep the website you might consider a hypervisor
instead of shared hosting. Look at VirtualBox and Proxmox. By using a
virtualization software you can build your own server (good for learning
and resume) and save a few bucks. It will take some time and there is a
learning curve.
I recently configured Proxmox on a old piece hardware and am glad I did.
Keith
On 2023-01-25 07:53, trent shipley via PLUG-discuss wrote:
I'm on the bench with my employer asd studying test driven development
using Harry Precival's Test-Driven Development with Python. Percival
uses a simple web site on Django as the practice or example project.
In chapter 9 the baby website gets put on a real hosted web server.
It needs to be an olde fashioned service where you have the freedom to
do a lot of admin work. That is, you need to have enough rope to hang
yourself. I also need a domain name and two sub-domain names. Price
is important. I will probably finish the tutorial book and throw the
site away instead of keeping it as a personal website.
Has anyone got any suggestions for where to get a domain name and a
hosting service?
Trent
Choosing Where to Host Our Site
There are loads of different solutions out there these days, but they
broadly fall into two camps:
* Running your own (possibly virtual) server
* Using a Platform-As-A-Service (PaaS) offering like Heroku,
OpenShift, or PythonAnywhere
Particularly for small sites, a PaaS offers a lot of advantages, and I
would definitely recommend looking into them. We’re not going to use
a PaaS in this book however, for several reasons. Firstly, I have a
conflict of interest, in that I think PythonAnywhere is the best, but
then again I would say that because I work there. Secondly, all the
PaaS offerings are quite different, and the procedures to deploy to
each vary a lot — learning about one doesn’t necessarily tell you
about the others. Any one of them might radically change their process
or business model by the time you get to read this book.
Instead, we’ll learn just a tiny bit of good old-fashioned server
admin, including SSH and web server config. They’re unlikely to ever
go away, and knowing a bit about them will get you some respect from
all the grizzled dinosaurs out there.
What I have done is to try to set up a server in such a way that’s a
bit like the environment you get from a PaaS, so you should be able to
apply the lessons
Percival, Harry. Test-Driven Development with Python (pp. 263-264).
O'Reilly Media. Kindle Edition. (2017)
Or free at: https://www.obeythetestinggoat.com/pages/book.html
---------------------------------------------------
PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
