loading...

re: How do you cover for domain name costs in FOSS projects? VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Maintaining a domain name costs almost nothing. I pay both it and hosting costs out of pocket and never notice the costs. And I work only part time...
 

The truth is it is less than 1 USD / mo right now, but I do care.

 

btw, how get cheap domain name ?

What have you tried? Actually, *.net is usualy not that expensive.

Also, you can get *.js.org for free, but it does have to be open source on GitHub Pages. Maintainers do pay, though.

You can always use a subdomain from one of many providers for free. For instance you can host a site on netlify 100% free, but your domain will be something like mareeps.netlify.com. Not a bad choice for some things.

If you have a bunch of side projects and do not want to start racking up domain name cost you can do like me and subdomain them from your main domain.

waylonwalker.com
find-kedro.waylonwalker.com
kedro-static-viz.waylonwalker.com

This works, but I believe it's very costly in terms of SEO.

great point for sure, I try a bunch of stuff out this way on a whim. The ones mentioned above are ones that I really should have their own domains for at their point.

What is the harm in prototyping like this and not getting a domain for them early on in the alpha stage? Am I hurting myself in the long term.

The only harm I can think of is that if some links to your prototype get spread around, they'll break when you switch to a full domain unless you keep up the test as a redirect indefinitely.

This was the last push that I needed. It's been in the back of my mind that I needed a new domain for my side projects. They all really fit under a good one that was available, so I bit the $12/year bullet and got a good domain for them.

They are all setup with netlify, so it was super simple. Create an exact copy of the website, let the domain stuff settle down then create a redirect.

git checkout <my-repo>
cd <my-repo>
git checkout --orphan redirect
git rm -rf .
echo "*    https://<shiny-new-domain>" > _redirects
git add .
git commit -m "setup redirect"
git push -u redirect

Now log into the old site on nelify and switch the production branch to redirect.

The above links now redirect automatically to the new domain.... now I need a site at the root.

I wanted to do this soon as they were starting to show up in the first fold of google search in some cases, not sure how google handles redirects. Everything with SEO seems a bit mysterious and better to be safe than sorry.

 

Consider the following: convert the cost of the domain to the time you'd have to work to earn that much money. It's less than an hour a year, right?

code of conduct - report abuse