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

re: 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...

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.

code of conduct - report abuse