Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

initial commit of drupal doc for upsun #4382

Merged
merged 4 commits into from
Feb 12, 2025
Merged

Conversation

gilzow
Copy link
Collaborator

@gilzow gilzow commented Feb 11, 2025

Why

Closes #4381

What's changed

Adds Drupal Guide to Upsun docs

Where are changes

Updates are for:

  • platform (sites/platform templates)
  • upsun (sites/upsun templates)

Copy link

Your Platform.sh environment has successfully deployed. 🚀

See the changed pages:

Platform.sh docs
Upsun docs

redis: 'cache:redis'
mounts:
# The default Drupal files directory.
'/web/sites/default/files':
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gilzow maybe writing mounts in a shorten version could help readability?

        mounts:
            # The default Drupal files directory.
            '/web/sites/default/files': { source: storage, source_path: 'files' }
            # Drupal gets its own dedicated tmp directory. The settings.platformsh.php
            # file will automatically configure Drupal to use this directory.
            '/tmp': { source: storage, source_path: 'tmp' }
            # Private file uploads are stored outside the web root. The settings.platformsh.php
            # file will automatically configure Drupal to use this directory.
            '/private': { source: storage, source_path: 'private' }
            # Drush needs a scratch space for its own caches.
            '/.drush': { source: storage, source_path: 'drush' }
            # Drush will try to save backups to this directory, so it must be
            # writeable even though you will almost never need to use it.
            '/drush-backups': { source: storage, source_path: 'drush-backups' }

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the longer format, while it does increase the page length, is easier to read. @Kemi-Elizabeth do you have any insight/input?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When you say shortened version, do you mean without the comments? I found it quite easy to read but I was taking my time. I understand that it might not be scannable, but do we want this to be easily scannable? I would think that people taking the time to read this article would want to take in all the details even if it makes the page a bit longer?

start: 'cd web ; drush core-cron'
runtime:
# Enable the redis extension so Drupal can communicate with the Redis cache.
extensions:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

            extensions: { redis, sodium, apcu, blackfire }

?

#
# We don't want to run drush commands if drupal isn't installed.
# Similarly, we don't want to attempt to run config-import if there aren't any config files to import

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tried to remove all uses of first person plural and tried to tone down the conversational TOV so that it fits more with the formality of the Docs as opposed to the DevCenter articles. I did see that some of the comments within the code are a bit colloquial (ie. the one above uses a tone that could come across slightly conversational). Do we want to keep those as they are (I'm not sure if changing the comments might affect the code snippet example)? @gilzow

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Kemi-Elizabeth i think the comments are important so the reader know what the commands are doing. We could change it to be:

# Don't run drush commands if drupal isn't installed.
# Don't run config-import if there aren't any config files to import

?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect! Yes, I still think the comments are necessary, I just wasn't sure if we could change the wording. But that's perfect and definitely along the lines of what I was thinking.

gilzow and others added 2 commits February 12, 2025 11:41
@Kemi-Elizabeth Kemi-Elizabeth merged commit 2aaad09 into main Feb 12, 2025
16 checks passed
@Kemi-Elizabeth Kemi-Elizabeth deleted the 4381-drupal-guide branch February 12, 2025 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add Drupal guide
4 participants