Search Results for "django"

pongo2 is a Django-syntax like templating-language for Go. The latest version is 6.0.0. Official additional filters/tags for pongo2 (for example a markdown-filter). They are in their own repository because they’re relying on 3rd-party-libraries. Most major Go web frameworks tightly integrated with our template engine pongo2. Fortune 500 companies and popular projects are using pongo2.

Up deploys infinitely scalable serverless apps, APIs, and static websites in seconds, so you can get back to working on what makes your product unique. Up focuses on deploying “vanilla” HTTP servers so there’s nothing new to learn, just develop with your favorite existing frameworks such as Express, Koa, Django, Golang net/HTTP or others. Up currently supports Node.js, Golang, Python, Java, Crystal, and static sites out of the box. Up is platform-agnostic, supporting AWS Lambda and API Gateway as the first targets, you can think of Up as a self-hosted Heroku-style user experience for a fraction of the price, with security, flexibility, and scalability of AWS, just $ up and you’re done! ...

Lile is an application generator (think create-react-app, rails new or django start project) for gRPC services in Go and a set of tools/libraries. The primary focus of Lile is to remove the boilerplate when creating new services by creating a basic structure, test examples, Dockerfile, Makefile etc. Lile comes with a 'generator' to quickly generate new Lile services. Lile follows Go's conventions around $GOPATH and is smart enough to parse your new service's name to create the service in the right place. ...

...Rendora works totally independently of your frontend and backend stacks. Rendora can be seen as a reverse HTTP proxy server sitting between your backend server (e.g. Node.js/Express.js, Python/Django, etc...) and potentially your frontend proxy server (e.g. nginx, traefik, apache, etc...) or even directly to the outside world that does actually nothing but transporting requests and responses as they are except when it detects whitelisted requests according to the config. In that case, Rendora instructs a headless Chrome instance to request and render the corresponding page and then return the server-side rendered page back to the client (i.e. the frontend proxy server or the outside world).