Configure assets controller(s) #475

Closed
jbrey opened this Issue Apr 21, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@jbrey
Contributor

jbrey commented Apr 21, 2015

Hey,

It would be great if we could create several instances (via cfg files?) of the AssetController by giving the following properties:

  • the path in the bundle or on file system,
  • the alias on which the resources are published,
  • if we manage assets from bundles.

Cheers
JB

@cescoffier cescoffier added the planned label Apr 21, 2015

@cescoffier cescoffier added this to the 0.8.1 milestone Apr 21, 2015

@cescoffier cescoffier self-assigned this Apr 21, 2015

@cescoffier

This comment has been minimized.

Show comment
Hide comment
@cescoffier

cescoffier Apr 21, 2015

Member

Right now it's only possible to configure the 'external' asset directory (so from file system). We should add:

  • the internal bundle directory (default to assets)
  • the root path on which the resources are exported (default to /assets)

We should check that the resources exposed by these new configured instances are listed correctly on the /assets/ page.

Member

cescoffier commented Apr 21, 2015

Right now it's only possible to configure the 'external' asset directory (so from file system). We should add:

  • the internal bundle directory (default to assets)
  • the root path on which the resources are exported (default to /assets)

We should check that the resources exposed by these new configured instances are listed correctly on the /assets/ page.

@jbrey

This comment has been minimized.

Show comment
Hide comment
@jbrey

jbrey Apr 22, 2015

Contributor

Thanks !

Contributor

jbrey commented Apr 22, 2015

Thanks !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment