- Website: leapp.cloud
- Documentation Website: docs.leapp.cloud
- Roadmap: Roadmap
- Chat with us: Slack
Leapp is a Cross-Platform Cloud access App, built on top of Electron.
The App is designed to manage and secure Cloud Access in multi-account environments.
We Strongly believe that access information to Cloud in
~/.awsor~/.azurefiles are not safe, and we prefer to store that information in an encrypted file managed by the system. Credentials will be hourly rotated and accessible in those files only when they are needed, so only when Leapp is active.
-
Switch Cloud Profile in a click
-
Secure repository for your access data
-
Multiple Cloud-Access strategies
-
No long-lived credentials
-
Generate and use sessions directly from your aws Organization
-
Connect EC2 instances straight away
All the covered access methods can be found here.
Get here the latest release.
Please read through our contributing guidelines and code of conduct. Included are directions for opening issues, coding standards, and notes on development.
Editor preferences are available in the editor config for easy use in common text editors. Read more and download plugins at editorconfig.org.
Development on Leapp can be done on Mac, Windows, or Linux as long as you have
NodeJS and Git. See the .nvmrc file located in the project for the correct Node version.
Initial Dev Setup
This repository is structured as a monorepo and contains many Node.JS packages. Each package has
its own set of commands, but the most common commands are available from the
root package.json and can be accessed using the npm run ... command. Here
are the only three commands you should need to start developing on the app.
# Install and Link Dependencies
npm install
# Start App without Live Reload
npm run electron-devIf Electron is failing building the native Library Keytar just run before npm run electron-dev:
# Clear Electron and Keytar conflicts
npm run rebuild-keytarEditor Requirements
You can use any editor you'd like, but make sure to have support/plugins for the following tools:
- ESLint – For catching syntax problems and common errors
By default, Leapp writes logs to the following locations:
- on Linux:
~/.config/Leapp/logs/log.log - on macOS:
~/Library/Logs/Leapp/log.log - on Windows:
%USERPROFILE%\\AppData\\Roaming\\Leapp\\log.logLogs are structured in the following way:
[YYYY-MM-DD HH:mm:ss.mmm] [LEVEL] [rendered/system] [COMPONENT] MESSAGE {Useful Object / Stacktrace Err Object}
Note: please always add logs whenever possible to any issue you want to fill to enable the team identify the problem quickly
Refer to the documentation website.
- Glossary: find other information about the system
- Roadmap: view our next steps and stay up to date
- Contributing: follow the guidelines if you'd like to contribute to the project
- Project Structure: check how we structured the project and where to find the files