Skip to content

Damien

My feedback

13 results found

  1. 79 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Damien commented  · 

    We have use cases where a server owner wants to grant a developer "unrestricted" access to do anything (e.g. including modification of nginx directives) for a single domain, but they do not want to give them access to modify things for other domains (so "additional admin" user is not appropriate).

    A way to grant greater power to a standard user, or a way to restrict an "additional administrator" to only work with specified domains/subscriptions would be useful (the latter would also overcome the problem where access to a server-level extension is required for the developer's work).

    Damien supported this idea  · 
  2. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damien supported this idea  · 
  4. 300 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Damien commented  · 

    Django is nice, but Python has a much broader ecosystem and our customers want to deploy Python apps in general (e.g. FastAPI, Flask), not only Django.

    In terms of what's important:
    - Python version management (different apps on the same server need different Python versions, and the developer should be able to specify their required one without needing sysadmin intervention; for example just like it's easy to select a different PHP version from the Plesk UI)
    - venv management / installation of dependencies (unfortunately the ecosystem is fragmented, so you have things like uv, pipenv, poetry with different toolchains preferred by different developers - unclear how to satisfy everyone / most people!)
    - A good (modern) way to run python apps (e.g. nginx + gunicorn + supervisor)

    Overall, yes it's currently possible to do all of these things on a Plesk server; but Plesk is not adding anything, so why pay for it? You can have the same (relatively painful) experience on a plain VM, but much cheaper.

    Damien supported this idea  · 
  5. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Damien commented  · 

    We use 360 monitoring to monitor the health of all of our servers as part of our managed hosting service.

    Depending on the alert, we handle it differently: some (most) go to our team via an Incident Management System (Squadcast) where they're triaged and pass through an escalation matrix; a small number of alerts are only for customer attention (if a server has a resource shortage, only the customer can purchase more resources to solve it).

    However, in this latter case we also want to provide visibility for our account management team. That requires a way for us to get the open alerts for a specific alert ID for all servers.

    In the UI you have https://monitoring.platform360.io/alerts/history?alertid=alert-id-here

    We just want the same via API so we can pull this data out to a suitable interface for our account managers.

    Damien supported this idea  · 
  6. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damien supported this idea  · 
    An error occurred while saving the comment
    Damien commented  · 

    We provide managed hosting services, so our customers have Plesk admin access but NOT root SSH.

    If we disable root SSH, we should also disable the workarounds like root user event handler scripts and root user cron VIA THE UI.

    But CloudLinux requires root user event handlers to manage CageFS, so please make it possible to still use root user event handlers via CLI whilst blocking their creation/management via Plesk UI.

  7. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Damien commented  · 

    Logging is essential - especially because:
    * git actions are executed using a different shell (/bin/sh) vs. whatever is configured for the system user (so environment or other nuances may cause unexpected errors)
    * errors are silent and fatal (the commands appear to executed as "command1 && command2", so command2 will only be executed if command1 has a clean exit code)
    * execution starts from the git deploy directory (not the system user home directory), so again this can be a source of user error when specifying the commands
    * troubleshooting and debugging all of the above is awkward: you have to write your own log files (e.g. redirecting command output) which is not at all elegant or intuitive for a typical developer who just wants to get their stuff deployed and working!

  9. 48 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    open discussion  ·  IgorG responded

    Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.

    IG

    Damien supported this idea  · 
  10. 108 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damien supported this idea  · 
  11. 252 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damien supported this idea  · 
  12. 62 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damien supported this idea  · 
  13. 71 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damien supported this idea  · 
    An error occurred while saving the comment
    Damien commented  · 

    These are remote services, so they can only scan webpage output. They are defacement monitors.

    The feature here is filesystem based, so it would identify new unknown files, or backend changes to files that may not cause any change to generated HTML)

Feedback and Knowledge Base