You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2023. It is now read-only.
As the title says—basically, it was a neat tech demo, and a site like http://prod.drupalvm.com/ is nice to have around... but it's yet-another-thing I have been maintaining for a while. I would rather not maintain it, nor continue paying the extra $5/month in perpetuity just to show off a feature that likely <1% of Drupal VM's users use.
Also, it adds a little weight to some of my decisions about backwards compatibility that I could more readily make if I knew people weren't running Drupal VM's codebase to build secure production environments.
I wouldn't really be taking away much (if any) functionality, but this issue would:
Make sure that using Drupal VM for prod is labeled as something experimental, and for which you would receive no official support. (This was already the case, but need to be explicit).
Update my old 'soup to nuts' blog post to mention that this type of usage is not really recommended .
Delete the prod.drupalvm.com site, archive it's codebase, etc.
The text was updated successfully, but these errors were encountered:
As the title says—basically, it was a neat tech demo, and a site like http://prod.drupalvm.com/ is nice to have around... but it's yet-another-thing I have been maintaining for a while. I would rather not maintain it, nor continue paying the extra $5/month in perpetuity just to show off a feature that likely <1% of Drupal VM's users use.
Also, it adds a little weight to some of my decisions about backwards compatibility that I could more readily make if I knew people weren't running Drupal VM's codebase to build secure production environments.
I wouldn't really be taking away much (if any) functionality, but this issue would:
The text was updated successfully, but these errors were encountered: