Bump version to v1.1.0 (getlago#337)

README.md

@@ -51,7 +51,7 @@ Engineers be like…
 
 Read more first-hand experiences from Qonto, Algolia, Pleo, Segment, or the 350+. Hackernews comments [here](https://news.ycombinator.com/item?id=31424450).
 
-**The Solution:** Lago, the open-source billing API for product-led SaaS 
+**The Solution:** Lago, the open-source billing API for product-led SaaS
 - Event-based: if you can track it, you can charge for it;
 - Built for product-led growth companies;
 - Hybrid pricing: subscription and usage;
@@ -105,7 +105,7 @@ docker-compose up
 
 You can now open your browser and go to http:https://localhost to connect to the application. Lago's API is exposed at http:https://localhost:3000.
 
-Note that if our docker server is not at http:https://localhost, the following env variables must be set: `LAGO_API_URL LAGO_API_URL`. This may be on the command line or in your .env file. For example:
+Note that if our docker server is not at http:https://localhost, the following env variables must be set: `LAGO_API_URL`. This may be on the command line or in your .env file. For example:
 
 ```
 LAGO_API_URL="http:https://192.168.122.71:3000"
@@ -147,18 +147,18 @@ You can follow this [guide](https://github.com/getlago/lago/wiki/Development-Env
 You can contribute by following our [guidelines](https://github.com/getlago/lago/blob/main/CONTRIBUTING.md).
 
 ## 💡 Philosophy
-B2B SaaS has evolved, but billing has not yet. 
+B2B SaaS has evolved, but billing has not yet.
 
 ### 1- We’re not in the “subscription economy” anymore. And we won’t go “full usage-based pricing” quite yet
 Pricings are now mostly hybrid: they include a usage-based component (i.e. “if you use more you pay more”) and a subscription component (i.e. a recurring fee for basic usage).
 
 Not all software companies will go full “usage-based” like Snowflake for instance. This model is the new standard for cloud infrastructure products. However, in other areas of SaaS, users want to know beforehand how much they will pay to control their spending and software companies want to be able to predict recurring revenues.
 
 ### 2- Go-to-market is not either bottom-up or top-down anymore
-SaaS used to be either self-service (SMBs) or sales-led (Enterprises). 
+SaaS used to be either self-service (SMBs) or sales-led (Enterprises).
 Go-to-market now mixes the self-service (all customers access the same price plans) and sales-led (customers get a custom quote from a sales representative) motions.
 A typical journey involves an individual contributor in a company who tests a new tool, puts their corporate credit card in, and starts spreading the use of the tool within the organization. At that point, the VP or head of department might want to upgrade to a custom plan tailored to the needs of the whole organization.
-As a result, billing needs to be flexible, automated, and transparent enough to embrace this hybrid go-to-market motion as well. 
+As a result, billing needs to be flexible, automated, and transparent enough to embrace this hybrid go-to-market motion as well.
 
 ### 3- The “rent seeker” pricing of current billing solutions needs to stop
 Why do payment companies take a cut on revenues?

docker-compose.yml

@@ -33,7 +33,7 @@ services:
 
  api:
  container_name: lago-api
- image: getlago/api:v1.0.0
+ image: getlago/api:v1.1.0
  restart: unless-stopped
  depends_on:
  - db
@@ -87,7 +87,7 @@ services:
 
  front:
  container_name: lago-front
- image: getlago/front:v1.0.0
+ image: getlago/front:v1.1.0
  restart: unless-stopped
  # Use this command if you want to use SSL with Let's Encrypt
  # command: "/bin/sh -c 'while :; do sleep 6h & wait $${!}; nginx -s reload; done & nginx -g \"daemon off;\"'"
@@ -126,7 +126,7 @@ services:
 
  api-worker:
  container_name: lago-worker
- image: getlago/api:v1.0.0
+ image: getlago/api:v1.1.0
  restart: unless-stopped
  depends_on:
  api:
@@ -170,7 +170,7 @@ services:
  # It is recommendend if you have a high usage of events to not impact the other Sidekiq Jobs.
  #api-events-worker:
  # container_name: lago-events-worker
- # image: getlago/api:v1.0.0
+ # image: getlago/api:v1.1.0
  # restart: unless-stopped
  # depends_on:
  # api:
@@ -208,7 +208,7 @@ services:
 
  api-clock:
  container_name: lago-clock
- image: getlago/api:v1.0.0
+ image: getlago/api:v1.1.0
  restart: unless-stopped
  depends_on:
  api: