This is a
playground to test code. It runs a full
Node.js environment and already has all of
npm’s 400,000 packages pre-installed, including
readmeio-sync with all
npm packages installed. Try it out:
This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.
A tool for managing your
Readme.io documentation locally.
NOTE This project is not officially supported by ReadMe. For support, please use the GitHub Issues for this project.
For Regular Use:
npm install -g readmeio-sync
For Development & Testing:
git clone firstname.lastname@example.org:mobify/readmeio-sync.git cd readmeio-sync npm link cd ../<your_readmeio_project> npm link readmeio-sync
This tool logs into Readme.io for you in order to upload files. For this to work, it needs your credentials!
README_PASSWORD environment variables need to be set for
readmeio-sync to know your credentials.
export README_EMAIL=<readmeio_account_email> export README_PASSWORD=<readmeio_account_password>
readmeio-sync differentiates between your production/staging projects using the
You can set the name of these projects using the
readmeio-sync config -s <staging-project-slug> -p <production-project-slug>
This will generate a
syncConfig.json file with the proper keys set.
Initialization allows you to download all your existing content from Readme.io.
It also creates a new
syncPaths.json file which represents the structure of your documentation and links to all your local content directories.
This will use the
production slug that you should have configured in step 3.
Upload allows you to push updated content to Readme.io. This might include:
Once your project has been initialized and has a config, you can upload using the upload command.
readmeio-sync upload [--production]
Including the production flag will push the content to production.
When you remove content files, it does not auto-magically delete it from your Readmeio project too. Upload only does updates and creates.
If you have out of date content on your Readmeio project, you can use the
clean-remote command to remove all content that is not specified in your filesystem.
readmeio-sync clean-remote [--production]
This will look at the state of your project, compare it to the state of your documentation, and delete whatever is not specified locally. This will be done for staging unless the production flag is set.
Sometimes 'ghost' documents can appear in Readme. These are documents that have been created but are no longer shown in the list of documentation. Since you can't see them in the list of documentation, they can't be deleted.
Additionally, attempting to create a new document with the same slug as a ghost doc will cause a document with a numbered slug to be created instead (eg. getting-started -> getting-started-1).
To make sure none of your docs have slugs associated to ghost documents, an
--aggressive flag can be set.
When this flag is set,
readmeio-sync will clean documents that only exist in Readme AND docs that only exist locally (and perhaps haven't been uploaded due to slug naming conflicts).
readmeio-sync clean-remote [--aggressive]
Note: If you remote clean a project and it removes all the documentation, Readmeio will not allow you to go into the documentation section. You will need to upload new content with the
readmeio-sync upload command to get it working again.)*
For an in-depth explanation of how to configuration works, see CONFIGURATION.md
Doing a remote-clean when you have no documentation in your
syncPaths.json file will cause all your documentation on readme.io to be deleted (after all, you are saying "delete all the things I don't have specified locally"...which is nothing!). Having no documentation causes Readme.io to break (you can't enter the documentation section of the site). To fix this you will have to add a document to your
syncPaths.json and upload it...or get in contact with Readme.io and admit you were using internal APIs (OOPS!).
Custom pages are not versioned. Ideally they would be, and that's why the "customPages" section exists in each version of the
syncPaths.json. When you initialize a project, the same custom pages will be downloaded for both versions and specified separately in the
syncPaths.json. If you try and upload while the pages are specified in both versions, duplicates will be created.
You can fix this by:
1. Deleting all the custom pages in all versions except one (however if you
clean-remote with this configuration, all custom pages will be deleted and you'll have to upload again).
clean-remote after each upload.
This tool is still in beta and may burn your project to the ground. Test it out, log issues, submit PRs.