From 5b459628206df3a427020a9cb657475f199611b3 Mon Sep 17 00:00:00 2001 From: FantasyPvP <80643031+FantasyPvP@users.noreply.github.com> Date: Fri, 1 Sep 2023 02:36:02 +0100 Subject: [PATCH 1/6] Create rust.yml automation stuff ig --- .github/workflows/rust.yml | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 .github/workflows/rust.yml diff --git a/.github/workflows/rust.yml b/.github/workflows/rust.yml new file mode 100644 index 0000000..d54fa2f --- /dev/null +++ b/.github/workflows/rust.yml @@ -0,0 +1,22 @@ +name: Rust + +on: + push: + branches: [ "master" ] + pull_request: + branches: [ "master" ] + +env: + CARGO_TERM_COLOR: always + +jobs: + build: + + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v3 + - name: Build + run: cargo build --verbose + - name: Run tests + run: cargo test --verbose From 52c914d15c472c7e8830d7dc60c5d0ac2642f791 Mon Sep 17 00:00:00 2001 From: FantasyPvP <80643031+FantasyPvP@users.noreply.github.com> Date: Fri, 1 Sep 2023 02:43:54 +0100 Subject: [PATCH 2/6] Update README.md --- README.md | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 093f616..a31e36b 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,23 @@ # pack deployer -- a simple utility to automatically archive and move your resourcepacks into a folder. +- a simple command line utility to automatically archive and move your resourcepacks into a folder. ## use cases this may be useful if you regularly create resourcepacks and want to organise your projects in different folders. -the utility recursively scans directories in the project folder and organises packs into a folder \ No newline at end of file + +## features +- the utility recursively scans directories in the project folder and organises packs into a folder + +## planned features + +- reading directory locations to sync packs to from a config file (currently the config part of the code doesn't do anything useful) +- pack repository support (i'm thinking something along the lines of a basic package manager where you can install from a URL or repository) + - downloading packs + - publishing / hosting your own packs with sharable URL's (so like a basic webserver kinda thing) +- auto setup: when the app runs for the first time it will do the following + - ask you to input your resourcepacks folder location + - ask for a projects folder location + - move all of your resourcepacks to your projects folder + - create a shortcut in resourcepacks to your _resourcepacks dir in the deployment folder + - from there the app will uatomatically add new packs to your folder as you download them like a package manager From 03a35e54c6dd5288b5e0daf4fd8e668ca7f05ace Mon Sep 17 00:00:00 2001 From: FantasyPvP <80643031+FantasyPvP@users.noreply.github.com> Date: Fri, 1 Sep 2023 02:52:40 +0100 Subject: [PATCH 3/6] Update README.md --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/README.md b/README.md index a31e36b..b5b2ff4 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,23 @@ this may be useful if you regularly create resourcepacks and want to organise your projects in different folders. +## how to use + +- you'll need a projects folder named whatever you want +- compile the binary in release mode with + > cargo run --release +- place the binary in the projects folder +- any resourcepacks you're working on should be in subdirectories of this folder +- when the binary is run, any subdirectories containing a pack.mcmeta file will have their contents archived and copied to _resourcepacks in your projects dir +- any existing zip files will also be copied into _resourcepacks +- you should make your .minecraft/resourcepacks folder a shortcut/symlink to _resourcepacks in your projects dir +WARNING: before running, ensure that any packs you want to keep are moved to your projects directory, _resourcepacks will be deleted and replaced each time the binary is run +- any folder prefixed with an underscore will be ignored + +here is an example layout: +![image](https://github.com/FantasyPvP/fqntqpacks/assets/80643031/e9603295-abe3-4eeb-872b-9cf75254eca8) + + ## features - the utility recursively scans directories in the project folder and organises packs into a folder From 763f61f40fd69d510b86370e38c5af8e72787425 Mon Sep 17 00:00:00 2001 From: FantasyPvP <80643031+FantasyPvP@users.noreply.github.com> Date: Fri, 1 Sep 2023 02:52:57 +0100 Subject: [PATCH 4/6] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index b5b2ff4..39dfc24 100644 --- a/README.md +++ b/README.md @@ -20,6 +20,7 @@ WARNING: before running, ensure that any packs you want to keep are moved to you - any folder prefixed with an underscore will be ignored here is an example layout: + ![image](https://github.com/FantasyPvP/fqntqpacks/assets/80643031/e9603295-abe3-4eeb-872b-9cf75254eca8) From 0199caeb97180ebd5962c75ec6f40a561c29b43f Mon Sep 17 00:00:00 2001 From: FantasyPvP <80643031+FantasyPvP@users.noreply.github.com> Date: Fri, 1 Sep 2023 02:53:18 +0100 Subject: [PATCH 5/6] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 39dfc24..924c3a8 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ this may be useful if you regularly create resourcepacks and want to organise yo - you'll need a projects folder named whatever you want - compile the binary in release mode with - > cargo run --release + > cargo build --release - place the binary in the projects folder - any resourcepacks you're working on should be in subdirectories of this folder - when the binary is run, any subdirectories containing a pack.mcmeta file will have their contents archived and copied to _resourcepacks in your projects dir From ba3ab537617e8459a2b5b2ea88ca30de2286bbdb Mon Sep 17 00:00:00 2001 From: FantasyPvP <80643031+FantasyPvP@users.noreply.github.com> Date: Fri, 1 Sep 2023 02:54:39 +0100 Subject: [PATCH 6/6] Update README.md --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 924c3a8..8ed3163 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,11 @@ this may be useful if you regularly create resourcepacks and want to organise your projects in different folders. +## platform support + +- developed on and tested for linux +- should work on windows and mac as well as it's not using platform specific libraries + ## how to use - you'll need a projects folder named whatever you want