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
{{ message }}
This repository has been archived by the owner on Sep 11, 2018. It is now read-only.
I've been using this boiler plate for a few months and also built a nice little 3 page project. It worked out all fine, but now I want to build a bigger project that'll have more than 7-8 such tiny projects.
So each one of them is a module and I want a separate repo.
Parent
|______Module 1
|______Module 2
|Module 3
|... and so on
I did read the Fractal project setup, but the documentation is very limited, I tried all day today and couldn't really figure out how can I extract each 'route' into a separate project setup that can act as an individual repo which can then be included by the parent to build it.
Other important factors: These projects then get into a docker either one or separate docker containers, but I'll figure that out if I get help just separating the routes and parent project setup.
I'm thinking each route will have its own reducers and actions, so that way I don't have to touch the parent at all, the only thing the parent does is 'builds' it.
Any help is appreciated, an example would be awesome! Thanks!
The text was updated successfully, but these errors were encountered:
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
Hello,
I've been using this boiler plate for a few months and also built a nice little 3 page project. It worked out all fine, but now I want to build a bigger project that'll have more than 7-8 such tiny projects.
So each one of them is a module and I want a separate repo.
Parent
|______Module 1
|______Module 2
|Module 3
|... and so on
I did read the Fractal project setup, but the documentation is very limited, I tried all day today and couldn't really figure out how can I extract each 'route' into a separate project setup that can act as an individual repo which can then be included by the parent to build it.
Other important factors: These projects then get into a docker either one or separate docker containers, but I'll figure that out if I get help just separating the routes and parent project setup.
I'm thinking each route will have its own reducers and actions, so that way I don't have to touch the parent at all, the only thing the parent does is 'builds' it.
Any help is appreciated, an example would be awesome! Thanks!
The text was updated successfully, but these errors were encountered: