I would like to build a brand new meteor project using an old meteor project as my starting point.
I assume i can’t just copy the whole old project folder and work from there, as the old app’s .meteor folder contains data about the old app including the .git, the old .db, and an .id as well as other information.
Is there some place where the project’s .meteor folder is documented so I can decide what to keep and what to discard when setting up the clone as a new project?
Thanks.
meteor reset --db will delete the old db.
running git init on the command line inside the cloned folder will init the git repo in that folder.
thanks. that helps.
what about the .id. How should I generate a new .id?
I did a quick check via whatever AI the Warp terminal app is using:
if I delete the .id file, will meteor automatically generate a new one?
Yes, Meteor will automatically generate a new .id file if you delete the existing one. When you run meteor (or other Meteor commands like meteor run, meteor build, etc.) and the .id file is missing, Meteor will create a new one with a fresh unique identifier.
However, there are a few things to consider:
- Deployment implications: If you’re deploying to services like Galaxy or other Meteor hosting platforms, changing the project ID could cause issues with deployment continuity. The hosting service might treat it as a new app rather than an update to the existing one.
- Analytics/Statistics: Package authors use these IDs for aggregated statistics, so changing it would start fresh tracking for your project.
- Version control: Since the comments in the file recommend checking it into your repository, deleting and regenerating it would create a change that you’d need to commit.
If you just want to see this behavior in action, you could temporarily rename the file (e.g., mv .meteor/.id .meteor/.id.backup) and then run a Meteor command to see the new ID get generated, then restore the original if needed.
AI models can be wrong of course. But the test it suggests at the end seems reasonable.