vendor.css and client.css not found about opensource-management-portal HOT 5 OPEN

Further investigations brought me to ember-app issue. Lack of my js knowledge doesn't help a lot here :(

from opensource-management-portal.

@ElenaForester I bet our prior Ember app is being included in the default version, even if you don't have your own ember app deployed...

There's already some dynamic code in the app to determine whether the Ember client app is being deployed... if I can plumb that into the view state, we could exclude those files...

from opensource-management-portal.

Thanks for response!

But is there any workaround to make it work (at least temporarily)? Maybe there is some view I can use?

Off topic:
I'm playing with the app now and finding it very promising, seems it will be super convenient to manage people, teams and repos (instead of using github terraform provider which I'm using now). But have some questions:

• is there any roadmap to check upcoming features & improvements?
• will it be possible to manage repository webhooks, branch protection configs, topics etc from the app? Do you have plans work on these features?
• are there any plans to add possibility of team creation from the app but not in Github UI? (Currently it redirects me to the Github team creation page)
• would be very nice to have more detailed documentation :)

Thanks in advance!

from opensource-management-portal.

Hi, I've run into this issue too and did some debugging. As written in the docs, it's possible to define a custom assets package to be used instead of the default-assets-package. But if I've a look into the the default-assets-package, I can't find any client.(js|css) or vendor.(js|css) files. Also not in the generated public folder after running Grunt. Maybe those files are just missing in the default assets package? Or any hints where I can find those client and vendor files? Seems like jQuery is not loading correctly too.

from opensource-management-portal.

This issue has been identified as stale because it has gone 30 days with no activity.
The issue will be closed in 10 days. If this is incorrect, simply comment on the issue, or remove the stale label.

from opensource-management-portal.