-
Notifications
You must be signed in to change notification settings - Fork 558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slim & stateless version of the boilerplate #156
Comments
@dzotokan Definitely! This has been bothering me because it took me at least 30 minutes stripping it out that day.
Good thinking. Perhaps we only need to keep that branch up to date when there are webpack or config changes then. |
I'm going to try to work on this guy. The refactoring here will mainly be in the The easiest approach I can think of is to:
I'll have a go to see how much work this will take + whether it's a good solution |
Closing as issue is tackled in #372 |
Cloned the project and didn't need any of the auth/db/models things.
Any thoughts on stripping those out and maybe creating a separate branch?
i.e. Static react app with routes and an empty
need
maybe, with no authentication and DB. Would be more suitable in a microservices architecture land perhaps.Happy to write up a PR removing those things (not for
master
obviously).The text was updated successfully, but these errors were encountered: