• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Domain Setup - Best Practice

P

pseconds

Guest
Question for you all... is there a best practice for setting up accounts? Like are people typcially setting up a client for every domain, or just setting up new domains under "my domains?"

Unless I'm missing something, it seems a little cumbersome - after the domain is created, I have to go back and grant control panel access, enable spam filtering on mailboxes and a few other tweaks.

I've got 15 Ensim servers and am just learning Plesk, so any advice is welcome.

Thanks!
 
Hi,

No there is no such best practice solutions. All depends on your needs.

You can create domains with templates where you can set required parameters(Domains -> dom template).

Also you can use event handlers to setup parameters(using Plesk cli utilities) during domain creation:
Plesk -> Server -> Event Manager
 
Back
Top