This is a template that creates an Electron application with a Flask backend and uses Vue3 and TailwindCSS (optional) for the frontend. Your backend api will be using Flask-RESTX for easier API development and automatic Swagger documentation. At the current time, this application template uses Electron.js version 15.0+ as it is the most recent version of electron that I was able to use with Vue. I will update this template with later versions when supported.
Star this template if it has been helpful :)
In the current world of serverless functions and cloud hosted servers, it is nice to have an always accessible backend server but if you want to run some code that uses quite a lot of processing power, this can be a challenge. If your application can have some processing handled by Python on the user's computer, this is a good alternative to have. Some potential use cases are listed below:
yarn install
cd src/pyflask
pip install -r requirements.txtTo compile the front end application and open it an Electron instance, use the following command:
yarn electron:serveUsing this command should compile your application and also allow hot-reloads for development. The dist_electron folder will be created at the root of your project and is your final actual electron application with an automatically generated 'package.json' and 'index.js' files. You don't have to worry about this folder too much. It should also automatically copy the pyflask folder to the dist_electron directory. If you would like to change/modify this functionality, change the path locations in the package.json file under the electron:serve-precopy script.
To run only the Vue frontend on your browser you can just use the following commands:
yarn serveThis will compile your application and also allow hot-reloads for development. If you want to test any components that don't use OS native calls this is a good alternative to have. In my opinion I would recommend using the electron compilation command because this should you the most up to date state of your application. If you want the backend to also run alongside the browser instance, just open a new terminal instance and run the following command:
python pyflask/api.pyNote: This instance will still not have access to the native node libraries since these are provided through the remote Electron mopdule.
To build the complete application, you will need to build the python executable and the Electron portion separately.
Note: You will not be able to do cross compatible builds for MacOS, Linux and Windows. The Python executable will be OS specific so you will need to build on each target OS separately. For macOS you will need an Apple Developer Certificate. You can get one of these here.
Note: I have also verified that notarization works for this application use case but your mileage may vary. Please verify this on your application and let me know how it works.
To first build the Python exectuable run:
yarn python:buildThis should create a single file named api or (api.exe on Windows) in the pyflaskdist directory. We use pyinstaller since we can't guarantee that a user will have python on their system. Using Pyinstaller allows us to have a portable python environment alongside our flask application. When you bundle the Electron application (in the next step), the python application will be automatically included in the Electron bundle.
To now build the final electron application you can use the following command:
yarn electron:buildThis will create the installer needed to share your application. The final installer will be saved in the dist_electron folder.
You can also push your build to a draft release on GitHub. You will need to have a Github token in your environment to push items to github. Create your github token here. You will need the repo permissions on your token. Follow the electron-builder instructions on setting up your token.
yarn electron:build-releaseThis template starts as a Vue application that Electron was added into using this amazing plugin created by @nklayman. I created this template to allow users who would like to use Vue as their frontend for an Electron application while using Flask for a backend. If you wanted to let a user of your application use their own computer to provide some processing power, this repo should hopefully work for you.
The original repository for Vue-Electron can be found here: @codingwithjustin/vue3-electron
The original repository for using Electron with a Python backend can be found here: @fyears/electron-python-example. This repo uses zerorpc and zeromq to pass messaged between the backend and the Electron application but the original zerorpc-node library hasn't been updated in over 3 years so using Flask and regular http calls is much more simpler and robust. Further more, using Flask as the backend allows you to use newer versions of Electron and Vue to create your application.
If you would like to use a different CSS framwork or use a library like bootstrap, you can remove the tailwind library from this project.
yarn remove tailwindcss postcss
rm tailwind.config.js
rm postcss.config.jsIn your src/index.css file remove the following lines:
@tailwind base;
@tailwind components;
@tailwind utilities;For the python portion of this application, Flask-RESTX is used to generate the API specific portion. In this example template, I have used a very small subsection of all the features it provides but you are welcome to read more about all the provided options in their documentation. To learn more about Flask-RESTX, click here.
One of the biggest reasons for using this library was the automatic generation of API documentation. If you are working in a team and have different front-end and back-end developers, this should allow you to document your application as you go through your development cycle. To view the documentation, I have set it up under the /docs endpoint. This can be accessed by either running yarn electron:serve (for the full application) or just running python pyflask/api.py (you can also use yarn python:dev for this purpose and have just one .env file). You can then visit the url at http://127.0.0.1:5000/docs and explore the Swagger documentation.
There is a large debate on what the best practices for a secure Electron application are. In this template I've implemented an example of the best way to use a preload.js file in your application to ensure that your renderer process is not exposed to a node environment. Please refer to the Electron documentation for more information on this topic.
Take a look at some of the amazing projects built with this template. Want to have your own project listed? Feel free to add your project at the bottom of the list below then submit a pull request.
Made with ❤️ by @megasanjay