Create your resume quickly and easily using your mobile phone or laptop.
With just one click, manage your professional information and have your personalized and exclusive resume in hand, which draws attention at the time of the interview.
This application contains essential resources for the User to build professional CVs, if you are a developer, you can easily build new templates with a few lines of HTML and CSS. Yes, just with HTML and CSS you have infinite construction freedom!
Try accessing the demo admin panel via the URL: https://cv-admin.tavares.in
To use this software you need to have NodeJS installed in version 16 or higher, this will allow you to create your development environment.
The administrative panel allows you to manage software assets such as: images, templates, users, expiration times and prices.
Later, you will see more information about this webapp, however it is recommended that you have a basic knowledge of Vuejs as this project was built with the Quasar Framework. Then, install the Quasar CLI tool to use and run the development environment via the command:
$ npm i -g @quasar/cli // or $ sudo npm i -g @quasar/cli
There aren’t many configurations to be done in this directory, so:
Change the api connection information in the
src/api.jsfile, this variable has the following definition:
export const api = process.env.DEV ? 'http://localhost:3333/admin' : 'https://your-domain/admin'
$ quasar devand wait for the project to run, a tab will automatically open in your default browser with the authentication screen of the administrative panel.
api/folder, all information and templates will be centralized. Enter the folder and:
Run the dependency installer:
$ npm install
Now, duplicate the environment variables file present in
api/.env.exampleand rename it
.env. Set your values according to your work environment.
- Run the dependency installer:
The environment variables present in
.env.example have the following structure:
PORT=3333 HOST=0.0.0.0 NODE_ENV=development APP_KEY=fIxfXUSGMwcOvum2JWksbylWCMRsEiHE DRIVE_DISK=s3 CACHE_VIEWS=false DB_CONNECTION=pg PG_HOST=localhost PG_PORT=5432 PG_USER=dummyKey PG_PASSWORD=dummyKey PG_DB_NAME=dummyKey S3_KEY=dummyKey S3_SECRET=dummyKey S3_BUCKET=dummyKey S3_REGION=sa-east-1 S3_ENDPOINT= SMTP_HOST=smtp.umbler.com SMTP_PORT=587 SMTP_USERNAME=<username> SMTP_PASSWORD=<password> USER_REGISTER=https://your-app-domain.com RENDER_URI=http://localhost:3334 BTCPAY_URI=https://mainnet.demo.btcpayserver.org BTCPAY_STORE=dummyKey BTCPAY_ORDER_URL=http://localhost:8084 BTCPAY_TOKEN=dummyKey
Note that there is a separation by a line to make it easier to explain the context and what each item is for, let’s start with the first block that refers to general settings:
PORT– Port that your application will run on, if you have other apps running, it is important to change this value. More information, here.
HOST– The host refers to the IP that is running, it is recommended to leave this default value. More information, here.
NODE_ENV– The way the API will be executed, if you put it in production, change this value to
production. Acceptable values are: production, development and testing. More information, here.
APP_KEY– Defines the key that will be applied to authentication tokens and cookies to avoid security breaches.
DRIVE_DISK– Defines which service will be used to save static files, for more information click here.
It is possible to save the files locally as well.
CACHE_VIEWS– Defines templates to be cached in memory at runtime and no precompiling is required.
DB_CONNECTION– Defines which database connection will be used.
Run database migrations (make sure you have created a database and that it is running) with the following command:
$ node ace migration:run
After making the proper settings, it is important that you have initial access to manage the software, for that, run the command from the
api folder and follow the steps on the screen:
$ node ace administrator
After that, you will be able to access it through the administrative application, which is in the
render/ directory has the application for this project’s template renderer, it is important to keep in mind that this software can be on a server with a separate computer (it can even run on a Raspberry Pi).
You should see a file named
.env.example, copy and paste it with a new name:
.env. Inside that file you should have the following settings:
PORT=3334 HOST=127.0.0.1 NODE_ENV=development APP_KEY=cmvv7feJnePa3T009vKtZEp_li0eWVwD DRIVE_DISK=local CACHE_VIEWS=false MASTER_SERVER=ws://localhost:3333 ADMIN_MAIL= ADMIN_PASS=
The purposes of each variable are similar to the API, however be aware of the three separate values that are part of the API connection:
MASTER_SERVERdefines in which domain the api to which the continuous connection will be made is configured.
ADMIN_PASSare your access variables to the administrative panel, without these values it will not be possible to connect or create templates.
After setting the values, run the following sequence of commands in your terminal/prompt:
Install the required dependencies by running:
$ yarn // ou $ npm install
After that, run the command:
$ node ace serve
- Wait for the connection to be established and that’s it.
Every time the application is started, it will check if there are templates pending rendering.
If there is a connection loss,
renderwill always try to reconnect. After establishing communication, it will check if there are templates pending rendering and will run a separate flow to complete pending issues.
Up to this point, you can already execute the command to import the pre-defined templates in the system, for that, access the
api/ folder and execute in your terminal/prompt:
$ node ace templates
Don’t forget to configure AWS S3® before proceeding.
The User application is in the
user/ folder, where it is possible to create resumes based on information on: experience, projects, languages, graduation, hard skills and soft skills.
The app is similar to admin, so:
Access the folder and install the dependencies in your terminal/prompt:
$ yarn // or $ npm install
The API connection configuration is in the
src/api.jsfile, when putting it into production change the line with ‘https://your-domain/user’ to your domain without removing the /user:
export const api = process.env.DEV ? 'http://localhost:3333/user' : 'https://your-domain/user'
$ quasar devand wait for the project to run, a tab will automatically open in your default browser with the lobby screen, where you can select login or registration.