codeandcanvas:

Understood the value of separating a production from a development environment in regards to my own website.

Following a tip from a very good friend, it is a good idea to have a website without tracking on it if you, like me, are still just running a personal website, rather than a commercial one.

So, I’ll do it like this: I will keep my personal website as is while I will keep working on my new website, using a different url to the one I am for my website.

So, when I am done with the new, I can just switch.

Fingers crossed, I don’t have all my books with me, so I’m playing this by intution alone.

Using Plesk and my backups, I could easily roll back my changes to a day prior to what I did today.

I am sort of digging how clean I made my website in regards to it doing any kind of tracking.

I might keep this for my fraidycat people, instead of throwing it away: when I do the switch, I think I want to have a failsafe version of my website around. Like putting it into failsafe.mariobreskic.de or even old.mariobreskic.de (safe.mariobreskic.de sounds semiotically best, I just realized), doing some easy mirroring of content between the future new website and the one without tracking.

Why do I want this? My good friend, I want out of my own behavioural loop of creation and oblivion: I want creation now, only, the oblivion comes later anyhow.

Source: My after‑hours blog on Tumblr Code & Canvas