Getting Started with makeflaskreact
This app makes it easier for your to build a react flask application.
Flask does not directly work with React in development as it needs cors to handle the cross-origin error on your local react app. So, this boiler plate reduces the time spent creating a simple react and flask app.
Requirements are yarn or npm and python>=3.6.0
To install:
$ pip install makeflaskreact
To run:
$ makeflaskreact
optionally:
add --name PROJECT_NAME to change the project name from app to what you want.
add --norun or N to run the server and client on exceution of the script
Parameters
| Input | Defaults |
|---|---|
| name (--name/-A) | app |
| run (--run/-r) (--no-run/-N) | True -- will run if --no-run is not present |
| server name | server |
| python (used to create virtual env and download requirments) | python |
| host | 127.0.0.1 |
| port | 5000 |
| react client | no default will ask for either yarn (0.25+) or npm (5.2+) |
| client | client |
Final Output
Assuming standard run makeflaskreact
Metadata
Release files for makeflaskreact 1.0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| makeflaskreact-1.0.8.tar.gz | 6.3 kB | Without provenance | Details for makeflaskreact-1.0.8.tar.gz |
Release files / makeflaskreact-1.0.8.tar.gz
| Download URL | makeflaskreact-1.0.8.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a6c1bad0cfba37308fdb5706b5889ec181ae6bda35a1a33f38e3839353a15bf
|
|
BLAKE2b-256 checksum How to use checksums |
b3d131a495db8e9bc003b2a3d9ae9e947345446fd6b847d5bea16fdc8f09f73c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.0.0 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.7.7
|
Security for makeflaskreact 1.0.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.