Partially deleting a site

Jack Kleinfeld

• February 21, 2020 20:09

I am not clear on some details. 

I have built a site that is hosted on a brizy.site sub-domain.  I specified the subdomain, but I don't know if that matters (please comment on that).  I have now migrated the completed site to a customer's hosting account.  I would like to delete the published sub-domain, but NOT lose access to the project and the work in the dashboard.  Is that possible?  Does "delete" do that or completely remove the project? 

 

TIA

Jack 

0

• 

  Alex

  • February 22, 2020 15:24

  Hi Jack,

  the DELETE options will remove the project, not the subdomain.

  All cloud projects are hosted on a subdomain automatically when published. It needs a name to be able to find it through many projects. You cannot have an unpublished project on the cloud. You can customize the subdomain, but can't delete it.

  The thing is that you must have an address and you have two options: custom domain or Brizy subdomain.

  0
• 

  Jack Kleinfeld

  • February 22, 2020 15:44

  I just tested by creating a new project.  I see that it automatically created a subdomain cloud version when I hit publish in the editor mode. 

  I see that hitting Publish in the dashboard on an already published project lets me select subdomain and I can rename the project site.  The original name was related directly to the client, and having published the real site on their hosting I wanted to divorce them from the subdomain.  I wanted to delete the subdomain and keep the project.  Since I can't do that, I've changed the cloud name.  It's a compromise, but acceptable.  

  Please clarify.  If I use delete, it deletes the project, but does the subdomain remain?  Or do both get deleted? 

  Thanks

  0
• 

  Alex

  • February 25, 2020 08:00

  The "Delete" option will delete your project. The subdomain remains but will return a 404 Not Found error because the project does not exist at that address.

  0
• 

  Jack Kleinfeld

  • February 25, 2020 13:18

  Thanks for the explanation.  

  That sounds inherently insecure - the content is still there, so couldn't it be found by methods other than just entering the URL? It also seems like it consumes your server space.

  Would it make sense to give the user the option to delete the subdomain (and retain the project)?  This would be especially applicable in those cases where something has been developed using the subdomain and then transferred elsewhere.  Once transferred, additional changes might be made and then there are disparate versions floating around.  Just a thought. 

   

  0
• 

  Alex

  • February 26, 2020 09:46

  I'll discuss this with the team. But, why not use the subdomain rename instead of deleting the subdomain? 

  Something was developed using the subdomain and then transferred elsewhere. Once transferred, you just need to change the subdomain from dev_project1.brizy.site to transfered_project1.site. So, it will not be accessible thought dev_project1.brizy.site, but it will be available on transfered_project1.site and no one knows this subdomain except you.

  0

Please sign in to leave a comment.