https://github.com/pashacoder217/ubix_pay_wallet
Lightweight and secure wallet for UBX, ETH and BEP-20 network tokens built by Vue and Quasar
https://github.com/pashacoder217/ubix_pay_wallet
ethersjs qrcode-vue quasar-framework vue3 vuedraggable
Last synced: about 1 month ago
JSON representation
Lightweight and secure wallet for UBX, ETH and BEP-20 network tokens built by Vue and Quasar
- Host: GitHub
- URL: https://github.com/pashacoder217/ubix_pay_wallet
- Owner: pashacoder217
- Created: 2025-02-25T11:19:09.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-02-25T12:25:23.000Z (over 1 year ago)
- Last Synced: 2025-03-12T23:18:00.461Z (about 1 year ago)
- Topics: ethersjs, qrcode-vue, quasar-framework, vue3, vuedraggable
- Language: JavaScript
- Homepage:
- Size: 2.76 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Quasar App (ubix)
A Quasar Framework app
## Install the dependencies
```bash
npm install
```
### Start the app in development mode (hot-code reloading, error reporting, etc.)
```bash
quasar dev
```
### Lint the files
```bash
npm run lint
```
### Format the files
```bash
npm run format
```
### Build the app for production
```bash
quasar build
```
### Customize the configuration
See [Configuring quasar.conf.js](https://quasar.dev/quasar-cli/quasar-conf-js).
The rules for working with the Ubix Pay project repository.
The repository can be found on github via the following link: https://github.com/SilentNotaryEcosystem/Ubixpay-logics/tree/development
There are two main branches in the repository.
main - it is the branch where the tested version is located.
development - it is the branch where all developers' branches merge - the product is being tested in this branch.
The creation of branches to perform tasks is done from the development branch. The naming is accomplished according to the following example:
task/{name of the task from JIRA}
For example:
task/UBIX-32
After completing the tasks, you need to upload the branch with commits to the repository. Also, It is necessary to remember to notify the colleagues about it - in the chat.
If, in the working process, there are updates to the development branch, then it is necessary to upload the changes. This will as well be announced in the chat.
The general rule is a daily morning check of changes in the development branch. This applies in case automatic notification is not provided on your IDE.