A template for new projects using a Vue.js + TailwindCSS frontend and a FastAPI backend.
Find a file
2023-03-14 03:54:41 +01:00
backend feat: initial commit 2023-03-13 19:54:16 +01:00
frontend fix: replace og image with dynamic parcel path 2023-03-13 22:49:35 +01:00
public/static/images/common feat: initial commit 2023-03-13 19:54:16 +01:00
.gitignore feat: initial commit 2023-03-13 19:54:16 +01:00
.postcssrc feat: initial commit 2023-03-13 19:54:16 +01:00
Caddyfile feat: rename Docker files to production 2023-03-14 03:54:41 +01:00
package-lock.json fix(asset): fix failed parcel link resolution 2023-03-13 19:58:38 +01:00
package.json fix(asset): fix failed parcel link resolution 2023-03-13 19:58:38 +01:00
postcss.config.js feat: initial commit 2023-03-13 19:54:16 +01:00
production.backend.Dockerfile feat: rename Docker files to production 2023-03-14 03:54:41 +01:00
production.docker-compose.yml feat: rename Docker files to production 2023-03-14 03:54:41 +01:00
production.frontend.Dockerfile feat: rename Docker files to production 2023-03-14 03:54:41 +01:00
README.md feat: initial commit 2023-03-13 19:54:16 +01:00
requirements.txt feat: initial commit 2023-03-13 19:54:16 +01:00
tailwind.config.js feat: initial commit 2023-03-13 19:54:16 +01:00

TODO

In index.html: make parcel replace the hard-coded base URL (in the meta tags).

About

This is a template project for a webapp using the following tech stack:

  • Frontend:
    • Vue.js
    • TailwindCSS
    • Axios
  • Backend:
    • FastAPI (python)
  • Other:
    • Caddy (webserver/reverse proxy)
    • Parcel (bundler)

Customization

A number of default template files and assets for the frontend are already present in the repository. These include essential assets like a set of fonts, and a default favicon.

Favicon

The standards for the correct favicons are annoying, many browser vendors use a different standard.

A quick and easy way to create a set of favicons with broad compatibility is to create your favicon as an .svg-file, and then use realfavicongenerator.net to create a set of relevant files and HTML for your favicon.

Place the generated icons into /frontend/assets/images/common/ and be sure to adjust the generated HTML to point to this path.

OG Image

The OG image is served directly by Caddy, and thus needs to be placed into /public/static/images/common/, ideally as a .webp-file.

The image's dimensions should be 1200 x 630 pixels, as according to the OGP standard.