20b7d283b0
It allow pipes to be used in nested functions. Before, pipes were added
to a variable before variable content was evaluated/compiled by
another function. This commit ensures that the commits are evaluted in
expected order.
The issue is solved by stopping precompiling functions. It makes code
less complex. It adds to compile time of the script file but nothing
noticable and something optimizable.
The problem was that the call trees we're not executed in expected
order. E.g. let's say we have functionA that outputs something like
"Hello {{ $name| pipe }}", and we have function B calling with "name:
dear {{ $firstName}}", and at last we have a script that's calling
function B with "firstName: undergroundwires". Before, expressions were
evaluated directly, meaning that function A would become:
"Hello Dear {{ $firstName}}", as you see the pipe in function A
is lost here after being applied to function B and not reaching
$firstTime input value. Parsing expressions in the end allows for pipes
etc. to not get lost.
The commit also does necessary name refactorings and folder refactorings
to reflect logical changes. `FunctionCompiler` is renamed to
`SharedFunctionsParser` as precompiling is removed and it just simply
parses now. `/FunctionCall/` is moved to `/Function/Call`.
Finally, it improves documentation and adds more tests.
privacy.sexy
Enforce privacy & security best-practices on Windows and macOS, because privacy is sexy 🍑🍆
Get started
- Online version at https://privacy.sexy
- 💡 No need to run any compiled software on your computer.
- Alternatively download offline version for Windows, macOS or Linux.
- 💡 Single click to execute your script.
- ❗ Come back regularly to apply latest version for stronger privacy and security.
Why
- Rich tweak pool to harden security & privacy of the OS and other software on it
- Free (both free as in beer and free as in speech)
- No need to run any compiled software that has access to your system, just run the generated scripts
- Have full visibility into what the tweaks do as you enable them
- Ability to revert (undo) applied scripts
- Everything is transparent: both application and its infrastructure are open-source and automated
- Easily extendable with own powerful templating language
- Each script is independently executable without cross-dependencies
Extend scripts
- You can either create an issue
- Or send a PR:
- Fork the repository
- Add more scripts in respective script collection in collections folder.
- 📖 If you're unsure about the syntax you can refer to the collection files | documentation.
- 🙏 For any new script, please add
revertCodeanddocsvalues if possible.
- Send a pull request 👌
Commands
- Project setup:
npm install - Testing
- Run unit tests:
npm run test:unit - Run integration tests:
npm run test:integration - Lint:
npm run lint
- Run unit tests:
- Desktop app
- Development:
npm run electron:serve - Production:
npm run electron:buildto build an executable
- Development:
- Webpage
- Development:
npm run serveto compile & hot-reload for development. - Production:
npm run buildto prepare files for distribution. - Or run using Docker:
- Build:
docker build -t undergroundwires/privacy.sexy:0.10.3 . - Run:
docker run -it -p 8080:80 --rm --name privacy.sexy-0.10.3 undergroundwires/privacy.sexy:0.10.3
- Build:
- Development:
Architecture overview
Application
- Powered by TypeScript, Vue.js and Electron 💪
- and driven by Domain-driven design, Event-driven architecture, Data-driven programming concepts.
- Application uses highly decoupled models & services in different DDD layers.
- 📖 Read more on • Presentation • Application
AWS Infrastructure
- It uses infrastructure from the following repository: aws-static-site-with-cd
- Runs on AWS 100% serverless and automatically provisioned using GitHub Actions.
- Maximum security & automation and minimum AWS costs are the highest priorities of the design.
GitOps: CI/CD to AWS
- CI/CD is fully automated for this repo using different GIT events & GitHub actions.
- Versioning, tagging, creation of
CHANGELOG.mdand releasing is automated using bump-everywhere action
- Versioning, tagging, creation of
- Everything that's merged in the master goes directly to production.
