-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Move front end/backend into separate repos? #44
Comments
I agree, though it will take some work. It'll be a task for the holidays when I've got the time for it. I'm thinking of keeping the backend in this repo and moving the frontend to a separate one called "mann-eller-kvinne-frontend" or something among those lines. |
Would be pretty cool. At the moment, I'm fantasizing about replicating the API using some different technologies such as
|
Sounds good to me! I'm open to the idea of rewriting the backend i.e. using some if not all of the technologies you've mentioned. I find it hard to see the point of adding kubernetes support though, but other than that I agree. |
In this use case, it might not be necessary, but if we were to care about dynamic scalability and minimal downtime Note that none of this has to be hosted by you. You can still do it the old fashioned way. Wouldn't it be pretty neat to have kubernetes on your resume? 😎 |
True true 👀 |
This calls for a rewrite of the frontend as well. It should be pretty easy to do and can be done in a couple of hours. I will get started on that in the near future |
I have now made a branch called "rewrite" in this repo and have started making some initial changes. I'll come back to you once the base structure of the rewrite is complete and (partially) working. |
Perhaps it's more clean given that the programs can be run independently.
Wdyt?
The text was updated successfully, but these errors were encountered: