-
Notifications
You must be signed in to change notification settings - Fork 11
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
Migrating mySQL database into strapi #104
Comments
Currently the VIM websites has a mysql database, which has to be migrated to strapi.
seems this expression was not accurate, according to just now reading the instr of strapi, it had a backend database still.. 😄
…--
shane.xb.qian
|
Apologies for the boat load of information here, in this LONG comment. I started following this repo because I wanted to follow the progress, I'm familiar with many dimensions of the challenges involved. My first impression was, "it will be difficult to help here" because the ./README.md reads more like napkin proposal (an important step BTW!) than a plan, and there is no reasoning is included, eg due to licensing and open source momentum, one would expect postgres to be the db of choice? My point is not which db to use, but this issue got my attention. It looks like strapi does support mysql https://docs.strapi.io/dev-docs/configurations/database but probably not the way it is a requirement. I appreciate there are a lot of opinions, and noise, with regard to undertaking a large project like this and I don't mean to distract! Although I want to contribute incrementally, I have no idea of the actual design, status, or workflow of the website refresh, and I anticipate many more experienced than myself are in the same situation. So my comment is about developing the framework for the design development and presentation to better crowd source from casual observers like myself. This is more of an inventory of ingredients that might contribute to an improved project development workflow, with a key goal of better solution crowd sourcing. As it may become be obvious, this solution was LLM developed, but please don't discredit it for being synthetic, I spent over an hour drafting the prompt (substantially longer than this introduction) to address the challenges I'm observing here. As a next step, I recommend going through the framework and annotating the line items with their applicability. Some items can easily be excluded with "too much control engineering" but I suggest going a step further to identify how the consequence of exclusion would play out, to better anticipate and pre-establish mitigations. Simply using the github interface, is not the solution, as elucidated in Is there a better project management method than maintaining the todo.txt manually? #14974 Many different project development frameworks could be highly effective. The key is establishing/publishing one, proactively selecting the steps relevant to the project, and in this case enabling efficient input from transient contributors. In my view that means defining a transparent process, recording the workflow in the repo, alongside the design and a record of solution evaluations, and lessons learned. Yes there is some overhead there, the benefit might not become apparent for six months, or when onboarding a new contributor, or another one, or just crowd sourcing a solution detail, all of these become more efficent when the larger context is presented in a more consumable manner. Thanks, Subject: Introducing a New Collaborative Framework for Our Website Transition Dear Contributors, We've recently encountered some challenges in our website CMS transition project, particularly regarding conflicting requirements and difficulty in coordinating our distributed team's efforts. In response, we're proposing a new collaborative framework to streamline our development process and enhance our ability to leverage the diverse expertise within our community. This framework aims to:
We believe this approach will help us overcome our current roadblocks and create a more robust, community-driven development process. In the following sections, you'll find a detailed breakdown of this framework, including its components, implementation plan, and expected benefits. We welcome your feedback and suggestions as we work together to refine and implement this new strategy. I've created a detailed framework to address the challenges and requirements you've outlined for transitioning the open-source project's website CMS. This framework is designed to facilitate transparent, collaborative development while accommodating contributors with varying levels of involvement. Key aspects of the proposed solution include:
This framework addresses the current challenges by providing:
The proposed solution empowers crowd-sourcing of innovative solutions by:
Justification for iterating working POC demos:
By implementing this framework, the project can effectively manage its transition to a new CMS while leveraging the diverse expertise of its community. The structure provides clarity and direction, while the flexibility allows for innovation and adaptation as the project evolves. Framework for Open Source Project Website TransitionCurrent Challenges
Proposed Solution: Collaborative Requirements and Design Management System1. Requirements Managementa. Requirements Classification
b. Requirements Documentation
2. Solution Evaluation Workflow
3. Design Documentation
4. Progress Tracking
5. Collaborative Platform
6. Communication Channels
7. Proof of Concept (POC) Demos
Implementation Plan
Benefits of the Proposed Solution
Empowering Crowd-Sourced Innovation
By implementing this framework, the project can harness the collective expertise of its community while maintaining a structured approach to development. This balance of structure and flexibility will enable the project to evolve efficiently and innovatively, even with distributed, part-time contributors. |
Thanks @georgalis for your input. I can't add to the project plan since im just a contributor, but I think this topic should be moved to the discussions. Feel free to copy+paste it there. |
Currently the VIM websites has a mysql database, which has to be migrated to strapi. The columns of interest for a first migration are the users and the scripts. Following thoughts/discussions have been made:
=> Users could be migrated on the fly => Additional requirement is to use a new hashing algorithm for the password
=> There script tables of interest for a first migration are: vs_scripts, vs_script_source, vs_script_ratings, vs_script_downloads
=> Topic is also strong related with seeding
Issues/concerns:
=> When migrating scripts, there is a direct connection to the users
- This is critical if the user migration is done on the fly => All scripts should be available from the beginning even though only a limited amount of users is migrated
- Possible solution: Adding placeholder users for not migrated users and only actually migrate and connect them to scripts in case of on the fly migration (e.g. first login)
The text was updated successfully, but these errors were encountered: