You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@notzippy should we allow skeletons to control the app.conf template?
if we add more official templates, e.g. zurb’s foundation, etc, we’ll have to maintain multiple app.conf templates, right? Maybe we should allow skeletons to override it, but we should set a default app.conf when creating a new revel app (in the cmd repo)?
The text was updated successfully, but these errors were encountered:
What about a "base" app.conf.template in the skeletons project ? then all app.conf.template files could import that base one and then there would be no need to worry about having multiple templates to update ?
Notes from gitter chat:
https://github.com/revel/cmd/blob/master/revel/new.go
https://github.com/revel/cmd/blob/master/revel/new.go#L202
https://github.com/revel/skeletons/blob/master/basic/bootstrap4/conf/app.conf.template
@notzippy should we allow skeletons to control the app.conf template?
if we add more official templates, e.g. zurb’s foundation, etc, we’ll have to maintain multiple app.conf templates, right? Maybe we should allow skeletons to override it, but we should set a default app.conf when creating a new revel app (in the cmd repo)?
The text was updated successfully, but these errors were encountered: