https://github.com/technologiestiftung/stadtpuls-redis

redis in memory db for stadtpuls
https://github.com/technologiestiftung/stadtpuls-redis

stadtpuls

Last synced: about 2 months ago
JSON representation

redis in memory db for stadtpuls

• Host: GitHub
• URL: https://github.com/technologiestiftung/stadtpuls-redis
• Owner: technologiestiftung
• License: mit
• Created: 2021-11-08T14:53:46.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2022-05-11T11:46:16.000Z (over 2 years ago)
• Last Synced: 2023-02-27T11:06:01.629Z (almost 2 years ago)
• Topics: stadtpuls
• Language: Dockerfile
• Homepage:
• Size: 14.6 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
![](https://img.shields.io/badge/Built%20with%20%E2%9D%A4%EF%B8%8F-at%20Technologiestiftung%20Berlin-blue)

# Stadtpuls.com redis

The [stadtpuls.com API](https://github.com/technologiestiftung/stadtpuls-api) uses Redis as in memory database for the fastify rate limiter.

## Development

In development you need to start the redis server with docker in a new shell session:

```bash

# MacOS

docker compose up

# Linux

sudo docker-compose up

# Windows

# ???

```

## Redis on Render

This is an example repo with a Dockerfile for running a Redis cache with persistence as a **private service** on Render.

Render private services are only visible to other Render services in your account. They have internal URLs (e.g. `redis:6379`), can speak any protocol (like [RESP](https://redis.io/topics/protocol)), and can listen on any port.

Backing Redis with a disk makes it resilient to data loss in the case of restarts or deploys, and Render makes this easy to do with Render Disks.

## Deployment

### One Click Deploy

Use the button below to deploy a persistent Redis instance on Render.

[![Deploy to Render](http://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy)

### Manual Deployment

1. Select **New Private Service** on your Render dashboard and use your fork of this repo to create the service.

2. Make sure the `Environment` is set to `Docker`, and enter a name for the service (this will be used to generate the private URL).

3. (optional) Add a new disk in the `Advanced` section. Give it a name and set the mount path to `/var/lib/redis`. You can also change the default size for your disk: `1 GB` should be enough for small projects.

Click `Save` and you're good to go! Once deployed, your Redis instance will be available on a URL similar to `redis:10000`, and you can start using your Redis URL from other services in your Render account. Be sure to prepend `redis://` to the URL displayed in your dashboard.

If you need help, you can always chat with us at https://render.com/chat.