GitXplorerGitXplorer
o

ansible-tiddlywiki

public
2 stars
0 forks
0 issues

Commits

List of commits on branch master.
Verified
30cba3b3141df02899b629e08e1c1bac2785401e

Merge pull request #2 from 4hel/4hel-patch-var-typo

ootakup0pe committed 4 years ago
Verified
d5b07308148cf7cf0fbfebe9e3a187d9a8c96ae9

fix typo in var name

44hel committed 4 years ago
Unverified
4b9900387cee55667b900fcfaaedf323103a1813

change path adding logic

ootakup0pe committed 4 years ago
Unverified
68b80f33667165ab5ddf3b65d294bd701426e962

better wsl quasi init script

ootakup0pe committed 6 years ago
Unverified
ee8d629a424d6d4ef929fbd93c269d83d6e8fb37

list tiddlywikis

ootakup0pe committed 6 years ago
Verified
2942c23077777c1d6e1025006ad0a9f5ebdf570d

Merge pull request #1 from otakup0pe/WIP

ootakup0pe committed 7 years ago

README

The README file for this repository.

Maintenance

Ansible / TiddlyWiki 5

One of the habits I've fallen into is using TiddlyWiki5 as a notepad. I use this role to install it on a variety of systems. At this point in time, I am actively using this role on macOS, Windows (WSL), and assorted Linux servers.

NodeJS is required. The ANXS.nodejs has treated me well.

On a Workstation

It is recommended to install this as your own user. To do this, you will need to set the tiddlywiki_install_directory, tiddlywiki_data_directory, tiddlywiki_log_directory and tiddlywiki_bin_directory.

On macs, you may also wish to tweak the tiddlywiki_ns_prefix variable. This is uesd when generating launchctl configurations.

On Linux, you will want to set the tiddlywiki_init_user to be something that is not root.

On WSL, you will want to set the tiddlywiki_pid_directory as well.

On a Server

Should work out of the box. YOLO.

Configuration

This role is entirely variable driven. A bunch of variables are shared between the instances you can define

  • tiddlywiki_install_directory dictates where to install the Git cloned TW5 repo.
  • tiddlywiki_data_directory dictates where to create the TW5 instances.
  • tiddlywiki_log_directory is where launchd will create logs.
  • tiddlywiki_owner is the user who will own these things.
  • tiddlywiki_group is the group who will own these things.
  • tiddlywiki_ns_prefix is the launchd namespace prefix.
  • tiddlywiki_bin_directory is where various helpers will be installed.
  • tiddlywiki_profile_path is where bits to be included in your profile will be installed.
  • tiddlywiki_rc allows you to control whether a profile snippet will be included
  • tiddlywiki_init_user on a linux system you can use this to install a user-specific systemd bit, as opposed to system-wide
  • tiddlywiki_init_group is used to set the ownership for init scripts. Can usually leave this default but may be helpful on non-root multi-user installs.
  • tiddlywiki_init_home is the home directory base to use when installing systemd outside of the root context
  • tiddlywiki_pid_directory is used by the WSL bits

You can then define numerous TiddlyWiki 5 instances in the tiddlywiki_instances variable. If you define none, then only TW itself will be installed.

tiddlwiki_instances:
- path: "/foo/tw"
  port: 8080
  edition: "server"
  name: "test"
...

License

MIT

Author

This Ansible role was created by Jonathan Freedman because he is a really big fan of TiddlyWiki and needs to write stuff down otherwise it is lost to the echos of time.