Llewellyn/exa
1
0
Fork 0
mirror of https://github.com/Llewellynvdm/exa.git synced 2024-11-11 07:10:56 +00:00
Code Issues Projects Releases Wiki Activity
2e0e29da22
exa/devtools
History
Benjamin Sago 70606f95ff Change user in Vagrantfile 
Why I have to keep doing this I have no idea. If you know, please tell!
2018-09-26 21:25:50 +01:00
..
dev-bash.sh Move the welcoming text to their own files too 2017-10-01 09:49:45 +02:00
dev-download-and-check-release.sh Add a release-checking script 2017-10-01 12:28:23 +02:00
dev-generate-checksums.sh Add script to generate checksums 2017-10-08 21:04:34 +01:00
dev-help-testvm.sh Give the testing VM commands and help text 2017-10-01 12:37:35 +02:00
dev-help.sh Change user in Vagrantfile 2018-09-26 21:25:50 +01:00
dev-package-for-linux.sh Change user in Vagrantfile 2018-09-26 21:25:50 +01:00
dev-run-debug.sh Show friendlier warnings when binaries don’t exist 2017-10-02 10:22:50 +02:00
dev-run-release.sh Show friendlier warnings when binaries don’t exist 2017-10-02 10:22:50 +02:00
dev-versions.sh Move the welcoming text to their own files too 2017-10-01 09:49:45 +02:00
local-package-for-macos.sh Copy weekly changes into macos script 2017-10-08 20:54:18 +01:00
README.md Add a dev help 2017-10-01 12:44:29 +02:00

README.md

exa development tools

These scripts deal with things like packaging release-worthy versions of exa and making sure the published versions actually work.

They are not general-purpose scripts that you’re able to run from your main computer! They’re intended to be run from the Vagrant machines — they have commands such as ‘package-exa’ or ‘check-release’ that execute them instead.