I asked this on twitter and got invited here: :sli...
# seed
d
I asked this on twitter and got invited here: 🙂 Hoping there is a hidden feature to ignore a folder or some glob from changes. We have a lot of markdown files in our backend, that’s purely documentation. Any change triggers a redeploy of all services…
.seedignore
😛
f
Hey @Danny! What’s the folder structure like? ie.
Copy code
/
  docs/
  services/
    serviceA/
    serviceB/
The reason I ask is b/c there a couple of ways to ignore things in a repo, and I want to put in something that works for your setup.
d
yes pretty much like that with some serverless.yml in each services and also new work on SST in another
Copy code
/
  lpl/   (what you call docs)
    000-architecture.md

  services/
    service-x/
      ...typescript
    old-service/
      serverless.yml
      ...more typescript

  aws-stack/
    sst.json
    lib/
      ...only CDK
f
Got ya! The ignore feature is pretty high on our priority list.
I will keep you posted when it’s ready.
d
I might want to build a documentation website from the same repo someday. Would be useful if another build could then have different ignores
f
You mean each service have its own ignores, right?
ie. say u turned
lpl
into a service, u want to configure such that the
lpl
service ignores the
services
and
aws-stack
folders; while the other services ignores the
lpl
folder?
Copy code
/
  lpl/
  services/
    service-x/
    old-service/
      serverless.yml
  aws-stack/
    sst.json
d
you got it
ideally something like
.seedignore
Copy code
[service-*]
/lpl

[lpl]
/services
/aws-stack
or in seed.yml of course
I hope this has a high priority, would really speed up our builds 😅
f
Yeah, let me talk to the team about it today, and give you an estimate on when we are looking at.