Browse Source

spiega su docker-compose

kiki 5 years ago
parent
commit
28df8741ba

+ 8 - 0
_data/sidebars/mydoc_sidebar.yml

@@ -27,6 +27,10 @@ entries:
       url: /mydoc_introduzione.html
       output: web, pdf
 
+    - title: Documentazione
+      url: /mydoc_documentazione.html
+      output: web, pdf
+
     - title: Installazione
       url: /mydoc_server.html
       output: web, pdf
@@ -34,4 +38,8 @@ entries:
     - title: L'idea e la struttura
       url: /mydoc_about.html
       output: web, pdf
+ 
+    - title: Utilizzo
+      url:  /mydoc_utilizzo.html
+      output:  web, pdf
 

+ 1 - 1
_posts/2019-01-10-ripresa.md

@@ -21,7 +21,7 @@ Si immette la pasw, non la si vede quando la si digita. a si mette due volte.. F
 
       su dispensa
 
-Ora siamo dispensa!  Una utente senza privilegi di root, quindi senza i super poteri della radice!  
+Ora siamo dispensa!  Una utente senza privilegi di root, quindi senza poteri di amministrazione!  
 
 [http://guide.debianizzati.org/index.php/Guida_ai_comandi_da_terminale_-_Gestione_utenti_e_gruppi](Approfondimento gestione utenti in Debian)
 

+ 4 - 4
_posts/2019-01-13-ancora_docker.md

@@ -1,11 +1,11 @@
 ---
-title:  "Ancora docker"
-permalink: ripresa2019.html
-tags: [news], [docker]
+title: "Ancora docker e docker-compose"
+permalink: ancora_docker.html
+tags: [server]
 ---
 
 
-Incontro domenica pomeriggio, ca battistini.
+Incontro domenica pomeriggio, ca battistini. 13 gennaio 2019.
 
 L'obiettivo è tornare sui propri passi, distruggere i container già esistenti ed avviarne due nuovi: un mariadb e un nextcloud.
 	docker --version

+ 20 - 0
_posts/2019-01-20-AGgennaio.md

@@ -0,0 +1,20 @@
+---
+title:  "prima assemblea generale 2019"
+permalink: 2019assembleagenerale01di6.html
+tags: [assemblea]
+---
+
+
+Assemblea generale allo Zonarelli, dalle 10 alle 18. Pranzo al sacco.
+Ordine del giorno:
+
+* Sostenibilità condivisa MAG6
+* proposte tavolo formazione
+* proposte tavoli bioregionali
+* riflessione sull'organizzazione strutturale di Campiaperti
+* deliberazione
+* report visite nuovi ingressi
+
+rilettura dei report.
+
+{% include links.html %}

+ 1 - 1
index.md

@@ -37,6 +37,6 @@ Si parla di tecnologia e di come la usiamo per i nostri scopi: il mutualismo, la
 * Sito web campiaperti.org
 * Video pubblicati su Arkiwi.org e embeddati nel sito campiaperti.org
 
-Non sono elencati i servizi che usaiamo su piattaforme di terzi.
+Non sono elencati i servizi che usiamo su piattaforme di terzi.
 
 {% include links.html %}

+ 27 - 1
pages/mydoc/mydoc_about.md

@@ -33,6 +33,31 @@ Appena loggata sul server puoi vedere se la macchina è aggiornata:
 
 Oppure se è un comando dato da poco: freccia su; oppure se lo vuoi cercare al volo nella bash_history:  ctrl+r  e poi digiti la parola da cercare.
 
+## autenticarsi ssh:
+
+requisiti: chiave segreta
+- pasw segreta
+-software ssh
+ in un terminale:
+
+~$ssh-add .ssh/campiaperti
+
+$ssh-add ~/.ssh/campiaperti
+
+Se ti dice che i permessi sono sbagliati fai:
+
+nella cartellina dove hai la chiave scrivi -ls -l così vedi di chi sono i file.
+Il tuo file della chiaveprivata deve essere accessibile, in lettura e uso solo dal tuo utente.
+
+in grafica: clicca sul file con il pulsante destro, scegli propriet- > permessi e setta:
+me: leggiscrivi
+gruppo: nessuno
+altri:nessuno
+
+quindi cambi i permessi e poi ci riprovi. gli metti la password e fatto!
+
+approfondimenti: https://it.wikipedia.org/wiki/RSA
+
 ### Caricare i file da ssh
 
 upload: local -> remote
@@ -40,7 +65,8 @@ upload: local -> remote
 caricare: dal locale al remoto
   
 	scp local_file user@remote_host:remote_file
-Quindi
+
+Quindi un esempio
 
 	scp -P 2222 Scrivania/CA_tutto/SERVER-campiaperti/CA_logo_2017.svg  root@campiaperti.tetaneutral.net:/var/app/themes/dispensatheme/core/img
 

+ 0 - 136
pages/mydoc/mydoc_faq.md

@@ -1,136 +0,0 @@
----
-title: FAQ layout
-permalink: mydoc_faq_layout.html
-sidebar: mydoc_sidebar
-tags: [special_layouts]
-keywords: frequently asked questions, FAQ, question and answer, collapsible sections, expand, collapse
-last_updated: November 30, 2015
-summary: "You can use an accordion-layout that takes advantage of Bootstrap styling. This is useful for an FAQ page."
-toc: false
-folder: mydoc
----
-
-<p>If you want to use an FAQ format, use the syntax shown on the faq.html page. Rather than including code samples here (which are bulky with a lot of nested <code>div</code> tags), just look at the source in the mydoc_faq.html theme file.</p>
-
-<div class="panel-group" id="accordion">
-                    <div class="panel panel-default">
-                        <div class="panel-heading">
-                            <h4 class="panel-title">
-                                <a class="noCrossRef accordion-toggle" data-toggle="collapse" data-parent="#accordion" href="#collapseOne">Lorem ipsum dolor sit amet, consectetur adipiscing elit?</a>
-                            </h4>
-                        </div>
-                        <div id="collapseOne" class="panel-collapse collapse noCrossRef">
-                            <div class="panel-body">
-                                Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.
-                            </div>
-                        </div>
-                    </div>
-                    <!-- /.panel -->
-                    <div class="panel panel-default">
-                        <div class="panel-heading">
-                            <h4 class="panel-title">
-                                <a class="noCrossRef accordion-toggle" data-toggle="collapse" data-parent="#accordion" href="#collapseTwo">Curabitur eget leo at velit imperdiet varius. In eu ipsum vitae velit congue iaculis vitae at risus?</a>
-                            </h4>
-                        </div>
-                        <div id="collapseTwo" class="panel-collapse collapse noCrossRef">
-                            <div class="panel-body">
-                                Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.
-                            </div>
-                        </div>
-                    </div>
-                    <!-- /.panel -->
-                    <div class="panel panel-default">
-                        <div class="panel-heading">
-                            <h4 class="panel-title">
-                                <a class="noCrossRef accordion-toggle" data-toggle="collapse" data-parent="#accordion" href="#collapseThree">Aenean consequat lorem ut felis ullamcorper?</a>
-                            </h4>
-                        </div>
-                        <div id="collapseThree" class="panel-collapse collapse noCrossRef">
-                            <div class="panel-body">
-                                Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.
-                            </div>
-                        </div>
-                    </div>
-                    <!-- /.panel -->
-                    <div class="panel panel-default">
-                        <div class="panel-heading">
-                            <h4 class="panel-title">
-                                <a class="noCrossRef accordion-toggle" data-toggle="collapse" data-parent="#accordion" href="#collapseFour">Lorem ipsum dolor sit amet, consectetur adipiscing elit?</a>
-                            </h4>
-                        </div>
-                        <div id="collapseFour" class="panel-collapse collapse">
-                            <div class="panel-body">
-                                Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.
-                            </div>
-                        </div>
-                    </div>
-                    <!-- /.panel -->
-                    <div class="panel panel-default">
-                        <div class="panel-heading">
-                            <h4 class="panel-title">
-                                <a class="noCrossRef accordion-toggle" data-toggle="collapse" data-parent="#accordion" href="#collapseFive">Curabitur eget leo at velit imperdiet varius. In eu ipsum vitae velit congue iaculis vitae at risus?</a>
-                            </h4>
-                        </div>
-                        <div id="collapseFive" class="panel-collapse collapse">
-                            <div class="panel-body">
-                                Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.
-                            </div>
-                        </div>
-                    </div>
-                    <!-- /.panel -->
-                    <div class="panel panel-default">
-                        <div class="panel-heading">
-                            <h4 class="panel-title">
-                                <a class="noCrossRef accordion-toggle" data-toggle="collapse" data-parent="#accordion" href="#collapseSix">Aenean consequat lorem ut felis ullamcorper?</a>
-                            </h4>
-                        </div>
-                        <div id="collapseSix" class="panel-collapse collapse">
-                            <div class="panel-body">
-                                Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.
-                            </div>
-                        </div>
-                    </div>
-                    <!-- /.panel -->
-                    <div class="panel panel-default">
-                        <div class="panel-heading">
-                            <h4 class="panel-title">
-                                <a class="noCrossRef accordion-toggle" data-toggle="collapse" data-parent="#accordion" href="#collapseSeven">Lorem ipsum dolor sit amet, consectetur adipiscing elit?</a>
-                            </h4>
-                        </div>
-                        <div id="collapseSeven" class="panel-collapse collapse">
-                            <div class="panel-body">
-                                Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.
-                            </div>
-                        </div>
-                    </div>
-                    <!-- /.panel -->
-                    <div class="panel panel-default">
-                        <div class="panel-heading">
-                            <h4 class="panel-title">
-                                <a class="noCrossRef accordion-toggle" data-toggle="collapse" data-parent="#accordion" href="#collapseEight">Curabitur eget leo at velit imperdiet varius. In eu ipsum vitae velit congue iaculis vitae at risus?</a>
-                            </h4>
-                        </div>
-                        <div id="collapseEight" class="panel-collapse collapse">
-                            <div class="panel-body">
-                                Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.
-                            </div>
-                        </div>
-                    </div>
-                    <!-- /.panel -->
-                    <div class="panel panel-default">
-                        <div class="panel-heading">
-                            <h4 class="panel-title">
-                                <a class="noCrossRef accordion-toggle" data-toggle="collapse" data-parent="#accordion" href="#collapseNine">Aenean consequat lorem ut felis ullamcorper?</a>
-                            </h4>
-                        </div>
-                        <div id="collapseNine" class="panel-collapse collapse">
-                            <div class="panel-body">
-                                Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon tempor, sunt aliqua put a bird on it squid single-origin coffee nulla assumenda shoreditch et. Nihil anim keffiyeh helvetica, craft beer labore wes anderson cred nesciunt sapiente ea proident. Ad vegan excepteur butcher vice lomo. Leggings occaecat craft beer farm-to-table, raw denim aesthetic synth nesciunt you probably haven't heard of them accusamus labore sustainable VHS.
-                            </div>
-                        </div>
-                    </div>
-                    <!-- /.panel -->
-</div>
-<!-- /.panel-group -->
-
-{% include links.html %}

+ 0 - 429
pages/mydoc/mydoc_generating_pdfs.md

@@ -1,429 +0,0 @@
----
-title: Generating PDFs
-permalink: mydoc_generating_pdfs.html
-tags: [publishing, single_sourcing, content_types]
-keywords: PDF, prince, prince XML, ant, xsl fo
-last_updated: July 3, 2016
-summary: "You can generate a PDF from your Jekyll project. You do this by creating a web version of your project that is printer friendly. You then use utility called Prince to iterate through the pages and create a PDF from them. It works quite well and gives you complete control to customize the PDF output through CSS, including page directives and dynamic tags from Prince."
-sidebar: mydoc_sidebar
-folder: mydoc
----
-
-
-## PDF overview
-This process for creating a PDF relies on Prince XML to transform the HTML content into PDF. Prince costs about $500 per license. That might seem like a lot, but if you're creating a PDF, you're probably working for a company that sells a product, so you likely have access to some resources. There's also a free license that prints a small "P" watermark on your title page, so if you're fine with that, great.
-
-The basic approach is to generate a list of all web pages that need to be added to the PDF, and then add leverage Prince to package them up into a PDF. Once you set it up, building a pdf is just a matter of running a couple of commands. Also, creating a PDF this way gives you a lot more control and customization capabilities than with other methods for creating PDFs. If you know CSS, you can entirely customize the output.
-
-## Demo
-
-You can see an example of the finished product here:
-
-<a target="\_blank" class="noCrossRef" href="{{ "pdf/mydoc.pdf"}}"><button type="button" class="btn btn-default" aria-label="Left Align"><span class="glyphicon glyphicon-download-alt" aria-hidden="true"></span> PDF Download</button></a>
-
-To generate the PDF, browse to the theme's directory in your terminal and run this script:
-
-```bash
-. pdf-mydoc.sh
-```
-
-This builds a PDF for the documentation in the theme. Look in the **pdf** folder for the output, and see the "last generated date" to confirm that you generated the PDF.
-
-To build a PDF for the other sample projects, run these commands:
-
-```bash
-. pdf-product1.sh
-```
-
-or
-
-```bash
-. pdf-product2.sh
-```
-
-You can see the details of the script in these files in the theme's root directory. For example, open pdf-mydoc.sh. It contains the following:
-
-```bash
-# Note that .sh scripts work only on Mac. If you're on Windows, install Git Bash and use that as your client.
-
-echo 'Kill all Jekyll instances'
-kill -9 $(ps aux | grep '[j]ekyll' | awk '{print $2}')
-clear
-
-echo "Building PDF-friendly HTML site for Mydoc ...";
-bundle exec jekyll serve --detach --config _config.yml,pdfconfigs/config_mydoc_pdf.yml;
-echo "done";
-
-echo "Building the PDF ...";
-prince --javascript --input-list=_site/pdfconfigs/prince-list.txt -o pdf/mydoc.pdf;
-
-echo "Done. Look in the pdf directory to see if it printed successfully."
-```
-
-After stopping all Jekyll instances, we build Jekyll using a special configuration file that specifies a unique stylesheet. The build contains a file (prince-list.txt) that contains a list of all pages to be included in the PDF. We feed this list into a Prince command to build the PDF.
-
-The following sections explain more about the setup.
-
-## 1. Set up Prince
-
-Download and install [Prince](http://www.princexml.com/doc/installing/).
-
-You can install a fully functional trial version. The only difference is that the title page will have a small Prince PDF watermark.
-
-## 2. Create a new configuration file for each of your PDF targets
-
-The PDF configuration file will build on the settings in the regular configuration file but will some additional fields. Here's the configuration file for the mydoc product within this theme. This configuration file is located in the pdfconfigs folder.
-
-```yaml
-destination: _site/
-url: "http://127.0.0.1:4010"
-baseurl: "/mydoc-pdf"
-port: 4010
-output: pdf
-product: mydoc
-print_title: Jekyll theme for documentation — mydoc product
-print_subtitle: version 5.0
-output: pdf
-defaults:
-  -
-    scope:
-      path: ""
-      type: "pages"
-    values:
-      layout: "page_print"
-      comments: true
-      search: true
-
-pdf_sidebar: mydoc_sidebar
-```
-
-{% include note.html content="Although you're creating a PDF, you must still build an HTML web target before running Prince. Prince will pull from the HTML files and from the file-list for the TOC." %}
-
-Note that the default page layout specified by this configuration file is `page_print`. This layout strips out all the sections that shouldn't appear in the print PDF, such as the sidebar and top navigation bar.
-
-Also note that there's a `output: pdf` property in case you want to make some of your content unique to PDF output. For example, you could add conditional logic that checks whether `site.output` is `pdf` or `web`. If it's `pdf`, then include information only for the PDF, and so on. If you're using nav tabs, you'll definitely want to create an alternative experience in the PDF.
-
-In the configuration file, customize the values for the `print_title` and `print_subtitle` that you want. These will appear on the title page of the PDF.
-
-We will access this configure file in the PDF generation script.
-
-## 3. Make sure your sidebar data file has titlepage.html and tocpage.html entries
-
-There are two template pages in the root directory that are critical to the PDF:
-
-* titlepage.html
-* tocpage.html
-
-These pages should appear in your sidebar YML file (in this product, mydoc_sidebar.yml):
-
-```yaml
-- title:
-  output: pdf
-  type: frontmatter
-  folderitems:
-  - title:
-    url: /titlepage.html
-    output: pdf
-    type: frontmatter
-  - title:
-    url: /tocpage.html
-    output: pdf
-    type: frontmatter
-```
-
-Leave these pages here in your sidebar. (The `output: pdf` property means they won't appear in your online TOC because the conditional logic of the sidebar.html checks whether `web` is equal to `pdf` or not before including the item in the web version of the content.)
-
-The code in the tocpage.html is mostly identical to that of the sidebar.html page. This is essential for Prince to create the page numbers correctly with cross references.
-
-There's another file (in the root directory of the theme) that is critical to the PDF generation process: prince-list.txt. This file simply iterates through the items in your sidebar and creates a list of links. Prince will consume the list of links from prince-list.txt and create a running PDF that contains all of the pages listed, with appropriate cross references and styling for them all.
-
-{% include note.html content="If you have any files that you do not want to appear in the PDF, add <code>output: web</code> (rather than <code>output: pdf</code>) in the list of attributes in your sidebar. The prince-list.txt file that loops through the mydoc_sidebar.yml file to grab the URLs of each page that should appear in the PDF will skip over any items that do not list <code>output: pdf</code> in the item attributes. For example, you might not want your tag archives to appear in the PDF, but you probably will want to list them in the online help navigation." %}
-
-## 4. Customize your headers and footers
-
-Open up the css/printstyles.css file and customize what you want for the headers and footers. At the very least, customize the email address (`youremail@domain.com`) that appears in the bottom left.
-
-Exactly how the print styling works here is pretty nifty. You don't need to understand the rest of the content in this section unless you want to customize your PDFs to look different from what I've configured. But I'm adding this information here in case you want to understand how to customize the look and feel of the PDF output.
-
-This style creates a page reference for a link:
-
-{% raw %}
-```css
-a[href]::after {
-    content: " (page " target-counter(attr(href), page) ")"
-}
-```
-
-You don't want cross references for any link that doesn't reference another page, so this style specifies that the content after should be blank:
-
-```css
-a[href*="mailto"]::after, a[data-toggle="tooltip"]::after, a[href].noCrossRef::after {
-    content: "";
-}
-```
-{% endraw %}
-
-{% include tip.html content="If you have a link to a file download, or some other link that shouldn't have a cross reference (such as link used in JavaScript for navtabs or collapsible sections, for example, add `noCrossRef` as a class to the link to avoid having it say \"page 0\" in the cross reference." %}
-
-This style specifies that after links to web resources, the URL should be inserted instead of the page number:
-
-```css
-a[href^="http:"]::after, a[href^="https:"]::after {
-    content: " (" attr(href) ")";
-}
-```
-
-This style sets the page margins:
-
-```css
-@page {
-    margin: 60pt 90pt 60pt 90pt;
-    font-family: sans-serif;
-    font-style:none;
-    color: gray;
-
-}
-```
-
-To set a specific style property for a particular page, you have to name the page. This allows Prince to identify the page.
-
-First you add frontmatter to the page that specifies the type. For the titlepage.html, here's the frontmatter:
-
-```yaml
----
-type: title
----
-```
-
-For the tocpage, here's the frontmatter:
-
-```yaml
----
-type: frontmatter
----
-```
-
-For the index.html page, we have this type tag (among others):
-
-```yaml
----
-type: first_page
----
-```
-
-The default_print.html layout will change the class of the `body` element based on the type value in the page's frontmatter:
-
-{% raw %}
-```liquid
-<body class="{% if page.type == "title"%}title{% elsif page.type == "frontmatter" %}frontmatter{% elsif page.type == "first_page" %}first_page{% endif %} print">
-```
-{% endraw %}
-
-Now in the css/printstyles.css file, you can assign a page name based on a specific class:
-
-```css
-body.title { page: title }
-```
-
-This means that for content inside of `body class="title"`, we can style this page in our stylesheet using `@page title`.
-
-Here's how that title page is styled:
-
-```css
-@page title {
-    @top-left {
-        content: " ";
-    }
-    @top-right {
-        content: " "
-    }
-    @bottom-right {
-        content: " ";
-    }
-    @bottom-left {
-        content: " ";
-    }
-}
-```
-
-As you can see, we don't have any header or footer content, because it's the title page.
-
-For the tocpage.html, which has the `type: frontmatter`, this is specified in the stylesheet:
-
-```css
-body.frontmatter { page: frontmatter }
-body.frontmatter {counter-reset: page 1}
-
-
-@page frontmatter {
-    @top-left {
-        content: prince-script(guideName);
-    }
-    @top-right {
-        content: prince-script(datestamp);
-    }
-    @bottom-right {
-        content: counter(page, lower-roman);
-    }
-    @bottom-left {
-        content: "youremail@domain.com";   }
-}
-```
-
-With `counter(page, lower-roman)`, we reset the page count to 1 so that the title page doesn't start the count. Then we also add some header and footer info. The page numbers start counting in lower-roman numerals.
-
-Finally, for the first page (which doesn't have a specific name), we restart the counting to 1 again and this time use regular numbers.
-
-```css
-body.first_page {counter-reset: page 1}
-
-h1 { string-set: doctitle content() }
-
-@page {
-    @top-left {
-        content: string(doctitle);
-        font-size: 11px;
-        font-style: italic;
-    }
-    @top-right {
-        content: prince-script(datestamp);
-        font-size: 11px;
-    }
-
-    @bottom-right {
-        content: "Page " counter(page);
-        font-size: 11px;
-    }
-    @bottom-left {
-        content: prince-script(guideName);
-        font-size: 11px;
-    }
-}
-```
-
-You'll see some other items in there such as `prince-script`. This means we're using JavaScript to run some functions to dynamically generate that content. These JavaScript functions are located in the \_includes/head_print.html:
-
-```js
-<script>
-    Prince.addScriptFunc("datestamp", function() {
-        return "PDF last generated: {{ site.time | date: '%B %d, %Y' }}";
-    });
-</script>
-
-<script>
-    Prince.addScriptFunc("guideName", function() {
-        return "{{site.print_title}} User Guide";
-    });
-</script>
-```
-
-There are a couple of Prince functions that are default functions from Prince. This gets the heading title of the page:
-
-```js
-        content: string(doctitle);
-```
-
-This gets the current page:
-
-```js
-        content: "Page " counter(page);
-```
-
-Because the theme uses JavaScript in the CSS, you have to add the `--javascript` tag in the Prince command (detailed later on this page).
-
-## 5. Customize and run the PDF script
-
-Duplicate the pdf-mydoc.sh file in the root directory and customize it for your specific configuration files.
-
-```
-echo 'Killing all Jekyll instances'
-kill -9 $(ps aux | grep '[j]ekyll' | awk '{print $2}')
-clear
-
-echo "Building PDF-friendly HTML site for Mydoc ...";
-jekyll serve --detach --config _config.yml,pdfconfigs/config_mydoc_pdf.yml;
-echo "done";
-
-echo "Building the PDF ...";
-prince --javascript --input-list=_site/pdfconfigs/prince-list.txt -o pdf/mydoc.pdf;
-echo "done";
-```
-
-Note that the first part kills all Jekyll instances. This way you won't try to serve Jekyll at a port that is already occupied.
-
-The `jekyll serve` command serves up the HTML-friendly PDF configurations for our two projects. This web version is where Prince will go to get its content.
-
-The prince script issues a command to the Prince utility. JavaScript is enabled (`--javascript`), and we tell it exactly where to find the list of files (`--input-list`) &mdash; just point to the prince-list.txt file. Then we tell it where and what to output (`-o`).
-
-Make sure that the path to the prince-list.txt is correct. For the output directory, I like to output the PDF file into my project's source (into the files folder). Then when I build the web output, the PDF is included and something I can refer to.
-
-{% include note.html content="You might not want to include the PDF in your project files, since you're likely committing the PDF to Github and as a result saving the changes from one PDF version to another with each save." %}
-
-## 6. Add conditions for your new builds in the PDF config file
-
-In the PDF configuration file, there's a section that looks like this:
-
-```
-{% raw %}{% if site.product == "mydoc" %}
-pdf_sidebar: product2_sidebar
-{% endif %}
-```
-
-Point to the sidebar you want here.
-
-What this does is allow the prince-list.txt and toc.html files to iterate through the right sidebar.  Otherwise, you would need to create a unique prince-list.txt and toc.html file for each separate PDF output you have.
-
-## 7. Add a download button for the PDF
-
-You can add a download button for your PDF using some Bootstrap button code:
-
-```html
-<a target="_blank" class="noCrossRef" href="/pdf/mydoc.pdf"><button type="button" class="btn btn-default" aria-label="Left Align"><span class="glyphicon glyphicon-download-alt" aria-hidden="true"></span> PDF Download</button></a>
-```
-
-Here's what that looks like:
-
-<a target="\_blank" class="noCrossRef" href={{ "pdf/mydoc.pdf"}}"><button type="button" class="btn btn-default" aria-label="Left Align"><span class="glyphicon glyphicon-download-alt" aria-hidden="true"></span> PDF Download</button></a>
-
-## JavaScript conflicts
-
-If you have JavaScript on any of your pages, Prince will note errors in Terminal like this:
-
-```
-error: TypeError: value is not an object
-```
-
-However, the PDF will still build.
-
-You need to conditionalize out any JavaScript from your PDF web output before building your PDFs. Make sure that the PDF configuration files have the `output: pdf` property.
-
-Then surround the JavaScript with conditional tags like this:
-
-```
-{% raw %}{% unless site.output == "pdf" %}
-javascript content here ...
-{% endunless %}{% endraw %}
-```
-
-For more detail about using `unless` in conditional logic, see [Conditional logic][mydoc_conditional_logic]. What this code means is "run this code unless this value is the case."
-
-## Overriding Bootstrap Print Styles
-
-The theme relies on Bootstrap's CSS for styling. However, for print media, Bootstrap applies the following style:
-
-```
-@media print{*,:after,:before{color:#000!important;text-shadow:none!important;background:0 0!important;-webkit-box-shadow:none!important;box-shadow:none!important}
-```
-This is minified, but basically the `*` (asterisk) means select all, and applied the color #000 (black). As a result, the Bootstrap style strips out all color from the PDF (for Bootstrap elements).
-
-This is problematic for code snippets that have syntax highlighting. I decided to remove this de-coloring from the print output. I commented out the Bootstrap style:
-
-```
-@media print{*,:after,:before{/*color:#000!important;*/text-shadow:none!important;/*background:0 0!important*/;-webkit-box-shadow:none!important;box-shadow:none!important}
-```
-
-If you update Bootrap, make sure you make this edit. (Sorry, admittedly I couldn't figure out how to simply overwrite the `*` selector with a later style.)
-
-I did, however, remove the color from the alerts and lighten the background shading for `pre` elements. The printstyles.css has this setting.
-
-{% include links.html %}

+ 0 - 21
pages/mydoc/mydoc_introduction.md

@@ -24,26 +24,5 @@ Quindi a grandi linee le scelte progettuali e tecnologiche fatte sono:
 * [Docker](https://www.docker.com/why-docker)
 * [Nextcloud](https://nextcloud.com/) 
 
-## Come contribuire alla documentazione
-
-Da un terminale si installa git
-
-    apt install git
-
-Ci si apre un account su git.lattuga.net
-
-Si apre sul proprio pc un terminale si digita:
-
-   git clone https://git.lattuga.net/campiaperti/documentazione.git
-
-   cd documentazione
-
-E si modificano le pagine dentro a pages/
-
-esempio: documentazione/pages/mydoc/mydoc_introduction.md
-
-poi si fa 
-
-     git status
 
 {% include links.html %}

+ 137 - 57
pages/mydoc/mydoc_server.md

@@ -6,85 +6,163 @@ permalink: mydoc_server.html
 folder: mydoc
 ---
 
-
-## autenticarsi ssh:
-
-requisiti: chiave segreta
-- pasw segreta
--software ssh
- in un terminale:
-
-~$ssh-add .ssh/campiaperti
-
-$ssh-add ~/.ssh/campiaperti
-
-Se ti dice che i permessi sono sbagliati fai:
-
-nella cartellina dove hai la chiave scrivi -ls -l così vedi di chi sono i file.
-Il tuo file della chiaveprivata deve essere accessibile, in lettura e uso solo dal tuo utente.
-
-in grafica: clicca sul file con il pulsante destro, scegli propriet- > permessi e setta:
-me: leggiscrivi
-gruppo: nessuno
-altri:nessuno
-
-quindi cambi i permessi e poi ci riprovi. gli metti la password e fatto!
-
-approfondimenti: https://it.wikipedia.org/wiki/RSA
-
-
-# connettersi ssh al server
-
-$ssh -p 2222 -l root campiaperti.tetaneutral.net
-
-a questo punto SEI NELLA MACCHINA!
-
-approfondimenti: https://it.wikipedia.org/wiki/Secure_Shell
-
+Seguito il tutorial [https://linuxize.com/post/how-to-install-and-use-docker-compose-on-debian-9/#uninstalling-docker-compose](https://linuxize.com/post/how-to-install-and-use-docker-compose-on-debian-9/#uninstalling-docker-compose)
 
 ## installato docker
 
-https://docs.docker.com/install/linux/docker-ce/debian/#install-using-the-repository
+[https://docs.docker.com/install/linux/docker-ce/debian/#install-using-the-repository](tutorial seguito)
 
 installato dipendenze, aggiunto repository di docker, aggiunto chiave GPG di docker, scaricato e aggiornato i repo, quindi installato docker sull server.
 
-Installata l'immagine nextcloud conteinerizzata:
+        apt-get update
 
-    docker pull nextcloud
+	apt-get install \
+    apt-transport-https \
+    ca-certificates \
+    curl \
+    gnupg2 \
+    software-properties-common
 
-    docker run -d -p 8080:80 nextcloud
+	curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add -
 
-SE IL TERMINALE NON DA ERRORI é ANDATO TUTTO BENE
+	sudo apt-key fingerprint 0EBFCD88
 
-visita: campiaperti.tetaneutral.net:8080
+confrontare le fingerprint: 9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88
 
-funziona.
+	add-apt-repository \
+   "deb [arch=amd64] https://download.docker.com/linux/debian \
+   $(lsb_release -cs) \
+   stable"
 
-scaricato mySQL
+	apt update
 
-	docker pull mysql
+	apt install docker-ce
 
-https://hub.docker.com/_/mysql/
-https://hub.docker.com/r/phpmyadmin/phpmyadmin/
+## Installare docker-compose
 
-impostato il servizo comunicante con l'altro ed il nextclpoud esposto sulla porta 80
+Verificare che davvero docker stia andando:
 
-visita: campiaperti.tetaneutral.net
+	systemctl start docker
+	systemctl enable docker	
 
-funziona! solo che poi abbiam sbagliato a cliccare nell'installazione in grafica.
+Installiamo docker-compose su debian 9
 
-Quindi
+<pre>
+curl -L "https://github.com/docker/compose/releases/download/1.23.1/docker-comp$
 
-TODO:
-Installare docker con il mysql ora comunicante ed installare un certificato SSL!
-Varare il servizio! personalizzarlo, predisporre la robustezza sul lungo periodo (copie e rispristini)
+docker-ce -v
 
+chmod +x /usr/local/bin/docker-compose
 
-## installare certificati SSL sul server
+ls -l /usr/local/bin/ | grep docker
 
-    sudo apt-get install letsencrypt
+docker-compose --version
 
-Leggiamo https://letsencrypt.org/getting-started/
+</pre>
+
+Creiamo un network di container che si parlano
+
+	
+	docker network create nextcloud_network
+
+
+Scriviamo il nostro file di configurazioni di docker compose
+
+	nano docker-compose.yml
+
+ATTENZIONE: in questo file alcuni valori sono da cambiare! non abbiamo usato dei nomi di default e le passw non ci sono :)
+
+<pre>version: '3' 
+
+services:
+
+  proxy:
+    image: jwilder/nginx-proxy:alpine
+    labels:
+      - "com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy=true"
+    container_name: nextcloud-proxy
+    networks:
+      - nextcloud_network
+    ports:
+      - 80:80
+      - 443:443
+    volumes:
+      - ./proxy/conf.d:/etc/nginx/conf.d:rw
+      - ./proxy/vhost.d:/etc/nginx/vhost.d:rw
+      - ./proxy/html:/usr/share/nginx/html:rw
+      - ./proxy/certs:/etc/nginx/certs:ro
+      - /etc/localtime:/etc/localtime:ro
+      - /var/run/docker.sock:/tmp/docker.sock:ro
+    restart: unless-stopped
+  
+  letsencrypt:
+    image: jrcs/letsencrypt-nginx-proxy-companion
+    container_name: nextcloud-letsencrypt
+    depends_on:
+      - proxy
+    networks:
+      - nextcloud_network
+    volumes:
+      - ./proxy/certs:/etc/nginx/certs:rw
+      - ./proxy/vhost.d:/etc/nginx/vhost.d:rw
+      - ./proxy/html:/usr/share/nginx/html:rw
+      - /etc/localtime:/etc/localtime:ro
+      - /var/run/docker.sock:/var/run/docker.sock:ro
+    restart: unless-stopped
+
+  db:
+    image: mariadb
+    container_name: nextcloud-mariadb
+    networks:
+      - nextcloud_network
+    volumes:
+      - db:/var/lib/mysql
+      - /etc/localtime:/etc/localtime:ro
+    environment:
+      - MYSQL_ROOT_PASSWORD=toor
+      - MYSQL_PASSWORD=mysql
+      - MYSQL_DATABASE=nextcloud
+      - MYSQL_USER=nextcloud
+    restart: unless-stopped
+  
+  app:
+    image: nextcloud:latest
+    container_name: nextcloud-app
+    networks:
+      - nextcloud_network
+    depends_on:
+      - letsencrypt
+      - proxy
+      - db
+    volumes:
+      - nextcloud:/var/www/html
+      - ./app/config:/var/www/html/config
+      - ./app/custom_apps:/var/www/html/custom_apps
+      - ./app/data:/var/www/html/data
+      - ./app/themes:/var/www/html/themes
+      - /etc/localtime:/etc/localtime:ro
+    environment:
+      - VIRTUAL_HOST=nextcloud.YOUR-DOMAIN
+      - LETSENCRYPT_HOST=nextcloud.YOUR-DOMAIN
+      - LETSENCRYPT_EMAIL=YOUR-EMAIL
+    restart: unless-stopped
+
+volumes:
+  nextcloud:
+  db:
+
+networks:
+  nextcloud_network:
+</pre>
+
+Ora facciamo partire il tutto:
+
+	docker-compose up -d
+
+Verifichiamo che funzioni
+
+	docker ps -a
+	docker stats
 
 ## Personalizzare il thema grafico, esistente di nextcloud
 
@@ -92,7 +170,9 @@ Leggiamo https://letsencrypt.org/getting-started/
 
 Quindi davvero ci copiamo doppia la cartella del thema
 
-	
+	nano dispensatheme/core/css/server.css
+
+Per ora l'unica cosa diversa è il logo! che è stato caricato nella cartella del tema dentro a core/img
 
 
 {% include links.html %}

+ 0 - 167
pages/mydoc/mydoc_shuffle.html

@@ -1,167 +0,0 @@
----
-title: Shuffle layout
-tags: [special_layouts]
-last_updated: November 30, 2015
-keywords: shuffle, card layout, dynamic grid, doc portal, support portal
-summary: "This layout shows an example of a knowledge-base style navigation system, where there is no hierarchy, just groups of pages that have certain tags."
-permalink: mydoc_shuffle.html
-sidebar: mydoc_sidebar
-folder: mydoc
----
-
-
-
-{% if site.output == "pdf" %}
-{{site.data.alerts.note}} The content on this page doesn't display well on PDF, but I included it anyway so you could see the problems this layout poses if you're including it in PDF.  {{site.data.alerts.end}}
-{% endif %}
-
-{% unless site.output == "pdf" %}
-<script src="js/jquery.shuffle.min.js"></script>
-<script src="js/jquery.ba-throttle-debounce.min.js"></script>
-{% endunless %}
-
-      <div class="filter-options">
-      <button class="btn btn-primary" data-group="all">All</button>
-      <button class="btn btn-primary" data-group="getting_started">Getting Started</button>
-      <button class="btn btn-primary" data-group="formatting">Formatting</button>
-      <button class="btn btn-primary" data-group="publishing">Publishing</button>
-      <button class="btn btn-primary" data-group="content-types">Content types</button>
-          <button class="btn btn-primary" data-group="single_sourcing">Single Sourcing</button>
-      <button class="btn btn-primary" data-group="special_layouts">Special Layouts</button>
-    </div>      
-
-<div id="grid" class="row">
-
-
-    <div class="col-xs-6 col-sm-4 col-md-4" data-groups='["getting_started"]'>
-
-               <div class="panel panel-default">
-               <div class="panel-heading">Getting started</div>
-               <div class="panel-body">
-                  If you're getting started with Jekyll, see the links in this section. It will take you from the beginning level to comfortable. 
-                  <ul>
-                {% for page in site.pages %}
-                {% for tag in page.tags %}
-                {% if tag == "getting_started" %}
-                  <li><a href="{{page.url | remove: '/'}}">{{page.title}}</a></li>
-                {% endif %}
-                {% endfor %}
-                {% endfor %} 
-                  </ul>
-               </div>
-            </div>
-    
-    </div>
-   
-
-    <div class="col-xs-6 col-sm-4 col-md-4" data-groups='["content-types"]'>
-
-        <div class="panel panel-default">
-            <div class="panel-heading">Content types</div>
-            <div class="panel-body">
-                This section lists different content types and how to work with them.
-                <ul>
-                    {% for page in site.pages %}
-                    {% for tag in page.tags %}
-                    {% if tag == "content-types" %}
-                    <li><a href="{{page.url | remove: '/'}}">{{page.title}}</a></li>
-                    {% endif %}
-                    {% endfor %}
-                    {% endfor %}
-                </ul>
-            </div>
-        </div>
-        
-    </div>
-
-
-
-    <div class="col-xs-6 col-sm-4 col-md-4" data-groups='["formatting"]'>
-
-                <div class="panel panel-default">
-               <div class="panel-heading">Formatting</div>
-               <div class="panel-body">
-                  These topics get into formatting syntax, such as images and tables, that you'll use on each of your pages: 
-                  <ul>
-                {% for page in site.pages %}
-                {% for tag in page.tags %}
-                {% if tag == "formatting" %}
-                  <li><a href="{{page.url | remove: '/'}}">{{page.title}}</a></li>
-                {% endif %}
-                {% endfor %}
-                {% endfor %}
-                  </ul>
-               </div>
-            </div>
-
-    </div>
-
-    <div class="col-xs-6 col-sm-4 col-md-4" data-groups='["single_sourcing"]'>
-         
-      <div class="panel panel-default">
-               <div class="panel-heading">Single Sourcing</div>
-               <div class="panel-body">These topics cover strategies for single_sourcing. Single sourcing refers to strategies for re-using the same source in different outputs for different audiences or purposes.
-               <ul>
-                {% for page in site.pages %}
-                {% for tag in page.tags %}
-                {% if tag == "single_sourcing" %}
-                  <li><a href="{{page.url | remove: '/'}}">{{page.title}}</a></li>
-                {% endif %}
-                {% endfor %}
-                {% endfor %} 
-               </ul>
-            </div>
-         </div>
-
-    </div>
-
-       <div class="col-xs-6 col-sm-4 col-md-4" data-groups='["publishing"]'>
-
-           <div class="panel panel-default">
-               <div class="panel-heading">Publishing</div>
-               <div class="panel-body">When you're building, publishing, and deploying your Jekyll site, you might find these topics helpful.
-                   <ul>
-                {% for page in site.pages %}
-                {% for tag in page.tags %}
-                {% if tag == "publishing" %}
-                  <li><a href="{{page.url | remove: '/'}}">{{page.title}}</a></li>
-                {% endif %}
-                {% endfor %}
-                {% endfor %}
-                   </ul>
-               </div>
-            </div>
-
-    </div>
-
-        <div class="col-xs-6 col-sm-4 col-md-4" data-groups='["special_layouts"]'>
-
-             <div class="panel panel-default">
-               <div class="panel-heading">Special Layouts</div>
-               <div class="panel-body">
-                  These pages highlight special layouts outside of the conventional page and TOC hierarchy.
-                  <ul>
-                {% for page in site.pages %}
-                {% for tag in page.tags %}
-                {% if tag == "special_layouts" %}
-                     <li><a href="{{page.url | remove: '/'}}">{{page.title}}</a></li>
-                {% endif %}
-                {% endfor %}
-                {% endfor %} 
-                  </ul>
-               </div>
-            </div>
-
-    </div>
-          <!-- sizer -->
-      <div class="col-xs-6 col-sm-4 col-md-1 shuffle_sizer"></div>          
-
-
-    </div><!-- /#grid -->
-
-{% unless site.output == "pdf" %}
-{% include initialize_shuffle.html %}
-{% endunless %}
-
-{{site.data.alerts.note}} This was mostly an experiment to see if I could break away from the hierarchical TOC and provide a different way of arranging the content. However, this layout is somewhat problematic because it doesn't allow you to browse other navigation options on the side while viewing a topic.{{site.data.alerts.end}}
-

+ 31 - 1
pages/mydoc/mydoc_strumenti.md

@@ -1,11 +1,41 @@
 ---
 title: Strumenti utili sul server
 sidebar: mydoc_sidebar
-permalink: mydoc_installazione.html
+permalink: mydoc_documentazione.html
 folder: mydoc
 ---
 
+## Come contribuire alla documentazione
 
+Da un terminale si installa git
+
+    apt install git
+
+Ci si apre un account su git.lattuga.net
+
+Si apre sul proprio pc un terminale si digita:
+
+   git clone https://git.lattuga.net/campiaperti/documentazione.git
+
+   cd documentazione
+
+E si modificano le pagine dentro a pages/
+
+esempio: documentazione/pages/mydoc/mydoc_introduction.md
+
+poi si fa 
+
+     git status
+
+e si vedono le pagine modificate, se sono giuste si fa
+	git add .
+così si aggiungono tutte, oppure si aggiungono una per una con il loro percorso, esempio:
+
+	git add pages/mianuovapagina.md
+
+Per aggiungerle alla lista a sinistra: 
+
+{% include links.html %}
 
 
 {% include links.html %}

+ 29 - 0
pages/mydoc/mydoc_utilizzo.md

@@ -0,0 +1,29 @@
+---
+title: Utilizzo
+sidebar: mydoc_sidebar
+summary: "Usare la dispensa"
+permalink: mydoc_utilizzo.html
+folder: mydoc
+---
+
+# Usare la dispensa online
+
+
+## Sincronizzare le cartelle (locali sul tuo pc ed online sul server)
+
+
+* [https://www.linuxbabe.com/debian/install-nextcloud-desktop-client-debian-9-stretch](Su Debian 9)
+
+* [https://launchpad.net/~nextcloud-devs/+archive/ubuntu/client](Su Ubuntu)
+
+* [https://docs.nextcloud.com/server/12/user_manual/files/access_webdav.html](Usano webdav su qualunque linux)
+
+* [https://nextcloud.com/install/#install-clients](Su windows e MAC)
+
+* [https://f-droid.org/packages/com.nextcloud.client/](Per Android gratuita su Fdroid)
+
+* [https://play.google.com/store/apps/details?id=com.nextcloud.client](Su Android da googleplay)
+
+* [https://itunes.apple.com/us/app/nextcloud/id1125420102?mt=8](Su IOS)
+
+{% include links.html %}