Initial commit
Signed-off-by: Julien Riou <julien@riou.xyz>
This commit is contained in:
commit
f0cab2f7c3
54 changed files with 19984 additions and 0 deletions
2
.gitignore
vendored
Normal file
2
.gitignore
vendored
Normal file
|
@ -0,0 +1,2 @@
|
|||
public
|
||||
.hugo_build.lock
|
3
.gitmodules
vendored
Normal file
3
.gitmodules
vendored
Normal file
|
@ -0,0 +1,3 @@
|
|||
[submodule "themes/hugo-xmin"]
|
||||
path = themes/hugo-xmin
|
||||
url = https://github.com/yihui/hugo-xmin.git
|
156
LICENSE
Normal file
156
LICENSE
Normal file
|
@ -0,0 +1,156 @@
|
|||
Creative Commons Attribution 4.0 International
|
||||
|
||||
Creative Commons Corporation (“Creative Commons”) is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an “as-is” basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible.
|
||||
|
||||
Using Creative Commons Public Licenses
|
||||
|
||||
Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses.
|
||||
|
||||
Considerations for licensors: Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. More considerations for licensors.
|
||||
|
||||
Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor’s permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described. Although not required by our licenses, you are encouraged to respect those requests where reasonable. More considerations for the public.
|
||||
|
||||
Creative Commons Attribution 4.0 International Public License
|
||||
|
||||
By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions.
|
||||
|
||||
Section 1 – Definitions.
|
||||
|
||||
a. Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image.
|
||||
|
||||
b. Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License.
|
||||
|
||||
c. Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights.
|
||||
|
||||
d. Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements.
|
||||
|
||||
e. Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material.
|
||||
|
||||
f. Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License.
|
||||
|
||||
g. Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license.
|
||||
|
||||
h. Licensor means the individual(s) or entity(ies) granting rights under this Public License.
|
||||
|
||||
i. Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them.
|
||||
|
||||
j. Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world.
|
||||
|
||||
k. You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning.
|
||||
|
||||
Section 2 – Scope.
|
||||
|
||||
a. License grant.
|
||||
|
||||
1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to:
|
||||
|
||||
A. reproduce and Share the Licensed Material, in whole or in part; and
|
||||
|
||||
B. produce, reproduce, and Share Adapted Material.
|
||||
|
||||
2. Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions.
|
||||
|
||||
3. Term. The term of this Public License is specified in Section 6(a).
|
||||
|
||||
4. Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material.
|
||||
|
||||
5. Downstream recipients.
|
||||
|
||||
A. Offer from the Licensor – Licensed Material. Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License.
|
||||
|
||||
B. No downstream restrictions. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material.
|
||||
|
||||
6. No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i).
|
||||
|
||||
b. Other rights.
|
||||
|
||||
1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise.
|
||||
|
||||
2. Patent and trademark rights are not licensed under this Public License.
|
||||
|
||||
3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties.
|
||||
|
||||
Section 3 – License Conditions.
|
||||
|
||||
Your exercise of the Licensed Rights is expressly made subject to the following conditions.
|
||||
|
||||
a. Attribution.
|
||||
|
||||
1. If You Share the Licensed Material (including in modified form), You must:
|
||||
|
||||
A. retain the following if it is supplied by the Licensor with the Licensed Material:
|
||||
|
||||
i. identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated);
|
||||
|
||||
ii. a copyright notice;
|
||||
|
||||
iii. a notice that refers to this Public License;
|
||||
|
||||
iv. a notice that refers to the disclaimer of warranties;
|
||||
|
||||
v. a URI or hyperlink to the Licensed Material to the extent reasonably practicable;
|
||||
|
||||
B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and
|
||||
|
||||
C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License.
|
||||
|
||||
2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information.
|
||||
|
||||
3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable.
|
||||
|
||||
4. If You Share Adapted Material You produce, the Adapter's License You apply must not prevent recipients of the Adapted Material from complying with this Public License.
|
||||
|
||||
Section 4 – Sui Generis Database Rights.
|
||||
|
||||
Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material:
|
||||
|
||||
a. for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database;
|
||||
|
||||
b. if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material; and
|
||||
|
||||
c. You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database.
|
||||
For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights.
|
||||
|
||||
Section 5 – Disclaimer of Warranties and Limitation of Liability.
|
||||
|
||||
a. Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You.
|
||||
|
||||
b. To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.
|
||||
|
||||
c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.
|
||||
|
||||
Section 6 – Term and Termination.
|
||||
|
||||
a. This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically.
|
||||
|
||||
b. Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates:
|
||||
|
||||
1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or
|
||||
|
||||
2. upon express reinstatement by the Licensor.
|
||||
|
||||
c. For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License.
|
||||
|
||||
d. For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License.
|
||||
|
||||
e. Sections 1, 5, 6, 7, and 8 survive termination of this Public License.
|
||||
|
||||
Section 7 – Other Terms and Conditions.
|
||||
|
||||
a. The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed.
|
||||
|
||||
b. Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License.
|
||||
|
||||
Section 8 – Interpretation.
|
||||
|
||||
a. For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License.
|
||||
|
||||
b. To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions.
|
||||
|
||||
c. No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor.
|
||||
|
||||
d. Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority.
|
||||
|
||||
Creative Commons is not a party to its public licenses. Notwithstanding, Creative Commons may elect to apply one of its public licenses to material it publishes and in those instances will be considered the “Licensor.” Except for the limited purpose of indicating that material is shared under a Creative Commons public license or as otherwise permitted by the Creative Commons policies published at creativecommons.org/policies, Creative Commons does not authorize the use of the trademark “Creative Commons” or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For the avoidance of doubt, this paragraph does not form part of the public licenses.
|
||||
|
||||
Creative Commons may be contacted at creativecommons.org.
|
5
README.md
Normal file
5
README.md
Normal file
|
@ -0,0 +1,5 @@
|
|||
# julien.riou.xyz
|
||||
|
||||
Source code behind [julien.riou.xyz](https://julien.riou.xyz) website. Made
|
||||
with [Hugo](https://gohugo.io/) and [xmin](https://github.com/yihui/hugo-xmin)
|
||||
theme.
|
5
archetypes/default.md
Normal file
5
archetypes/default.md
Normal file
|
@ -0,0 +1,5 @@
|
|||
+++
|
||||
title = '{{ replace .File.ContentBaseName "-" " " | title }}'
|
||||
date = {{ .Date }}
|
||||
draft = true
|
||||
+++
|
9
content/_index.markdown
Normal file
9
content/_index.markdown
Normal file
|
@ -0,0 +1,9 @@
|
|||
---
|
||||
title: Home
|
||||
---
|
||||
|
||||
<div class="center">
|
||||
<img src="/imgs/profile.jpg" class="rounded" alt="Profile pic" />
|
||||
|
||||
[Mastodon](https://hachyderm.io/@jriou) | [Code](https://git.riou.xyz/jriou) | [LinkedIn](https://www.linkedin.com/in/jriou) | [E-mail](mailto:julien@riou.xyz) | [PGP](https://keys.openpgp.org/vks/v1/by-fingerprint/458D536DEE2B11404BC4BF6E9A099EDA51316854)
|
||||
</div>
|
304
content/blog/postgis-and-the-hard-rock-cafe-collection.md
Normal file
304
content/blog/postgis-and-the-hard-rock-cafe-collection.md
Normal file
|
@ -0,0 +1,304 @@
|
|||
---
|
||||
title: PostGIS and the Hard Rock Cafe collection
|
||||
date: 2024-05-27T18:00:00+02:00
|
||||
categories:
|
||||
- postgresql
|
||||
---
|
||||
|
||||
In 2007, I went to the west coast of the United States where I visited a Hard
|
||||
Rock Cafe store in Hollywood CA and bought the first T-Shirt of my collection.
|
||||
Now, I'm an open-source DBA and my number one database is
|
||||
[PostgreSQL](https://www.postgresql.org/). So I've decided to use the
|
||||
[PostGIS](https://postgis.net/) extension to plan my next vacations or
|
||||
conferences to buy more T-Shirts.
|
||||
|
||||
# The collection
|
||||
|
||||
## Inventory
|
||||
|
||||
Let's do the inventory of my collected T-Shirts by looking at my closet.
|
||||
|
||||

|
||||
|
||||
The titles represent a location, generally a city but it could be a known place
|
||||
like a stadium. This will be enough to find the related shop in a database.
|
||||
Titles can be written into a file:
|
||||
|
||||
```
|
||||
Dublin
|
||||
Los Angeles
|
||||
Prague
|
||||
London
|
||||
```
|
||||
|
||||
([collection.csv](/hrc/collection.csv))
|
||||
|
||||
## Coordinates
|
||||
|
||||
The next step is to add coordinates. This information can be found by querying
|
||||
the [Nominatim](https://nominatim.org/) API based on the
|
||||
[OpenStreetMap](https://www.openstreetmap.org) community-driven project.
|
||||
|
||||
```python
|
||||
#!/usr/bin/env python3
|
||||
import requests
|
||||
import csv
|
||||
import time
|
||||
|
||||
|
||||
if __name__ == "__main__":
|
||||
headers = {"User-Agent": "Hard Rock Cafe Blog Post From Julien Riou"}
|
||||
session = requests.Session()
|
||||
session.headers.update(headers)
|
||||
|
||||
with open("collection_with_coordinates.csv", "w") as dest:
|
||||
writer = csv.writer(dest)
|
||||
with open("collection.csv", "r") as source:
|
||||
for row in csv.reader(source):
|
||||
name = row[0]
|
||||
r = session.get(f"https://nominatim.openstreetmap.org/search?q={name}&limit=1&format=json")
|
||||
time.sleep(1)
|
||||
r.raise_for_status()
|
||||
data = r.json()
|
||||
if len(data) == 1:
|
||||
data = data[0]
|
||||
writer.writerow([name, data["lon"], data["lat"]])
|
||||
else:
|
||||
print(f"Location not found for {title}, skipping")
|
||||
```
|
||||
|
||||
([collection.py](/hrc/collection.py))
|
||||
|
||||
The Python script iterates over the `collection.csv` file to query the
|
||||
Nominatim API to find the most relevent OpenStreetMap node then writes
|
||||
coordinates in the `collection_with_coordinates.csv` file using the
|
||||
coma-separated values (CSV) format.
|
||||
|
||||
```
|
||||
Dublin,53.3493795,-6.2605593
|
||||
Los Angeles,34.0536909,-118.242766
|
||||
Prague,50.0596288,14.446459273258009
|
||||
London,51.4893335,-0.14405508452768728
|
||||
```
|
||||
|
||||
([collection_with_coordinates.csv](/hrc/collection_with_coordinates.csv))
|
||||
|
||||
# The shops (or "nodes")
|
||||
|
||||
Now we need a complete list of Hard Rock Cafe locations with their coordinates
|
||||
to match the collection.
|
||||
|
||||
## OpenStreetMap
|
||||
|
||||
My first idea was to use OpenStreetMap that should provide the needed dataset.
|
||||
I tried to use the Nominatim API but the queries are [limited to 40
|
||||
results](https://nominatim.org/release-docs/latest/api/Search/#parameters). I
|
||||
could [download the entire
|
||||
dataset](https://wiki.openstreetmap.org/wiki/Downloading_data), import it in a
|
||||
[PostgreSQL instance](https://osm2pgsql.org/) locally but it would have been
|
||||
space and time consuming. So, I used the [Overpass
|
||||
API](https://wiki.openstreetmap.org/wiki/Overpass_API) with [this
|
||||
query](https://overpass-turbo.eu/s/1LwQ) (thanks
|
||||
[Andreas](https://andreas.scherbaum.la/)). In the end, the quality of the data
|
||||
was not satisfying. The amenity was restaurant, bar, pub, cafe, nightclub or
|
||||
shop. The name had an accent ("é") or not ("e"). Sometimes, the brand was not
|
||||
reported. Even with all those filters, there was a
|
||||
[node](https://www.openstreetmap.org/node/6260098710) that was not even a Hard
|
||||
Rock Cafe. The more the query grew, the more I wanted to use another method.
|
||||
|
||||
## Website
|
||||
|
||||
I decided to parse the official website. By using a well-known library like
|
||||
[Selenium](https://selenium-python.readthedocs.io/) or
|
||||
[ferret](https://www.montferret.dev/)? Given the personal time I had for this
|
||||
project, I've chosen the quick and dirty path. Let me present you the ugly but
|
||||
functional one-liner to parse the official Hard Rock Cafe website:
|
||||
|
||||
```
|
||||
curl -sL https://cafe.hardrock.com/locations.aspx | \
|
||||
grep 'var currentMapPoint=' | \
|
||||
sed "s/.*{'title':/{'title':/g;s/,'description.*/}/g;s/'/\"/g" | \
|
||||
sed 's/{"title"://g;s/"lat":/"/g;s/,"lng":/","/g;s/}/"/g' \
|
||||
> nodes.csv
|
||||
```
|
||||
|
||||
Very ugly, not future-proof, but it did the job.
|
||||
|
||||
```
|
||||
"Hard Rock Cafe Amsterdam","52.36211","4.88298"
|
||||
"Hard Rock Cafe Andorra","42.507707","1.531977"
|
||||
"Hard Rock Cafe Angkor","13.35314","103.85676"
|
||||
"Hard Rock Cafe Asuncion","-25.2896910","-57.5737599"
|
||||
```
|
||||
|
||||
([nodes.csv](/hrc/nodes.csv))
|
||||
|
||||
# Data exploration
|
||||
|
||||
The tool of choice to import and analyze this data is PostgreSQL and its
|
||||
PostGIS extension. I've used [Docker](https://www.docker.com/) to have a
|
||||
disposable local instance to perform quick analysis.
|
||||
|
||||
```
|
||||
docker run -d --name postgres -v "$(pwd):/mnt:ro" \
|
||||
-e POSTGRES_USER=hrc -e POSTGRES_PASSWORD=insecurepassword \
|
||||
-e POSTGRES_DB=hrc \
|
||||
postgis/postgis:16-3.4
|
||||
docker exec -ti postgres psql -U hrc -W
|
||||
```
|
||||
|
||||
The instance is now started and we are connected.
|
||||
|
||||
## Import
|
||||
|
||||
The [COPY](https://www.postgresql.org/docs/current/sql-copy.html) command on
|
||||
PostgreSQL can import CSV lines easily. We'll use the psql alias (`\copy`) to
|
||||
send data directly through the client.
|
||||
|
||||
```
|
||||
create table collection (
|
||||
name text primary key,
|
||||
lat numeric,
|
||||
lon numeric
|
||||
);
|
||||
\copy collection (name, lat, lon) from '/mnt/collection_with_coordinates.csv' csv;
|
||||
|
||||
create table nodes (
|
||||
name text primary key,
|
||||
lat numeric,
|
||||
lon numeric
|
||||
);
|
||||
\copy nodes (name, lat, lon) from '/mnt/nodes.csv' delimiter ',' csv;
|
||||
```
|
||||
|
||||
## Correlation
|
||||
|
||||
The SQL query takes all the rows from the `collection` table and try to
|
||||
find a row in the `nodes` table within 50 km based on coordinates.
|
||||
|
||||
```
|
||||
select c.name as tshirt, n.name as restaurant,
|
||||
round((ST_Distance(ST_Point(c.lon, c.lat), ST_Point(n.lon, n.lat), true)/1000)::numeric, 2)
|
||||
as distance_km
|
||||
from collection c
|
||||
left join nodes n
|
||||
on ST_DWithin(ST_Point(c.lon, c.lat), ST_Point(n.lon, n.lat), 50000, true)
|
||||
order by c.name, distance_km;
|
||||
```
|
||||
|
||||
The PostGIS functions used are:
|
||||
|
||||
* [ST_Point](https://postgis.net/docs/ST_Point.html) to create a point in space with coordinates
|
||||
* [ST_Distance](https://postgis.net/docs/ST_Distance.html) to compute the distance between two points
|
||||
* [ST_DWithin](https://postgis.net/docs/ST_DWithin.html) to filter only rows with a distance less or equal than the provided value
|
||||
|
||||
Result:
|
||||
|
||||
```
|
||||
tshirt | restaurant | distance_km
|
||||
------------------+--------------------------------------------+-------------
|
||||
Amsterdam | Hard Rock Cafe Amsterdam | 1.38
|
||||
Angkor | Hard Rock Cafe Phnom Penh | 0.75
|
||||
Antwerp | Hard Rock Cafe Brussels | 41.84
|
||||
Barcelona | Hard Rock Cafe Barcelona | 0.64
|
||||
Berlin | Hard Rock Cafe Berlin | 4.32
|
||||
Boston | (null) | (null)
|
||||
Brussels | Hard Rock Cafe Brussels | 0.10
|
||||
Detroit | (null) | (null)
|
||||
Dublin | Hard Rock Cafe Dublin | 0.40
|
||||
Hamburg | Hard Rock Cafe Hamburg | 2.36
|
||||
Ho Chi Minh City | (null) | (null)
|
||||
Hollywood | Hard Rock Cafe Hollywood on Hollywood Blvd | 1.07
|
||||
Lisbon | Hard Rock Cafe Lisbon | 1.07
|
||||
London | Hard Rock Cafe London | 1.66
|
||||
London | Hard Rock Cafe London Piccadilly Circus | 2.40
|
||||
Los Angeles | Hard Rock Cafe Hollywood on Hollywood Blvd | 10.46
|
||||
Miami | Hard Rock Cafe Miami | 0.97
|
||||
Miami | Hard Rock Cafe Hollywood FL | 30.83
|
||||
Miami Gardens | Hard Rock Cafe Hollywood FL | 12.62
|
||||
Miami Gardens | Hard Rock Cafe Miami | 19.26
|
||||
New York | Hard Rock Cafe New York Times Square | 5.18
|
||||
New York | Hard Rock Cafe Yankee Stadium | 14.53
|
||||
Orlando | Hard Rock Cafe Orlando | 11.50
|
||||
Oslo | (null) | (null)
|
||||
Paris | Hard Rock Cafe Paris | 2.14
|
||||
Prague | Hard Rock Cafe Prague | 3.59
|
||||
San Francisco | Hard Rock Cafe San Francisco | 3.36
|
||||
Singapore | Hard Rock Cafe Singapore | 5.74
|
||||
Singapore | Hard Rock Cafe Changi Airport Singapore | 18.88
|
||||
Singapore | Hard Rock Cafe Puteri Harbour | 19.33
|
||||
Yankee Stadium | Hard Rock Cafe Yankee Stadium | 0.14
|
||||
Yankee Stadium | Hard Rock Cafe New York Times Square | 9.53
|
||||
```
|
||||
|
||||
We can identify multiple patterns here:
|
||||
|
||||
* exact match
|
||||
* closed restaurants (Boston, Detroit, Ho Chi Minh City, Oslo)
|
||||
* multiple restaurants (Miami, Miami Gardens, Singapore, New York, Yankee Stadium)
|
||||
* multiple T-Shirts (Miami, Los Angeles)
|
||||
* wrong match (Angkor, Antwerp)
|
||||
* missed opportunities (Hollywood FL, Piccadilly Circus)
|
||||
|
||||
I've created a [script](/hrc/update.sql) to update the names in the
|
||||
`collection` table to match the names in the `nodes` tables to join them by names
|
||||
instead of the location.
|
||||
|
||||
# Next locations
|
||||
|
||||
The last step of the exploration is to find Hard Rock Cafe locations within a
|
||||
reasonable distance from home (1000 Km). As I don't want to disclose the exact
|
||||
position, we'll search for "Belgium". The country is quite small so that should
|
||||
not be an issue.
|
||||
|
||||
```
|
||||
$ curl -A "Hard Rock Cafe Blog Post From Julien Riou" \
|
||||
-sL "https://nominatim.openstreetmap.org/search?limit=1&format=json&q=Belgium" | \
|
||||
jq -r '.[0].name,.[0].lon,.[0].lat'
|
||||
België / Belgique / Belgien
|
||||
4.6667145
|
||||
50.6402809
|
||||
```
|
||||
|
||||
The query to search for shops that I don't have already visited looks like
|
||||
this:
|
||||
|
||||
```
|
||||
select n.name,
|
||||
round((ST_Distance(ST_Point(n.lon, n.lat), ST_Point(4.6667145, 50.6402809), true)/1000)::numeric, 2)
|
||||
as distance_km
|
||||
from nodes n
|
||||
left join collection c
|
||||
on n.name = c.name
|
||||
where c.name is null
|
||||
and ST_Distance(ST_Point(n.lon, n.lat), ST_Point(4.6667145, 50.6402809), true)/1000 < 1000
|
||||
order by distance_km;
|
||||
```
|
||||
|
||||
The final result:
|
||||
|
||||
```
|
||||
name | distance_km
|
||||
-----------------------------------------+-------------
|
||||
Hard Rock Cafe Cologne | 164.87
|
||||
Hard Rock Cafe London Piccadilly Circus | 349.99
|
||||
Hard Rock Cafe Manchester | 569.37
|
||||
Hard Rock Cafe Munich | 573.42
|
||||
Hard Rock Cafe Innsbruck | 618.90
|
||||
Hard Rock Cafe Newcastle | 640.64
|
||||
Hard Rock Cafe Milan | 666.41
|
||||
Hard Rock Cafe Copenhagen | 769.51
|
||||
Hard Rock Cafe Edinburgh | 789.31
|
||||
Hard Rock Cafe Venice | 812.96
|
||||
Hard Rock Cafe Wroclaw | 870.89
|
||||
Hard Rock Cafe Vienna | 890.23
|
||||
Hard Rock Cafe Florence | 911.37
|
||||
Hard Rock Cafe Gothenburg | 918.32
|
||||
Hard Rock Cafe Andorra | 935.20
|
||||
```
|
||||
|
||||
# Conclusion
|
||||
|
||||
According to this study, my next vacations or conferences should take place in
|
||||
Germany or UK. A perfect opportunity to go to
|
||||
[PGConf.DE](https://2024.pgconf.de/) and [PGDay UK](https://pgday.uk/)!
|
129
content/blog/so-ive-self-hosted-my-code-using-forgejo.md
Normal file
129
content/blog/so-ive-self-hosted-my-code-using-forgejo.md
Normal file
|
@ -0,0 +1,129 @@
|
|||
+++
|
||||
title = "So I've self-hosted my code using Forgejo"
|
||||
date = 2024-12-21T12:00:00+01:00
|
||||
+++
|
||||
|
||||
The open source philosophy is often reduced to the the source code of a
|
||||
software that is available somewhere published under a permissive license. That
|
||||
somewhere is mostly [GitHub](https://github.com/), using
|
||||
[Git](https://git-scm.com/) as a source code management tool. GitHub provides a
|
||||
centralized place for everyone to contribute to open source projects. While
|
||||
this is a good boost for them, having this giant place using your code to train
|
||||
AI models or even providing [AI product that we don't need for free if you are
|
||||
an open source
|
||||
maintainer](https://www.msn.com/en-us/technology/tech-companies/github-is-making-its-ai-programming-copilot-free-for-vs-code-developers/ar-AA1w9UrA),
|
||||
is not aligned with my values.
|
||||
|
||||
The second problem I have with GitHub is that when I was a student at the
|
||||
university, I created an [account](https://github.com/riouj) using my former
|
||||
handle (riouj), my student e-mail and my french phone number. Years later, I
|
||||
tried to recover this account but having lost access to both recovery methods,
|
||||
GitHub support said "Nope", even if I can prove my identity and provide my
|
||||
diploma. My professional handle (jriou) is used by [someone
|
||||
else](https://github.com/jriou). So I've created an
|
||||
[account](https://github.com/jouir) using a handle that I used on some forums
|
||||
(jouir) which is not very professional if you speak french. Moving somewhere
|
||||
else will allow me to use my regular nickname, finally!
|
||||
|
||||
Alright, now where should I move my code?
|
||||
|
||||
There are multiple services online to store your code like
|
||||
[bitbucket.org](https://bitbucket.org/). We use Atlassian products at work so
|
||||
why not giving their online service a try on their free tier? There's also
|
||||
[gitlab.com](https://about.gitlab.com/) which is famous to be one of the
|
||||
biggest alternative to GitHub. That would also mean my code will be hosted by
|
||||
another US corporation. Then I heard about [Gitea](https://about.gitea.com/)
|
||||
that was taken over by a for-profit company and the
|
||||
[Forgejo](https://forgejo.org/) fork backed by
|
||||
[Codeberg](https://codeberg.org/), a non-profit organization based in Germany,
|
||||
in the EU. I could push my code to a service managed by an association sharing
|
||||
my values...
|
||||
|
||||
Or, I could deploy the free and open source software (FOSS) directly on one of
|
||||
my homelab servers! Exposing the source code of my personal projects should not
|
||||
use that much of resources, especially bandwidth, and should not be sensitive
|
||||
to latency, right? Let's find out.
|
||||
|
||||
# The setup
|
||||
|
||||
My hosts rely on a home-made backup solution based on ZFS replicated to three
|
||||
locations. Everything is explained in my [Journey of a Home-based Personal
|
||||
Cloud Storage Project](https://julien.riou.xyz/socallinuxexpo2024.handout.html)
|
||||
talk and [self-hosting](https://self-hosting.riou.xyz/) blog. I've taken the
|
||||
server with the most bandwidth to host the Forgejo instance. As I use Ansible
|
||||
to manage my personal infrastructure, I've created an [Ansible
|
||||
role](https://git.riou.xyz/jriou/ansible-role-forgejo) to manage Forgejo using
|
||||
docker compose. The [official
|
||||
documentation](https://forgejo.org/docs/next/admin/installation-docker/) is
|
||||
simple and easy. In a matter of minutes, my instance was up and running!
|
||||
|
||||
In order to expose the instance to the public and share my software
|
||||
contributions to the world, I have some components that are not self-hosted: a
|
||||
domain name and a virtual private server (VPS) to route the traffic to my home
|
||||
network hosting OpenVPN and Nginx. I should try
|
||||
[tailscale](https://tailscale.com/) one day but that's another topic.
|
||||
|
||||

|
||||
|
||||
The HTTPS exposition is pretty easy with Nginx. There are plenty of
|
||||
documentations everywhere for that purpose. For SSH, which is TCP, I've used
|
||||
nginx streams:
|
||||
|
||||
```
|
||||
load_module /usr/lib/nginx/modules/ngx_stream_module.so;
|
||||
|
||||
stream {
|
||||
server {
|
||||
listen 222;
|
||||
proxy_pass IP.OF.VPN.INSTANCE:222;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
I tried to use iptables for forwarding the SSH port to the private instance but
|
||||
failed miserably. The Nginx stream solution is much easier! Don't forget to
|
||||
allow the incoming port on the VPS. After years of experience, I fell into this
|
||||
trap and spent at least one hour debugging why this damn Nginx stream
|
||||
configuration was not working.
|
||||
|
||||
And the website is live, ready to receive my code!
|
||||
|
||||
# Code migration
|
||||
|
||||
My code is not very popular. I mostly have archived repositories. My maintained
|
||||
repositories have little to no issues. I don't use GitHub actions (yet). And I
|
||||
have less than 20 repositories. So the migration was pretty simple:
|
||||
|
||||
1. Create repository on Forgejo including the description
|
||||
1. Disable what I don't use (wiki, releases, projects, actions, etc)
|
||||
1. Add "forgejo" remote on git
|
||||
1. Push everything including tags to the "forgejo" remote
|
||||
1. Rename "forgejo" git remote by origin
|
||||
1. Delete repository from GitHub
|
||||
|
||||
As far as I know, there's no way to force ordering of your repositories on
|
||||
Forgejo like you could have on GitHub with pinned repositories. So if you would
|
||||
like to order your repositories when your visitors will land onto your profile
|
||||
page, you should create them from the oldest to the newest which is the default
|
||||
ordering on Forgejo. I don't care about the order personally so I took them in
|
||||
a "first seen, first migrated" fashion. The git history is respected though.
|
||||
|
||||
# What's next
|
||||
|
||||
The basic setup is done but there's still work to do like setting up local
|
||||
actions to ensure code quality.
|
||||
|
||||
# Conclusion
|
||||
|
||||
Now I have all my repositories, on my own infrastructure, [publicly
|
||||
available](https://git.riou.xyz/jriou), running entirely on FOSS, and this is
|
||||
beautiful.
|
||||
|
||||

|
||||
|
||||
I would like to thank the Forgejo contributors and the Codeberg organization
|
||||
for their amazing work to provide an open source self-hosted alternative to
|
||||
GitHub. The best way to really thank them is to [donate
|
||||
regularly](https://donate.codeberg.org/) (which I'm proud to do).
|
||||
|
||||
|
441
content/blog/yubikey-for-personal-use.md
Normal file
441
content/blog/yubikey-for-personal-use.md
Normal file
|
@ -0,0 +1,441 @@
|
|||
---
|
||||
title: Yubikey for personal use
|
||||
date: 2024-08-07T07:45:00+02:00
|
||||
categories:
|
||||
- yubikey
|
||||
---
|
||||
|
||||
At work, we use SSH to connect to our infrastructure using
|
||||
[PIV](https://developers.yubico.com/PIV/Guides/SSH_with_PIV_and_PKCS11.html)
|
||||
and a [Yubikey](https://www.yubico.com/) to comply with the PCI DSS standard.
|
||||
I've seen a post from [Christian
|
||||
Stankowic](https://chaos.social/@stdevel/112490125694988342) (aka "stdevel") on
|
||||
Mastodon showing a Yubikey for personal use, so I decided to give it a try.
|
||||
This blog post is the result of how I use a Yubikey outside of work.
|
||||
|
||||

|
||||
|
||||
Parts:
|
||||
- [YubiKey 5 NFC (USB-A)](https://www.yubico.com/be/product/yubikey-5-nfc/)
|
||||
- [Lanyard](https://www.yubico.com/be/product/yubico-keyport-parapull-lanyard/)
|
||||
- [Double Rainbow Cover](https://www.yubico.com/be/product/yubistyle-covers-usb-a-c-nfc/)
|
||||
|
||||
|
||||
I'm not paid to promote these products.
|
||||
|
||||
# Disclaimer
|
||||
|
||||
Modifying security keys may be dangerous. I cannot be responsible of any data
|
||||
loss that may have been caused. Use the commands with caution.
|
||||
|
||||
# Requirements
|
||||
|
||||
I'm running on Ubuntu 24.04 (Noble Numbat) at the time of writing. The easiest
|
||||
way to install Yubikey Manager to set up the Yubikey is to use the PPA.
|
||||
|
||||
```
|
||||
sudo add-apt-repository ppa:yubico/stable
|
||||
sudo apt-get update
|
||||
sudo apt-get install yubikey-manager
|
||||
ykman --version
|
||||
```
|
||||
|
||||
If you have another system, please [follow the official
|
||||
documentation](https://docs.yubico.com/software/yubikey/tools/ykman/).
|
||||
|
||||
# SSH with FIDO2
|
||||
|
||||
At home, I self-host multiple services from a [distributed file
|
||||
storage](/socallinuxexpo2024.handout.html),
|
||||
[finances](https://www.firefly-iii.org/) to my home lab. They run on various
|
||||
hosts accessible via SSH. But instead of relying on PIV, like at work, I wanted
|
||||
to try something more secure and supposed to be easy to use:
|
||||
[FIDO2](https://developers.yubico.com/SSH/Securing_SSH_with_FIDO2.html).
|
||||
|
||||
The components:
|
||||
|
||||

|
||||
|
||||
In short, it's a regular public and private key system, using [eliptic-curve
|
||||
cryptography](https://en.wikipedia.org/wiki/Elliptic-curve_cryptography)
|
||||
("ECC"), but instead of storing the private key on on your client, an _access_
|
||||
key (with "sk" suffix for "Security Key") is used to access the private key on
|
||||
the Yubikey.
|
||||
|
||||
Like regular SSH keys, a **password** can protect the private key itself.
|
||||
|
||||
With FIDO2 on the Yubikey, there are two more security mechanisms to be aware
|
||||
of:
|
||||
- **PIN**: alphanumeric password, special chars allowed, that must be **at
|
||||
least** 4 chars long
|
||||
- **Touch**: security that requires you to touch the "Y" area of the Yubikey
|
||||
with your finger to validate your physical presence
|
||||
|
||||
Note that the minimum version of OpenSSH with FIDO2 support is 8.2, which means
|
||||
at least Debian 11. If you have older versions around, it's time to upgrade!
|
||||
|
||||
## PIN
|
||||
|
||||
By default, the FIDO PIN is not defined. You should generate a strong PIN from
|
||||
a password manager like [KeepPassXC](https://keepassxc.org/).
|
||||
|
||||
```
|
||||
read -s PIN
|
||||
echo -ne $PIN | wc -c
|
||||
ykman fido access change-pin --new-pin "${PIN}"
|
||||
```
|
||||
|
||||
## SSH keys
|
||||
|
||||
The next step is to create a pair of SSH keys. This operation has to be
|
||||
repeated for each client. The Yubikey is able to store multiple private keys.
|
||||
One private key should not be re-used by multiple clients because that would
|
||||
mean the _access_ key, which must stay private, on the client
|
||||
(`~/.ssh/id_ed25519_sk`) used to unlock the private key on the Yubikey, has to
|
||||
be moved around, which is a bad practice.
|
||||
|
||||
I've chosen the [Ed25519](https://en.wikipedia.org/wiki/EdDSA) algorithm
|
||||
instead of
|
||||
[ECSDA](https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm)
|
||||
because interoperability is not an issue for me, all my systems are up-to-date
|
||||
and compatible. Both are strong options. Both are not
|
||||
[RSA](https://en.wikipedia.org/wiki/RSA_(cryptosystem)).
|
||||
|
||||
```
|
||||
ssh-keygen -t ed25519-sk -O resident -O verify-required \
|
||||
-O "application=ssh:$(hostname -f)" \
|
||||
-C "$(hostname -f)"
|
||||
```
|
||||
|
||||
Enter the **PIN**, **touch** the Yubikey then set a **password** to protect the
|
||||
SSH key.
|
||||
|
||||
Finally copy the public key to the remote hosts (file
|
||||
`~/.ssh/id_ed25519_sk.pub`).
|
||||
|
||||
## SSH agent
|
||||
|
||||
The main problem is that we need to pass 3 security tests for every single SSH
|
||||
connection:
|
||||
|
||||
1. Enter the password of the SSH key
|
||||
1. Enter the FIDO2 PIN of the Yubikey
|
||||
1. Touch the Yubikey
|
||||
|
||||
I know this is security but it's not very user-friendly. So I've tried to use
|
||||
an SSH agent to "cache" the private key for a limited amount of time, like I do
|
||||
for regular keys and even with PIV.
|
||||
|
||||
Let's try to add the identities to the agent:
|
||||
|
||||
```
|
||||
$ ssh-add -K
|
||||
Enter PIN for authenticator:
|
||||
Resident identity added: ED25519-SK SHA256:***
|
||||
$ ssh-add -l
|
||||
256 SHA256:*** (ED25519-SK)
|
||||
```
|
||||
|
||||
Then connect:
|
||||
|
||||
```
|
||||
$ pilote
|
||||
sign_and_send_pubkey: signing failed for ED25519-SK "/home/jriou/.ssh/id_ed25519_sk" from agent: agent refused operation
|
||||
```
|
||||
|
||||
Unfortunately, the SSH agent doesn't seem to load the FIDO keys properly. To
|
||||
fix this issue, you can disable the agent in file `~/.ssh/config`:
|
||||
|
||||
```
|
||||
Host *
|
||||
IdentityAgent none
|
||||
```
|
||||
|
||||
You still need to pass the 3 security checks but, at least, you can connect.
|
||||
|
||||
I use [Ansible](https://github.com/ansible/ansible) to manage most of my
|
||||
personal infrastructure. With FIDO2, you can multiply the number of security
|
||||
checks by the number of managed host. This is a nightmare. Unfortunately, I've
|
||||
chosen to create a regular ed25519 key pair and use it only for Ansible from
|
||||
one host that will never leave my secure house.
|
||||
|
||||
# FIDO U2F to replace OTPs
|
||||
|
||||
This [open authentication
|
||||
standard](https://www.yubico.com/authentication-standards/fido-u2f-standard/)
|
||||
enables you add an additional security check based on a hardware key, to log on
|
||||
a website for example. Traditionally, you have to enter your user name and your
|
||||
password. You can add [two-factor
|
||||
authentication](https://en.wikipedia.org/wiki/Multi-factor_authentication) with
|
||||
an application generating one-time passwords ("OTP"). They are generated for a
|
||||
limited amount of time. I have way too many OTPs registered in my
|
||||
[FreeOTP](https://freeotp.github.io/) application. FIDO U2F is a way to replace
|
||||
your OTP by touching your Yubikey. As simple as that.
|
||||
|
||||
It's supported by plenty of platforms including (but not limited) Mastodon,
|
||||
Github and Linkedin. The workflow to setup a hardware key goes often like this:
|
||||
|
||||
1. Go to Settings / Security or Account
|
||||
1. Look for 2FA or MFA
|
||||
1. Setup OTP (even if you won't use it)
|
||||
1. Search for hardware key
|
||||
1. Enter the FIDO PIN
|
||||
1. Touch the Yubikey
|
||||
|
||||
The interface will be different for each platform but the workflow should be
|
||||
the same.
|
||||
|
||||
# PGP
|
||||
|
||||
Nowadays, communication systems provide transparent [end-to-end
|
||||
encryption](https://en.wikipedia.org/wiki/End-to-end_encryption). But it's not
|
||||
always enabled by default (I see you [Telegram](https://telegram.org/)). Do you
|
||||
trust those providers claiming they are not able to decrypt your messages?
|
||||
Where are my keys? Can I bring my own? _It's encrypted, trust me bro_.
|
||||
|
||||
Technically, Pretty Good Privacy ("PGP") solves this issue. I can generate my
|
||||
own set of keys to encrypt or authenticate data using public key cryptography.
|
||||
[ECC](https://www.rfc-editor.org/rfc/rfc6637) is supported. The **private key**
|
||||
can be protected by the **Yubikey**.
|
||||
|
||||
The only problem is to find people like me, believing in privacy, able to use
|
||||
PGP to encrypt communications. In our daily lives, we talk mostly to
|
||||
non-technical people that don't know a word about how cryptography works or
|
||||
even how computers work. E-mails are less and less used. Which means I don't
|
||||
use PGP to encrypt my messages very often, except at work.
|
||||
|
||||
Another usage of PGP is to encrypt **sensible files**. In that case, storing
|
||||
the private key on a Yubikey is a good way to make it more secure. But at the
|
||||
same time, if you loose the key, you will never be able to decrypt the original
|
||||
files. You can still export the private key and store it somewhere secure. But
|
||||
how secure is it? Here it comes the endless loop of paranoia to encrypt the key
|
||||
of the key of the key of the... You get it. I've chosen to protect the exported
|
||||
private key by a password stored on my password manager which has its own
|
||||
password that I know in my head. The security stops if I forget the password
|
||||
manager's password, and it's ok.
|
||||
|
||||
I also use PGP to **sign my git commits**.
|
||||
|
||||
## Access
|
||||
|
||||
There are two differents PINs for the PGP application on the Yubikey:
|
||||
- **Admin PIN**: to unlock PGP administration commands
|
||||
- **PIN**: to unlock the PGP private key
|
||||
|
||||
The PIN is specific to the PGP application. If you have already set up a FIDO
|
||||
PIN, please chose a different one for PGP.
|
||||
|
||||
Unlike FIDO, default PINs are set from factory. Run the "reset" operation only
|
||||
if you don't know the current PIN. Be careful, this is a **destructive**
|
||||
operation. Any existing PGP key will be removed.
|
||||
|
||||
```
|
||||
ykman openpgp reset
|
||||
```
|
||||
|
||||
Change the Admin PIN:
|
||||
|
||||
```
|
||||
ykman openpgp access change-admin-pin --admin-pin 12345678
|
||||
```
|
||||
|
||||
Change the PIN:
|
||||
|
||||
```
|
||||
ykman openpgp access change-pin --pin 123456
|
||||
```
|
||||
|
||||
## Generate key
|
||||
|
||||
Let's generate the key pair locally, then move the private key to the Yubikey
|
||||
afterwards.
|
||||
|
||||
```
|
||||
gpg --expert --full-gen-key
|
||||
Please select what kind of key you want:
|
||||
(9) ECC (sign and encrypt) *default*
|
||||
Your selection? 9
|
||||
Please select which elliptic curve you want:
|
||||
(1) Curve 25519 *default*
|
||||
Your selection? 1
|
||||
Please specify how long the key should be valid.
|
||||
Key is valid for? (0) 1y
|
||||
Is this correct? (y/N) y
|
||||
```
|
||||
|
||||
Enter real name, e-mail address and eventually a comment.
|
||||
|
||||
Validate:
|
||||
```
|
||||
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
|
||||
```
|
||||
|
||||
Then move key to the Yubikey:
|
||||
|
||||
```
|
||||
gpg --edit-key 0x1234
|
||||
gpg> keytocard
|
||||
```
|
||||
|
||||
Enter the **PGP password**, the one to protect the private key itself, then the
|
||||
**Admin PIN** to store it on the Yubikey.
|
||||
|
||||
## Publish to keyserver
|
||||
|
||||
How to discover public keys from other people?
|
||||
|
||||
1. Participate to a [key signing
|
||||
party](https://en.wikipedia.org/wiki/Key_signing_party) (at
|
||||
[FOSDEM](https://fosdem.org) for example)
|
||||
1. Use a **keyserver**, because we cannot meet everybody in person
|
||||
|
||||
The [keys.openpgp.org](https://keys.openpgp.org/) server seems to be a popular
|
||||
option to publish your public key. It verifies your identity by sending an
|
||||
e-mail to every PGP identity (= e-mail) included in the published key.
|
||||
|
||||
```
|
||||
gpg --export 0x1234 | curl -T - https://keys.openpgp.org
|
||||
```
|
||||
|
||||
## Info on the card
|
||||
|
||||
The gpg binary enables you to store more information like your full name and
|
||||
the URL of your public key, directly on the Yubikey. Feel free to set them up
|
||||
or not. Anyone grabbing your Yubikey will be able to retreive such information.
|
||||
|
||||
```
|
||||
gpg --card-edit
|
||||
gpg/card> admin
|
||||
gpg/card> name
|
||||
```
|
||||
|
||||
Enter your **last** name, **first** name, then the Admin PIN to save the
|
||||
modification.
|
||||
|
||||
For the URL:
|
||||
```
|
||||
gpg/card> url
|
||||
```
|
||||
|
||||
Enter the public key URL (ex:
|
||||
`https://keys.openpgp.org/vks/v1/by-fingerprint/1234`), then the Admin PIN to
|
||||
save the modification.
|
||||
|
||||
Verify:
|
||||
|
||||
```
|
||||
gpg --card-status
|
||||
```
|
||||
|
||||
This commands tells you if your Yubikey has been detected by the gpg
|
||||
application by showing the card details. Sometimes, you could have the
|
||||
following error:
|
||||
|
||||
```
|
||||
gpg: OpenPGP card not available: General error
|
||||
```
|
||||
|
||||
In that case, you should unplug then plug your Yubikey.
|
||||
|
||||
<p style="text-align: center">
|
||||
<img
|
||||
src="/yubikey/the-it-crowd-meme.jpg"
|
||||
alt="The IT Crowd (TV show) meme saying 'Have you tried to turning it off and on again?'"
|
||||
/>
|
||||
</p>
|
||||
|
||||
## Renew an expired key
|
||||
|
||||
It's important to set an expiration duration because if you lose control over
|
||||
your key, it will expire automatically. I've performed this
|
||||
[operation](https://superuser.com/questions/813421/can-you-extend-the-expiration-date-of-an-already-expired-gpg-key/1141251#1141251)
|
||||
a couple of times over the years.
|
||||
|
||||
Edit the main key:
|
||||
|
||||
```
|
||||
gpg --edit-key 0x1234
|
||||
gpg> expire
|
||||
Key is valid for? (0) 1y
|
||||
Is this correct? (y/N) y
|
||||
```
|
||||
|
||||
Enter the PIN to unlock the Yubikey.
|
||||
|
||||
Then edit the sub key:
|
||||
|
||||
```
|
||||
gpg> key 1
|
||||
gpg> expire
|
||||
Key is valid for? (0) 1y
|
||||
Is this correct? (y/N) y
|
||||
```
|
||||
|
||||
Enter the PIN to unlock the Yubikey.
|
||||
|
||||
Save and publish:
|
||||
|
||||
```
|
||||
gpg> save
|
||||
gpg --keyserver keys.openpgp.org --send-keys 0x1234
|
||||
```
|
||||
|
||||
This doesn't prevent from compromision. In that case, you should [revoke the
|
||||
key](https://superuser.com/questions/1526283/how-to-revoke-a-gpg-key-and-upload-in-gpg-server).
|
||||
|
||||
## Sign git commits
|
||||
|
||||
[Git](https://git-scm.com/) is a very popular [version
|
||||
control](https://en.wikipedia.org/wiki/Version_control) software used by
|
||||
open-source projects to distribute code and accept contributions. Show the
|
||||
world that you own your git commits! With PGP, you can sign your commits so
|
||||
everybody can verify that you are effectively the one and true author of the
|
||||
commit, or your private key has been compromised but that's another topic.
|
||||
|
||||
File `~/.gitconfig`:
|
||||
|
||||
```
|
||||
[user]
|
||||
email = first@name.email
|
||||
name = First Name
|
||||
signingkey = 0x1234
|
||||
```
|
||||
|
||||
Every time you will try to commit a change using git, you will have to unlock
|
||||
your PGP private key on the Yubikey by entering the PIN.
|
||||
|
||||
Finally, add your public key to your [Github
|
||||
account](https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account)
|
||||
so everyone will see the check mark on your commits.
|
||||
|
||||
<p style="text-align: center">
|
||||
<img
|
||||
src="/yubikey/github-signed-commit.png"
|
||||
alt="Screenshot from Github with 'jouir committed 2 weeks ago' + 'Verified'"
|
||||
/>
|
||||
</p>
|
||||
|
||||
# Sudo
|
||||
|
||||
The Yubikey can be used to secure [sudo](https://en.wikipedia.org/wiki/Sudo),
|
||||
the software used to execute commands with root privileges. You can decide to
|
||||
**replace** your password by a touch on the Yubikey ("passwordless"), or
|
||||
**add** a touch on the Yubikey after the password ("2FA"). [This blog
|
||||
post](https://dev.to/bashbunni/set-up-yubikey-for-passwordless-sudo-authentication-4h5o)
|
||||
describes the procedure to do both.
|
||||
|
||||
I've tried to setup a **passwordless** authentication for sudo but I'm still
|
||||
asked for my password from time to time. And when the Yubikey requires to be
|
||||
touched, sudo doesn't print any instruction on the terminal, the Yubikey starts
|
||||
to blink. The sudo command is not stuck, you just have to touch the Yubikey.
|
||||
|
||||
# Conclusion
|
||||
|
||||
Is my digital life more secure now? Yes, probably. But security comes at a
|
||||
cost. The cost of entering two passwords and touch the Yubikey for **every
|
||||
single SSH connection** (maybe using SSH with PIV is easier after all). The
|
||||
cost of encrypting messages with PGP to non tech-savvy people. The cost of
|
||||
monitoring the expiration date of your PGP keys. The cost of the Yubikey
|
||||
itself. On the bright side, replacing vicious OTPs that regenerate too quickly
|
||||
by a simple touch is very nice! Same for sudo. In the end, it was a fun project
|
||||
and that's what matters.
|
BIN
content/imgs/profile.jpg
Normal file
BIN
content/imgs/profile.jpg
Normal file
Binary file not shown.
After Width: | Height: | Size: 36 KiB |
33
content/talks.md
Normal file
33
content/talks.md
Normal file
|
@ -0,0 +1,33 @@
|
|||
---
|
||||
title: Talks
|
||||
---
|
||||
|
||||
# 2024
|
||||
|
||||
* 2024-09-13: [Efficient Time Series Management with TimescaleDB at OVHcloud](/pgdaynl2024.html) ([transcript](/pgdaynl2024.handout.html), [video](https://www.youtube.com/watch?v=l2CiGydVXgI)) @ [PGDay Lowlands 2024](https://www.postgresql.eu/events/pgdaynl2024/schedule/session/5614-efficient-time-series-management-with-timescaledb-at-ovhcloud/)
|
||||
* 2024-06-12: [PostGIS et la collection Hard Rock Cafe](/pgdayfr2024-hardrockcafe.html) (FR) @ [PG Day France 2024](https://pgday.fr) (lightning talk)
|
||||
* 2024-06-12: [Trucs et astuces pour TimescaleDB](/pgdayfr2024-timescaledb.html) (FR) @ [PG Day France 2024](https://pgday.fr) (lightning talk)
|
||||
* 2024-03-16: [Journey of a Home-based Personal Cloud Storage Project](/socallinuxexpo2024.html) ([transcript](/socallinuxexpo2024.handout.html), [video](https://www.youtube.com/watch?v=VYAdTSkDNjk)) @ [SCaLE 21x](https://www.socallinuxexpo.org/scale/21x/presentations/journey-home-based-personal-cloud-storage-project)
|
||||
* 2024-03-15: [Database schema management for lazybones: from chaos to heaven](/postgresatscale2024.html) ([transcript](/postgresatscale2024.handout.html), [video](https://www.youtube.com/watch?v=cD79bTGh6Zc)) @ [PostgreSQL@SCaLE 21x](https://www.socallinuxexpo.org/scale/21x/presentations/database-schema-management-lazybones-chaos-heaven)
|
||||
* 2024-02-13: [Real-Time Feeding of a Data Lake with PostgreSQL and Debezium](/meetupbe2024.html) ([transcript](/meetupbe2024.handout.html)) @ [PostgreSQL Users Group Belgium](https://www.meetup.com/postgresbe/events/298633135/)
|
||||
* 2024-02-06: [Automating Internal Databases Operations at OVHcloud with Ansible](/cfgmgmtcamp2024.html) ([transcript](/cfgmgmtcamp2024.handout.html), [video](https://www.youtube.com/live/I2FaIdC5Rus?si=tdmqQMuItsigF3sl&t=3587)) @ [Config Management Camp 2024](https://cfp.cfgmgmtcamp.org/2024/talk/P3NKVG/)
|
||||
* 2024-01-25: [Alimentation d'un Data Lake en temps réel grâce à PostgreSQL et Debezium](/meetuplille2024.html) (FR) ([transcript](/meetuplille2024.handout.html)) @ [Meetup PostgreSQL Lille](https://www.meetup.com/meetup-postgresql-lille/events/298087677/)
|
||||
|
||||
# 2022
|
||||
|
||||
* 2022-09-23: [The Elephantine Upgrade](/pgconfnyc2022.pdf) ([video](https://www.youtube.com/watch?v=TvjaD1GjQvA)) @ [PGConf NYC 2022](https://postgresql.us/events/pgconfnyc2022/sessions/session/998-the-elephantine-upgrade/)
|
||||
* 2022-06-22: [Automatisation d'une mise à jour éléphantesque](/pgdayfrance2022.pdf) (FR) ([video](https://www.youtube.com/watch?v=Rlrt4LpieW0)) @ [PG Day France 2022](https://2022.pgday.fr/programme)
|
||||
|
||||
# 2021
|
||||
|
||||
* 2021-02-06: [Databases schema management for lazybones: from chaos to heaven](/fosdem21.pdf) ([video](https://video.fosdem.org/2021/D.postgresql/postgresql_database_schema_management_for_lazybones_from_chaos_to_heaven.webm)) @ [FOSDEM 21](https://fosdem.org/2021/schedule/event/postgresql_database_schema_management_for_lazybones_from_chaos_to_heaven/)
|
||||
|
||||
# 2020
|
||||
|
||||
* 2020-10-21: [Security and Traceability on Distributed Database Systems](/perconaliveonline2020.pdf) ([video](https://www.youtube.com/watch?v=3uoA4FlGwr4)) @ [Percona Live Online 2020](https://perconaliveonline2020.sched.com/event/ePpB)
|
||||
* 2020-03-05: [Databases schema management for lazybones: from chaos to heaven](/meetupbe2020.pdf) @ [PostgreSQL Users Group Belgium](https://www.meetup.com/postgresbe/events/268772486/)
|
||||
|
||||
# 2019
|
||||
|
||||
* 2019-09-12: [Upgrade all the things!](/postgresopen2019.pdf) ([video](https://www.youtube.com/watch?v=53eiI_31ZVY)) @ [PostgresOpen 2019](https://postgresql.us/events/pgopen2019/schedule/session/613-upgrade-all-the-things/)
|
||||
* 2019-06-19: [Dans les coulisses d'une infrastructure hautement disponible](/pgdayfrance2019.pdf) (FR) ([video](https://www.youtube.com/watch?v=DOU5xgrP3PI)) @ [PG Day France 2019](https://2019.pgday.fr/programme)
|
42
hugo.yaml
Normal file
42
hugo.yaml
Normal file
|
@ -0,0 +1,42 @@
|
|||
---
|
||||
baseURL: https://julien.riou.xyz/
|
||||
languageCode: en-us
|
||||
title: Julien Riou
|
||||
theme: hugo-xmin
|
||||
|
||||
permalinks:
|
||||
blog: "/blog/:year/:month/:day/:slug"
|
||||
|
||||
menu:
|
||||
main:
|
||||
- name: Home
|
||||
url: ""
|
||||
weight: 1
|
||||
- name: Talks
|
||||
url: "/talks/"
|
||||
weight: 2
|
||||
- name: Categories
|
||||
url: "/categories/"
|
||||
weight: 3
|
||||
|
||||
markup:
|
||||
highlight:
|
||||
codeFences: false
|
||||
goldmark:
|
||||
renderer:
|
||||
unsafe: true
|
||||
extensions:
|
||||
passthrough:
|
||||
enable: true
|
||||
delimiters:
|
||||
block:
|
||||
- - \[
|
||||
- \]
|
||||
- - $$
|
||||
- $$
|
||||
inline:
|
||||
- - \(
|
||||
- \)
|
||||
|
||||
taxonomies:
|
||||
category: categories
|
71
layouts/_default/rss.xml
Normal file
71
layouts/_default/rss.xml
Normal file
|
@ -0,0 +1,71 @@
|
|||
{{- /* Deprecate site.Author.email in favor of site.Params.author.email */}}
|
||||
{{- $authorEmail := "" }}
|
||||
{{- with site.Params.author }}
|
||||
{{- if reflect.IsMap . }}
|
||||
{{- with .email }}
|
||||
{{- $authorEmail = . }}
|
||||
{{- end }}
|
||||
{{- end }}
|
||||
{{- else }}
|
||||
{{- with site.Author.email }}
|
||||
{{- $authorEmail = . }}
|
||||
{{- warnf "The author key in site configuration is deprecated. Use params.author.email instead." }}
|
||||
{{- end }}
|
||||
{{- end }}
|
||||
|
||||
{{- /* Deprecate site.Author.name in favor of site.Params.author.name */}}
|
||||
{{- $authorName := "" }}
|
||||
{{- with site.Params.author }}
|
||||
{{- if reflect.IsMap . }}
|
||||
{{- with .name }}
|
||||
{{- $authorName = . }}
|
||||
{{- end }}
|
||||
{{- else }}
|
||||
{{- $authorName = . }}
|
||||
{{- end }}
|
||||
{{- else }}
|
||||
{{- with site.Author.name }}
|
||||
{{- $authorName = . }}
|
||||
{{- warnf "The author key in site configuration is deprecated. Use params.author.name instead." }}
|
||||
{{- end }}
|
||||
{{- end }}
|
||||
|
||||
{{- $pctx := . }}
|
||||
{{- if .IsHome }}{{ $pctx = .Site }}{{ end }}
|
||||
{{- $pages := slice }}
|
||||
{{- if or $.IsHome $.IsSection }}
|
||||
{{- $pages = (where (where $pctx.RegularPages ".Section" "blog") "Kind" "page") }}
|
||||
{{- else }}
|
||||
{{- $pages = (where (where $pctx.Pages ".Section" "blog") "Kind" "page") }}
|
||||
{{- end }}
|
||||
{{- $limit := .Site.Config.Services.RSS.Limit }}
|
||||
{{- if ge $limit 1 }}
|
||||
{{- $pages = $pages | first $limit }}
|
||||
{{- end }}
|
||||
{{- printf "<?xml version=\"1.0\" encoding=\"utf-8\" standalone=\"yes\"?>" | safeHTML }}
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>{{ if eq .Title .Site.Title }}{{ .Site.Title }}{{ else }}{{ with .Title }}{{ . }} on {{ end }}{{ .Site.Title }}{{ end }}</title>
|
||||
<link>{{ .Permalink }}</link>
|
||||
<description>Recent content {{ if ne .Title .Site.Title }}{{ with .Title }}in {{ . }} {{ end }}{{ end }}on {{ .Site.Title }}</description>
|
||||
<generator>Hugo</generator>
|
||||
<language>{{ site.Language.LanguageCode }}</language>{{ with $authorEmail }}
|
||||
<managingEditor>{{.}}{{ with $authorName }} ({{ . }}){{ end }}</managingEditor>{{ end }}{{ with $authorEmail }}
|
||||
<webMaster>{{ . }}{{ with $authorName }} ({{ . }}){{ end }}</webMaster>{{ end }}{{ with .Site.Copyright }}
|
||||
<copyright>{{ . }}</copyright>{{ end }}{{ if not .Date.IsZero }}
|
||||
<lastBuildDate>{{ (index $pages.ByLastmod.Reverse 0).Lastmod.Format "Mon, 02 Jan 2006 15:04:05 -0700" | safeHTML }}</lastBuildDate>{{ end }}
|
||||
{{- with .OutputFormats.Get "RSS" }}
|
||||
{{ printf "<atom:link href=%q rel=\"self\" type=%q />" .Permalink .MediaType | safeHTML }}
|
||||
{{- end }}
|
||||
{{- range $pages }}
|
||||
<item>
|
||||
<title>{{ .Title }}</title>
|
||||
<link>{{ .Permalink }}</link>
|
||||
<pubDate>{{ .PublishDate.Format "Mon, 02 Jan 2006 15:04:05 -0700" | safeHTML }}</pubDate>
|
||||
{{- with $authorEmail }}<author>{{ . }}{{ with $authorName }} ({{ . }}){{ end }}</author>{{ end }}
|
||||
<guid>{{ .Permalink }}</guid>
|
||||
<description>{{ .Content | transform.XMLEscape | safeHTML }}</description>
|
||||
</item>
|
||||
{{- end }}
|
||||
</channel>
|
||||
</rss>
|
9
layouts/partials/footer.html
Normal file
9
layouts/partials/footer.html
Normal file
|
@ -0,0 +1,9 @@
|
|||
<hr>
|
||||
<footer>
|
||||
<div>
|
||||
<p>
|
||||
Julien Riou<br />
|
||||
Made with <a href="https://gohugo.io/">Hugo</a> (<a href="https://github.com/yihui/hugo-xmin">xmin</a>) and passion
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
1
layouts/partials/head_custom.html
Normal file
1
layouts/partials/head_custom.html
Normal file
|
@ -0,0 +1 @@
|
|||
<link rel="alternate" type="application/rss+xml" href="{{.Site.BaseURL }}index.xml" title="{{ .Site.Title }}">
|
1092
static/cfgmgmtcamp2024.handout.html
Normal file
1092
static/cfgmgmtcamp2024.handout.html
Normal file
File diff suppressed because one or more lines are too long
1708
static/cfgmgmtcamp2024.html
Normal file
1708
static/cfgmgmtcamp2024.html
Normal file
File diff suppressed because one or more lines are too long
BIN
static/css/Signika-Regular.ttf
Normal file
BIN
static/css/Signika-Regular.ttf
Normal file
Binary file not shown.
19
static/css/fonts.css
Normal file
19
static/css/fonts.css
Normal file
|
@ -0,0 +1,19 @@
|
|||
@font-face {
|
||||
font-family: "Signika-Regular";
|
||||
src: url("Signika-Regular.ttf");
|
||||
}
|
||||
|
||||
body {
|
||||
font-family: "Signika-Regular"
|
||||
}
|
||||
|
||||
.center {
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
.rounded {
|
||||
-moz-border-radius: 50%;
|
||||
border-radius: 50%;
|
||||
border: 1px solid grey;
|
||||
padding: 5px;
|
||||
}
|
3
static/css/general.css
Normal file
3
static/css/general.css
Normal file
|
@ -0,0 +1,3 @@
|
|||
.center {
|
||||
text-align: center;
|
||||
}
|
BIN
static/forgejo-screenshot.png
Normal file
BIN
static/forgejo-screenshot.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 393 KiB |
1292
static/forgejo.excalidraw
Normal file
1292
static/forgejo.excalidraw
Normal file
File diff suppressed because it is too large
Load diff
11
static/forgejo.svg
Normal file
11
static/forgejo.svg
Normal file
File diff suppressed because one or more lines are too long
After Width: | Height: | Size: 24 KiB |
BIN
static/fosdem21.pdf
Normal file
BIN
static/fosdem21.pdf
Normal file
Binary file not shown.
25
static/hrc/collection.csv
Normal file
25
static/hrc/collection.csv
Normal file
|
@ -0,0 +1,25 @@
|
|||
Dublin
|
||||
Los Angeles
|
||||
Prague
|
||||
London
|
||||
Miami Gardens
|
||||
Hamburg
|
||||
Orlando
|
||||
New York
|
||||
San Francisco
|
||||
Boston
|
||||
Singapore
|
||||
Hollywood
|
||||
Detroit
|
||||
Amsterdam
|
||||
Angkor
|
||||
Lisbon
|
||||
Ho Chi Minh City
|
||||
Barcelona
|
||||
Brussels
|
||||
Yankee Stadium
|
||||
Oslo
|
||||
Paris
|
||||
Berlin
|
||||
Antwerp
|
||||
Miami
|
|
25
static/hrc/collection.py
Executable file
25
static/hrc/collection.py
Executable file
|
@ -0,0 +1,25 @@
|
|||
#!/usr/bin/env python3
|
||||
import requests
|
||||
import csv
|
||||
import time
|
||||
|
||||
|
||||
if __name__ == "__main__":
|
||||
headers = {"User-Agent": "Hard Rock Cafe Blog Post From Julien Riou"}
|
||||
session = requests.Session()
|
||||
session.headers.update(headers)
|
||||
|
||||
with open("collection_with_coordinates.csv", "w") as dest:
|
||||
writer = csv.writer(dest)
|
||||
with open("collection.csv", "r") as source:
|
||||
for row in csv.reader(source):
|
||||
name = row[0]
|
||||
r = session.get(f"https://nominatim.openstreetmap.org/search?q={name}&limit=1&format=json")
|
||||
time.sleep(1)
|
||||
r.raise_for_status()
|
||||
data = r.json()
|
||||
if len(data) == 1:
|
||||
data = data[0]
|
||||
writer.writerow([name, data["lon"], data["lat"]])
|
||||
else:
|
||||
print(f"Location not found for {title}, skipping")
|
25
static/hrc/collection_with_coordinates.csv
Normal file
25
static/hrc/collection_with_coordinates.csv
Normal file
|
@ -0,0 +1,25 @@
|
|||
Dublin,53.3493795,-6.2605593
|
||||
Los Angeles,34.0536909,-118.242766
|
||||
Prague,50.0596288,14.446459273258009
|
||||
London,51.4893335,-0.14405508452768728
|
||||
Miami Gardens,25.9420377,-80.2456045
|
||||
Hamburg,53.550341,10.000654
|
||||
Orlando,28.5421109,-81.3790304
|
||||
New York,40.7127281,-74.0060152
|
||||
San Francisco,37.7792588,-122.4193286
|
||||
Boston,42.3554334,-71.060511
|
||||
Singapore,1.357107,103.8194992
|
||||
Hollywood,34.0980031,-118.329523
|
||||
Detroit,42.3315509,-83.0466403
|
||||
Amsterdam,52.3730796,4.8924534
|
||||
Angkor,11.5717566,104.92848
|
||||
Lisbon,38.7077507,-9.1365919
|
||||
Ho Chi Minh City,10.7763897,106.7011391
|
||||
Barcelona,41.3828939,2.1774322
|
||||
Brussels,50.8465573,4.351697
|
||||
Yankee Stadium,40.82958275,-73.92652118491901
|
||||
Oslo,59.9133301,10.7389701
|
||||
Paris,48.8588897,2.3200410217200766
|
||||
Berlin,52.5170365,13.3888599
|
||||
Antwerp,51.2211097,4.3997081
|
||||
Miami,25.7741728,-80.19362
|
|
163
static/hrc/nodes.csv
Normal file
163
static/hrc/nodes.csv
Normal file
|
@ -0,0 +1,163 @@
|
|||
"Hard Rock Cafe Amsterdam","52.36211","4.88298"
|
||||
"Hard Rock Cafe Andorra","42.507707","1.531977"
|
||||
"Hard Rock Cafe Angkor","13.35314","103.85676"
|
||||
"Hard Rock Cafe Asuncion","-25.2896910","-57.5737599"
|
||||
"Hard Rock Cafe Athens","37.97642","23.72584"
|
||||
"Hard Rock Cafe Atlanta","33.75978","-84.3874"
|
||||
"Hard Rock Cafe Atlantic City","39.359131","-74.417321"
|
||||
"Hard Rock Cafe Ayia Napa","34.989260","34.000232"
|
||||
"Hard Rock Cafe Bali","-8.72188","115.16989"
|
||||
"Hard Rock Cafe Bali Airport","-8.7448956","115.1653683"
|
||||
"Hard Rock Cafe Baltimore","39.2861","-76.60738"
|
||||
"Hard Rock Cafe Bangkok","13.7440272","100.5420842"
|
||||
"Hard Rock Cafe Barcelona","41.385880","2.170830"
|
||||
"Hard Rock Cafe Bengaluru","12.96984","77.60088"
|
||||
"Hard Rock Cafe Bengaluru Airport","13.19986","77.71551"
|
||||
"Hard Rock Cafe Bengaluru Whitefield","12.986775","77.735883"
|
||||
"Hard Rock Cafe Berlin","52.503112","13.329474"
|
||||
"Hard Rock Cafe Biloxi","30.39255","-88.88771"
|
||||
"Hard Rock Cafe Brussels","50.84618","4.35292"
|
||||
"Hard Rock Cafe Bucharest","44.47564","26.07622"
|
||||
"Hard Rock Cafe Budapest","47.49615","19.05106"
|
||||
"Hard Rock Cafe Buenos Aires Aeroparque","-34.55803","-58.417009"
|
||||
"Hard Rock Cafe Cabo San Lucas","22.887190","-109.911603"
|
||||
"Hard Rock Cafe Cancun","21.132179","-86.746964"
|
||||
"Hard Rock Cafe Cape Town","-33.952935","18.3753743"
|
||||
"Hard Rock Cafe Caracas","10.502818","-66.845608"
|
||||
"Hard Rock Cafe Cartagena","10.42216","-75.55017"
|
||||
"Hard Rock Cafe Cayman Islands","19.2937","-81.3838"
|
||||
"Hard Rock Cafe Changi Airport Singapore","1.355365829","103.9891753"
|
||||
"Hard Rock Cafe Chennai","13.0658047","80.2395507"
|
||||
"Hard Rock Cafe Chiang Mai","18.783975","99.000409"
|
||||
"Hard Rock Cafe Chicago","41.89312","-87.63059"
|
||||
"Hard Rock Cafe Cincinnati","39.10829776941105","-84.50682523998104"
|
||||
"Hard Rock Cafe Cologne","50.936166","6.957734"
|
||||
"Hard Rock Cafe Copenhagen","55.6766896","12.56900410000003"
|
||||
"Hard Rock Cafe Cordoba Airport","31.31462","64.21349"
|
||||
"Hard Rock Cafe Cozumel","20.478774","-86.972582"
|
||||
"Hard Rock Cafe Curitiba","-25.438177","-49.281201"
|
||||
"Hard Rock Cafe Dubai","25.223864","55.351410"
|
||||
"Hard Rock Cafe Dubai Airport","25.245024","55.360507"
|
||||
"Hard Rock Cafe Dublin","53.34582","-6.26081"
|
||||
"Hard Rock Cafe Dubrovnik","42.64167","18.10698"
|
||||
"Hard Rock Cafe Edinburgh","55.95364","-3.19642"
|
||||
"Hard Rock Cafe Florence","43.772025","11.253518"
|
||||
"Hard Rock Cafe Florianopolis","-27.58944868266472","-48.51511813068522"
|
||||
"Hard Rock Cafe Fortaleza","-3.741667","-38.473458"
|
||||
"Hard Rock Cafe Foxwoods","41.47611","-71.96127"
|
||||
"Hard Rock Cafe Gdansk","54.3484","18.65446"
|
||||
"Hard Rock Cafe Gothenburg","57.70137","11.9741"
|
||||
"Hard Rock Cafe Gramado","-29.38112","-50.871195"
|
||||
"Hard Rock Cafe Gran Canaria","27.753661","-15.570056"
|
||||
"Hard Rock Cafe Guam","13.51461","144.80585"
|
||||
"Hard Rock Cafe Guyana","6.8247628","-58.1838637"
|
||||
"Hard Rock Cafe Hamburg","53.5457182","9.9658749"
|
||||
"Hard Rock Cafe Hollywood FL","26.05192","-80.21249"
|
||||
"Hard Rock Cafe Hollywood on Hollywood Blvd","34.10263","-118.33967"
|
||||
"Hard Rock Cafe Honolulu","21.28092","-157.83077"
|
||||
"Hard Rock Cafe Hurghada","27.17179","33.82352"
|
||||
"Hard Rock Cafe Hyderabad","17.41943","78.44837"
|
||||
"Hard Rock Cafe Hyderabad Hitech City","17.4329","78.3815"
|
||||
"Hard Rock Cafe Ibiza","38.90927","1.43399"
|
||||
"Hard Rock Cafe Iguazu Airport","-25.73157","-54.47620"
|
||||
"Hard Rock Cafe Innsbruck","47.265844","11.393448"
|
||||
"Hard Rock Cafe Ipoh","4.592740","101.086059"
|
||||
"Hard Rock Cafe Jiuzhaigou","33.29059","103.87573"
|
||||
"Hard Rock Cafe Johannesburg","-26.1074","28.05466"
|
||||
"Hard Rock Cafe Kathmandu","27.7105","85.3179"
|
||||
"Hard Rock Cafe Key West","24.55783","-81.80423"
|
||||
"Hard Rock Cafe Kolkata","22.552528","88.353160"
|
||||
"Hard Rock Cafe Krakow","50.06144","19.93898"
|
||||
"Hard Rock Cafe Kuala Lumpur","3.15573","101.70547"
|
||||
"Hard Rock Cafe Kuala Lumpur International Airport","2.7417","101.7016"
|
||||
"Hard Rock Cafe La Paz","-16.531337661807843","-68.08743677671306"
|
||||
"Hard Rock Cafe Lagos","6.4226444","3.4419286"
|
||||
"Hard Rock Cafe Las Vegas","36.10425","-115.17259"
|
||||
"Hard Rock Cafe Lisbon","38.71646","-9.14174"
|
||||
"Hard Rock Cafe London","51.5038936","-0.14912010000000464"
|
||||
"Hard Rock Cafe London Piccadilly Circus","51.50991","-0.133722"
|
||||
"Hard Rock Cafe Madrid Rock Shop","40.418437","-3.7073207"
|
||||
"Hard Rock Cafe Makati","14.33084","121.01315"
|
||||
"Hard Rock Cafe Malaga","36.7184","-4.4129"
|
||||
"Hard Rock Cafe Maldives","4.1226668","73.4660499"
|
||||
"Hard Rock Cafe Mallorca","39.56921","2.63501"
|
||||
"Hard Rock Cafe Malta Airport","35.855174","14.4816053"
|
||||
"Hard Rock Cafe Malta Bar (Valletta)","35.8902","14.50795"
|
||||
"Hard Rock Cafe Manchester","53.48528","-2.24073"
|
||||
"Hard Rock Cafe Manila","14.532715","120.980290"
|
||||
"Hard Rock Cafe Melaka","2.195","102.24825"
|
||||
"Hard Rock Cafe Miami","25.77724","-80.18457"
|
||||
"Hard Rock Cafe Milan","45.46606990647218","9.185745840359427"
|
||||
"Hard Rock Cafe Montevideo","-34.909481","-56.134371"
|
||||
"Hard Rock Cafe Munich","48.1377183","11.5774404"
|
||||
"Hard Rock Cafe Myrtle Beach","33.71841","-78.88076"
|
||||
"Hard Rock Cafe Nabq","28.043474","34.430348"
|
||||
"Hard Rock Cafe Nashville","36.16232","-86.77491"
|
||||
"Hard Rock Cafe Newcastle","54.96856805987448","-1.6079029765494606"
|
||||
"Hard Rock Cafe New Delhi","28.6291500","77.2197880"
|
||||
"Hard Rock Cafe New Orleans","29.954689","-90.069360"
|
||||
"Hard Rock Cafe New York Times Square","40.75692","-73.98649"
|
||||
"Hard Rock Cafe Niagara Falls Canada","43.09116","-79.07204"
|
||||
"Hard Rock Cafe Niagara Falls USA","43.08684","-79.06456"
|
||||
"Hard Rock Cafe Northern Indiana","41.56693775234533","-87.40398532233412"
|
||||
"Hard Rock Cafe Orlando","28.473711","-81.467376"
|
||||
"Hard Rock Cafe Osaka Universal","34.66806","135.43617"
|
||||
"Hard Rock Cafe Panama","8.975924","-79.517112"
|
||||
"Hard Rock Cafe Paris","48.87187","2.34158"
|
||||
"Hard Rock Cafe Pattaya","12.93956","100.88508"
|
||||
"Hard Rock Cafe Penang","5.4676","100.24155"
|
||||
"Hard Rock Cafe Philadelphia","39.95206","-75.15975"
|
||||
"Hard Rock Cafe Phnom Penh","11.574152","104.922030"
|
||||
"Hard Rock Cafe Phuket","7.887383","98.294382"
|
||||
"Hard Rock Cafe Pigeon Forge","35.82423","-83.57914"
|
||||
"Hard Rock Cafe Pittsburgh","40.43386","-80.00499"
|
||||
"Hard Rock Cafe Playa Del Carmen","20.624119","-87.074036"
|
||||
"Hard Rock Cafe Podgorica","42.4416389","19.2618695"
|
||||
"Hard Rock Cafe Ponce","17.997039","-66.604014"
|
||||
"Hard Rock Cafe Port El Kantaoui","35.907104","10.581355"
|
||||
"Hard Rock Cafe Porto","41.147173","-8.614191764"
|
||||
"Hard Rock Cafe Porto Alegre","-30.08043363991145","-51.24698597782039"
|
||||
"Hard Rock Cafe Prague","50.086735","14.419145"
|
||||
"Hard Rock Cafe Puerto Madero","-34.600622","-58.367225"
|
||||
"Hard Rock Cafe Puerto Plata","19.7637395","-70.5164890"
|
||||
"Hard Rock Cafe Puteri Harbour","1.4124476909637451","103.65474700927734"
|
||||
"Hard Rock Cafe Punta Cana","18.6479967","-68.4943815"
|
||||
"Hard Rock Cafe Pune","18.5185929","73.9316109"
|
||||
"Hard Rock Cafe Reykjavik","64.1470386","-21.9393442"
|
||||
"Hard Rock Cafe Ribeirão Preto","-21.2022974","-47.7910663"
|
||||
"Hard Rock Cafe Rome","41.90622","12.48975"
|
||||
"Hard Rock Cafe Sacramento","39.036131","-121.514621"
|
||||
"Hard Rock Cafe Saipan","15.20915","145.71752"
|
||||
"Hard Rock Cafe San Antonio","29.42511","-98.48912"
|
||||
"Hard Rock Cafe San Francisco","37.80861","-122.40998"
|
||||
"Hard Rock Cafe Santa Cruz","-17.753311","-63.199008"
|
||||
"Hard Rock Cafe Santiago","-33.41756","-70.60818"
|
||||
"Hard Rock Cafe Santo Domingo","18.47275","-69.94113"
|
||||
"Hard Rock Cafe Sharm el Sheikh","27.90939","34.32391"
|
||||
"Hard Rock Cafe Shenzhen","22.720865","114.07425"
|
||||
"Hard Rock Cafe Singapore","1.3058623","103.8279541"
|
||||
"Hard Rock Cafe Stockholm","59.34414","18.05507"
|
||||
"Hard Rock Cafe Sun City","-25.356593","27.097766"
|
||||
"Hard Rock Cafe Suriname","5.856529","-55.173806"
|
||||
"Hard Rock Cafe Suriname Airport","5.456535","-55.198445"
|
||||
"Hard Rock Cafe Tampa","27.99347","-82.37259"
|
||||
"Hard Rock Cafe Tampa Airport","27.980743","-82.534012"
|
||||
"Hard Rock Cafe Tenerife","28.05463","-16.73126"
|
||||
"Hard Rock Cafe Tianjin","39.092829","117.176028"
|
||||
"Hard Rock Cafe Tokyo Roppongi","35.66178","139.73413"
|
||||
"Hard Rock Cafe Tokyo Uyeno Eki","35.71393","139.77734"
|
||||
"Hard Rock Cafe Toronto","43.65665412475884","-79.38074259583352"
|
||||
"Hard Rock Cafe Tromso","69.64772576701856","18.95328541129822"
|
||||
"Hard Rock Cafe Ulaanbaatar","47.916836","106.916672"
|
||||
"Hard Rock Cafe Ushuaia","-54.806768","-68.30604"
|
||||
"Hard Rock Cafe Valencia","39.468953","-0.377121"
|
||||
"Hard Rock Cafe Venice","45.43419","12.33681"
|
||||
"Hard Rock Cafe Vienna","48.21131","16.37556"
|
||||
"Hard Rock Cafe Vientiane","17.96514012167344","102.6062438540694"
|
||||
"Hard Rock Cafe Yerevan","40.18003141198915","44.51608478273878"
|
||||
"Hard Rock Cafe Warsaw","52.23017","21.00269"
|
||||
"Hard Rock Cafe Washington DC","38.89635","-77.02595"
|
||||
"Hard Rock Cafe Wroclaw","51.109157","17.032089"
|
||||
"Hard Rock Cafe Yankee Stadium","40.828478","-73.925797"
|
||||
"Hard Rock Cafe Yokohama","35.45584","139.63303"
|
||||
"Hard Rock Cafe Guadalajara","20.67663","-103.41351"
|
|