||4 months ago|
|.github||4 months ago|
|bin||3 years ago|
|exe||3 years ago|
|lib||2 years ago|
|test||3 years ago|
|.dockerignore||3 years ago|
|.editorconfig||3 years ago|
|.gitignore||2 years ago|
|CHANGELOG.md||2 years ago|
|CODE_OF_CONDUCT.md||3 years ago|
|Dockerfile||2 years ago|
|Gemfile||3 years ago|
|LICENSE||2 years ago|
|README.md||2 years ago|
|Rakefile||3 years ago|
|entrypoint.sh||2 years ago|
|env.sample||2 years ago|
|outliner.gemspec||2 years ago|
A simple HTTParty based wrapper for the Outline API. It also offers a one-line import option to let you migrate an existing set of Markdown files to Outline. For quickly running export/import commands, you can use the Docker Image as well.
Add this line to your application's Gemfile:
And then execute:
Or install it yourself as:
$ gem install outliner
The API Client automatically picks up the Token from the
OUTLINE_TOKEN environment variable. All the API calls are available with the
. replaced with a
_ in the method name. So if you need to call the
collections.remove_user API, use the
require 'outliner' client = Outliner.new('https://knowledge.example.com') pp client.auth_info pp client.collections_list(offset: 0, limit: 10)
outliner can be used to import an existing collection of documents into Outline. To do this, run:
export OUTLINE_BASE_URI="https://kb.example.com" export OUTLINE_TOKEN="PUT YOUR TOKEN HERE" export SOURCE_DIRECTORY="/home/user/wiki" export DESTINATION_COLLECTION_NAME="Archive" bundle install outliner outliner-import "$SOURCE_DIRECTORY" "$DESTINATION_COLLECTION_NAME"
outliner can be used to run a one-time export of all documents in Outline to a local directory. To do this, run:
export OUTLINE_BASE_URI="https://kb.example.com" export OUTLINE_TOKEN="PUT YOUR TOKEN HERE" # Ensure that this exists and is writable export DESTINATION_DIRECTORY="/data" bundle install outliner outliner-export "$DESTINATION_DIRECTORY"
You can use the pre-built docker image to run the above commands as well. See the following commands for examples:
env.sample file to
.env and update the values there.
Downloads all collections from Outline, and exports them as nested markdown files inside the given directory (
/data inside the container, mount it accordingly.)
docker run --env-file .env --volume /tmp:/data \ captn3m0/outliner \ export \ /data
Imports all markdown documents in a directory to a named Collection on outline. Creates the collection if it doesn't exist.
docker run --env-file .env --volume /path/to/wiki:/data \ captn3m0/outliner \ import /data "Archive"
Does a export from Outline, and pushes the corresponding result to the Git repository. Currenly does a force-push to the repository. Use with care.
Note: Sync is currently only available as a Docker Command
docker run --env-file .env --volume /etc/ssh/private.key:/root/.ssh/id_rsa captn3m0/outliner \ sync
- [import] Images are currently not imported. Host them externally for this to work.
- [import] Only
.mdfiles are currently supported
StrictHostKeyCheckingis currently disabled for
push, please only run this in trusted networks.
After checking out the repo, run
bin/setup to install dependencies. You can also run
bin/console for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run
bundle exec rake install. To release a new version, update the version number in
version.rb, and then run
bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the
.gem file to rubygems.org.
Bug reports and pull requests are welcome on GitHub at https://github.com/captn3m0/outliner. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
Code of Conduct
Everyone interacting in the Outliner project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.
Licensed under the MIT License. See LICENSE file for details.