Edge: some upcoming (breaking) configuration changes

Edge
1

In the ongoing move to slowly move away from SETTINGS as a “special” page, and even to be able to move away from space-config in general in the future I’m migrating some SETTINGS into server-side environment variables.

This means that on Edge these particular SETTINGS will stop having effect (and need to be configured via equivalent environment variables):

  • indexPage is now to be configured using SB_INDEX_PAGE
  • spaceIgnore is now to be configured using SB_SPACE_IGNORE

All this will be documented here: Install/Configuration

2

The power of doing this on a settings page is that you can easily modify it from the client without restarting the server (just a reload).
The risk is that, even on a read-only space, you leak date (especially with things like space ignore or secret values).

Is everything eventually moving to server side config or will we still be able to configure some things via a page or block?

3

No no, generally configuring SB from pages (like SETTINGS) will stay as it is.

There’s only a few things I’d like to move out. For now only indexPage and spaceIgnore, because these two impact server boot behavior.

1 Like
4

Will SB_SPACE_IGNORE still support ignoring multiple patterns?

5

Yes, it should if you can somehow encode multiple lines in an env variable?

7

I guess you can:

$ export TESTENV2="Line1
> Line2
> Line3
> Line4"
$ echo "$TESTENV2"
Line1
Line2
Line3
Line4
$ echo $TESTENV2
Line1 Line2 Line3 Line4

You have to use double quotes with bash though. I can test edge later, but maybe it’ll just work w/ deno

1 Like