v0.16.0

Changes between 0.15.0 and 0.16.0

• Set service status to "done" before running runtime stuff:
  • Runtime scripts and runtime Makejails should not change the service state, as it is preferable to avoid recreation (and therefore downtime).
• Only set service state to failed in phases other than post-start.

Full Changelog: v0.15.0...v0.16.0

v0.15.0

Changes between 0.14.2 and 0.15.0

• Added: support for appjail-apply(1):
  • Added: runtime-makejail parameter.
  • Added: runtime-arguments parameter.
  • Added: runtime-environment parameter.
• Added: scripts.[].post-start parameter.

Full Changelog: v0.14.2...v0.15.0

v0.14.2

Changes between 0.14.1 and 0.14.2

• Fixed: name cannot be numeric (unless it is the jid):
  • When the user leaves it up to Director to generate the jail name, in some exceptional cases a string consisting solely of numeric characters is generated, which can cause an error in jail(8). To avoid this, Director checks whether the generated string consists solely of numeric characters and regenerates it until there is at least one non-numeric character in the string.

Full Changelog: v0.14.1...v0.14.2

v0.14.1

Changes between 0.14.0 and 0.14.1

• Fixed: "Permission denied" error when executing Director as non-root user:
  When creating locks from a shared directory such as /tmp/director/locks, a permission denied error may occur if first one user creates that directory and another tries the same thing. The second user will see the error (except if Director is running as root, of course).

  Since the idea behind using that directory is to remove old locks on FreeBSD startup (clear_tmp_enable=YES), I think it is a good idea to use ~/.director/locks for non-root users and /tmp/director/locks for root.

Full Changelog: v0.14.0...v0.14.1

v0.14.0

Changes between 0.13.1 and 0.14.0

• Store lock files in the temporary directory:
  • The lock files are stored on a per-project basis, which is undesirable because it can cause that after an operating system crash or simply unplugging the power cable the lock files remain stale, preventing Director from running again. The current workaround is to use the temporary directory that Director assumes is removed on boot (clear_tmp_enable=YES in your rc.conf(5)).

Full Changelog: v0.13.1...v0.14.0

v0.13.1

Changes between 0.13.0 and 0.13.1

• Fixed: typo ~/.director/director.ini -> ~/.config/director/director.ini.

Full Changelog: v0.13.0...v0.13.1

v0.13.0

Changes between 0.12.0 and 0.13.0

• Add cancel command:

  • Cancels a running project started by the up command. It simply sends a SIGTERM signal to the PID of the Director instance that started the project, so that when Director handles that signal it will terminate the processes it started.

    This is useful especially when the user makes a mistake and wants to cancel the project, especially if the project has been running for a long time (like a VM). So, instead of waiting for the project to finish, the user can simply cancel its execution, fix the error and deploy again.

Full Changelog: v0.12.0...v0.13.0

v0.12.0

Changes between 0.11.0 and 0.12.0

• Improve reliability when setting project status:
  • Set project state on exit.
  • Set project state to FAILEDwhen the process is terminated in both up and down.
• Flush and sync file descriptor after writing.
• Add JSON support in up & down.

Full Changelog: v0.11.0...v0.12.0

v0.11.0

Changes between 0.10.0 and 0.11.0

• Added: support for OCI.
• Improved: reliability while setting start arguments.

Full Changelog: v0.10.0...v0.11.0

v0.10.0

Changes between 0.9.0 and 0.10.0

• Updated: Python version in README (thanks @imiguelsalcedo).
• Moved note to the correct section.
• Fixed URL to install AppJail.

Full Changelog: v0.9.0...v0.10.0