enhancement: Spooling documentation mentions available location

[73VW]

DESCRIBE YOUR PR

This PR enhances the spooling section of the relay configuration page.

It clarifies that only /etc/relay and /work are writable in the container.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

• Urgent deadline (GA date, etc.):
• Other deadline:
• None: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
  Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

@73VW is attempting to deploy a commit to the Sentry Team on Vercel.

A member of the Team first needs to authorize it.

[Dav1dde]

I think the intention is to mount a directory into the container, which then needs to be writable by the user under which Relay is running. Using an existing directory (not mounted) is generally not a good idea.

@jjbayer wdyt, also are these spooling docs still up to date?

[jjbayer]

I think the intention is to mount a directory into the container, which then needs to be writable by the user under which Relay is running. Using an existing directory (not mounted) is generally not a good idea.

Yes, I left a suggestion accordingly.

wdyt, also are these spooling docs still up to date?

Thanks for the hint, I will verify.

[73VW]

Hey @jjbayer @Dav1dde the documentation about spooling is not up to date! We've learned it the hard way.
For example, spool.envelopes.max_memory_size does not exist anymore. Check this.

I have checked in the code base and the last link I have provided is the real documentation.

I can update this MR if you want me to!

[jjbayer]

@73VW thanks, will update in #15850.