<commit_before>---
published: false
title: Build up a backend to make maps
layout: post
---
This is the most technical part of the whole process and we are going to use some DevOps tools.

If you are only focused on the creation and management of the data have a look only to the System Overview section and beg your your nerd best friend to read the rest of the post and do the nerd work for you.

## System overview

<img title="RIGHT CLICK TO OPEN !!! - System diagram" src="https://raw.githubusercontent.com/f-ds/f-ds.github.io/master/public/img/make_data_geobackend.png" width="50%">

* Geoserver

* PostGIS 

* GDAL

## Buy a Virtual Machine

If you didn't realize it yet, we need a server steadily up and running in order to serve the maps to a client. We can easilly deploy all the static code of a map browser on github pages but we need a backend to host our custom dataset created in the previous post.

Unless you are a very insane and weird person you won't use your old desktop computer for this pourpouse. 

The reason is simple: your partner will break up with you due to the 24h server noise in your bedroom, your electrical company will kindly send each month high bills and you have also to pay a lot for a very good internet connection and a static IP address.
<commit_msg>Post update: Build up a backend to make maps<commit_after>---
published: false
title: Build up a backend to make maps
layout: post
---
This is the most technical part of the whole process and we are going to use some DevOps tools.

If you are only focused on the creation and management of the data have a look only to the System Overview section and beg your your nerd best friend to read the rest of the post and do the nerd work for you.

## System overview

<img title="RIGHT CLICK TO OPEN !!! - System diagram" src="https://raw.githubusercontent.com/f-ds/f-ds.github.io/master/public/img/make_data_geobackend.png" width="70%">

* Geoserver

* PostGIS 

* GDAL

## Buy a Virtual Machine

If you didn't realize it yet, we need a server steadily up and running in order to serve the maps to a client. We can easilly deploy all the static code of a map browser on github pages but we need a backend to host our custom dataset created in the previous post.

Unless you are a very insane and weird person you won't use your old desktop computer for this pourpouse. 

The reason is simple: your partner will break up with you due to the 24h server noise in your bedroom, your electrical company will kindly send each month high bills and you have also to pay a lot for a very good internet connection and a static IP address.

{'fraction_non_alphanumeric': 0.04776461597248758, 'fraction_numerical': 0.003056935422239205, 'mean_word_length': 3.9118198874296435, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1561839', 'n_tokens_mistral': 700, 'n_tokens_neox': 671, 'n_words': 436}