| |
Perff
Administrator
Posts: 1679 |
CSDb V2
As some of you might have seen, there have been talked a bit about a CSDb V2.
I have also had this idea for some years now, because of some basic flaws in the originally database design of CSDb.
Now is the time to try to do something about it.
But we, the current CSDb staff, don't have the resources to do this, so we need your help!
Here is what we need:
1. Somewhere to host CSDb V2. The current hosting for CSDb is not very good, as some of you might agree on, and it would be very difficult for more people to develop on it, so a new hosting place is needed.
The requirements for such place are not to much. Talking about performance, CSDb can run on any normal computer today with no problem, and a few gig of disk space should be ok. The daily trafic sums up to about 40-50.000 hits and 300-400mb.
Some kind of CVS or similar to make it easy for multiple people to develop on it, is also required. (PS. We got no money! )
2. People that would help. First of all we need some willing developers - PHP & SQL. I don't think we should get too many - 2-3, perhaps 4 (plus myself :) ) We'll figure that out.
Also some design people, to make the site look kewl. :) And finally some people with deep knowledge of the scene so we are sure to get around every corner in the design phase.
3. Time and patience. :)
The plan is then to put togehter a CSDb V2 team (not to big, 6-8 people tops), and figure out exatcly how to make it. Of course we should look at the current CSDb, but I sugest we make everything from scratch.
Most importaint is the design phase. We must try to take all into account when designing it. I think this is the most importaint part of it all.
Then it gets coded, designed etc, and when it is ready for release, we transfer all the data from CSDb to CSDb V2. :)
Even though the CSDb team is the ones who should make it, it dosn't mean that the rest of you have nothing to say. Perhaps we could post our plans somewhere for all of you to comment on.
That is roughly how I see it.
Now lets have a nice little discussion. :) |
|
... 91 posts hidden. Click here to view all posts....
|
| |
TDJ
Registered: Dec 2001
Posts: 1879 |
Quote: ...primairily focus on...
He he heeee ha ha haaaa
Well, given that I am involved too, you can understand why the petname for this project is FSDb ;-) |
| |
Conrad
Registered: Nov 2006
Posts: 847 |
I know this is an old thread, but has there been any development for this idea at all? |
| |
instant
Registered: Mar 2020
Posts: 20 |
This thread seems pretty stale. I've got free cycles so I've started on things. If anyone is interested in helping please get in contact with me. Perff's help would be greatly appreciated of course (even at the bare minimum) but I understand if he is no longer interested in this.
Backend:
nodejs
appwrite.io
Middleware:
graphql
Frontend:
Nuxt3 or Flutter 2
(could do both actually. nuxt for web and flutter for mobile apps? or Flutter for both web and apps)
That is what I'm thinking. I'm open to other ideas but would like to stick to some of the latest tech. Then I'm learning something new that will benefit me with other projects while rebuilding everything at CSDb. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11364 |
The most important thing is a proper redesign of the database structure, fixing all the little flaws we learned about in the past decades.
After a few iterations of design/review/fixing that - it makes sense to start thinking about redoing the website :) |
| |
instant
Registered: Mar 2020
Posts: 20 |
I'm thinking a NOSQL database would be best. The current database seems over engineered. JSON documents would work just fine and then maybe a small database just for the indexes for searching. Appwrite.io is perfect for this. |
| |
Digger
Registered: Mar 2005
Posts: 427 |
Another thread from the grave. I think I've posted it already years ago – the only way IMO to move forward is to make CSDb open-source and let ppl fix issues, there's a few of us knowing modern JS stacks.
Ofc there needs to be a team to approve PRs. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11364 |
As someone who has seen the source i can assure you: there is no way to fix all the mess that needs fixing in the existing codebase. In any case, the biggest and most important task is to create a sane db structure that is future proof and migrate the data to it. Making the frontend to that db then is just the icing on the cake. |
| |
Seven
Registered: Jan 2002
Posts: 202 |
Tech stack first, concept second. I see we're in good hands. |
| |
instant
Registered: Mar 2020
Posts: 20 |
I'll have something worked out to show soon. PM me if you are interested in helping. :) |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
Quote: The most important thing is a proper redesign of the database structure, fixing all the little flaws we learned about in the past decades.
After a few iterations of design/review/fixing that - it makes sense to start thinking about redoing the website :)
@instant: Really listen to this.
If I were you I'd start interviewing the main contributors to the Database, like Hedning, to properly understand what's needed for preservation and history.
Once you have a proper design, do an API to expose it. You can for sure use GraphQL or slap GraphQL onto a REST API, whatever floats your boat.
After that, think about UI tech choices. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 - Next |
