Skip to main content

Plesk delete domain would delete your entire site !

You read that right, when you delete a domain through Plesk control panel it would actually remove your entire site, including your mysql database. No warning given other than just "Are you sure ...?". For something so destructive like that, one definitely expect the message should read something like "This would delete your entire site including your database ...". Good UI design should closely mimic the real world scenario. When you delete your domain, what you would doing without the stupid control panel is open up the zone file and delete few lines there. Nothing you did there would affect your site code or the database. It just a dns record !

My fault here is I'm assuming too much. I assumed that no sane mind out there would setup the domain record so tighten with the application resources. Turn out that I'm dealing with an 'insane' mind ... sigh.

Here's an example how Webfaction control panel translate the real operations into UI metaphor.
  • You create a domain - The equivalent of adding entries into zone file.
  • You create an application - The equivalent of creating a directory to hold your PHP files or any kind of web framework you're using.
  • You define a website that would associate a domain to application at a given path (most of the time / but not limited to) - The equivalent of creating a virtual host entry in your apache config pointing to the document root or some other handlers.
So when you delete a domain, you just deleting a dns record, not your whole application. Plesk want to be clever though, when you create a domain it would create EVERYTHING so you would get a site up instantly. But when you remove a domain, it would also REMOVE EVERYTHING. The rest is just histrory ....
Labels:

Comments

Post a Comment

Popular posts from this blog

PHP with docker

A friend asking about a PHP library and I decided to test whether that library is working. But I don't have PHP environment setup (we're Python shop btw). But thanks to docker, that's easy these days. docker run -it --tty --rm --volume $PWD:/app --user $(id -u):$(id -g) composer require google/apiclient:^2.0 Then we just need to create the script to run, still in the same directory:- include_once __DIR__ . '/vendor/autoload.php'; $GCSE_API_KEY = "nqwkoigrhe893utnih_gibberish_q2ihrgu9qjnr"; $GCSE_SEARCH_ENGINE_ID = "937592689593725455:msi299dkne4de"; $client = new Google_Client(); $client->setApplicationName("My_App"); $client->setDeveloperKey($GCSE_API_KEY); $service = new Google_Service_Customsearch($client); $optParams = array("cx"=>self::GCSE_SEARCH_ENGINE_ID); $results = $service->cse->listCse("lol cats", $optParams); And we can run that script again using docker:- docker run -it --...
1 comment
Read more

Ubuntu 22.04 Wayland share screen

 After switching to Dell XPS 13 which running Ubuntu 22.04, I noticed that trying to share screen through Google Meet, it shows this:-    This - Use operating system settings, I never saw it before. Usually here we will be presented the windows that we want to share.  It turned out that screen sharing in Ubuntu 22.04 indeed an issue, due to the use of Wayland instead of Xorg as its display server. Many suggested to disable wayland and back to use Xorg. I try to avoid that since Wayland seems to works fine so far. After some searching, the conclusion seems we can make this working by installing some packages. sudo apt install xdg-desktop-portal xdg-desktop-portal-gnome But it turned out that I have already installed the packages! So what were the problems?  Well, turn out it's more psychological than technical. Since the pop up is different than what I'm used to before, I never click the allow button. But clicking the allow button we will see this:-   Which...
Post a Comment
Read more

The rise of localhost

I noticed a pattern in dex world, where you build client backend to participate in the network, and then build a web app that simply connect to  localhost:someport  for the UI. To check my scuttlebutt updates, I opened up http://localhost:8027/. For those using Ethereum Parity wallet, they can open it at http://localhost:8180/. ZeroNet users are browsing at http://localhost:43110/. But Parity for example, try to make it seamless, they still provide a dns - web3.site which then redirected to home.web3.site which simply resolved to 127.0.0.1. But this I think bring up some problem, especially non-tech user which think that Parity is a website hosted by Parity Technologies. I seen this in a some articles about the latest bug .
1 comment
Read more